MCP servers for AI agents
Model Context Protocol (MCP) clients such as Claude and Cursor can call the same BRAINIAC operations over Streamable HTTP. Tool listing is free. Invoking a paid tool uses the same x402 payment path as a direct POST to the API.
Where to start
Read MCP servers for catalog URLs, Cursor config, and which products are wrapped. Machine discovery also lives at /.well-known/mcp and /mcp/server.json.
Same prices as REST
MCP does not invent a second billing model. Each tool maps to a POST operation with a fixed USDC price on Base. Unpaid calls surface 402 terms; settlement still only happens on successful 2xx results. See x402 payments and How it works.
What agents typically call
Compliance and screening (sanctions screening), Base token checks (token security), construction and COI helpers (construction reporting), plus the broader API catalog.
Crawl note
Streamable MCP endpoints are POST-only; GET returns 405 and those URLs are omitted from the sitemap. Indexable discovery stays on the JSON docs and the MCP about page — POST tool calls themselves are unchanged.