BRAINIAC API catalog
Server Details
Search and call BRAINIAC pay-per-call APIs. Unpaid calls return 402.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 4 tools
The four tools split cleanly along discovery vs. metadata vs. execution lines: list_apis enumerates servers, search_endpoints finds endpoints, describe_endpoint returns schema/price without running, and call_endpoint actually executes a paid call. The describe_endpoint/call_endpoint pair is explicitly contrasted in their descriptions ("does not run the endpoint" vs. "call"), leaving no realistic misselection.
All four tools follow a strict snake_case verb_noun pattern (list_apis, search_endpoints, describe_endpoint, call_endpoint), with the verb carrying the semantic weight. The only trivial variation is singular 'endpoint' vs. plural 'endpoints/apis', which reads naturally rather than inconsistently.
Four tools is on the lean side, but each maps to a distinct stage of the workflow (browse → search → inspect → invoke) with no filler. It is a small surface, though nothing appears superfluous or missing at the tool-count level.
The core lifecycle for a paid endpoint catalog — discover APIs, find endpoints, inspect schema and price, execute with settlement — is fully covered. Gaps are minor but real: there is no way to check account balance, payment history, or failed-settlement status, which agents handling 402 responses may want.
Available Tools
4 toolscall_endpointCall endpointBInspect
Call one paid POST endpoint by id. Unpaid calls return 402 and do not run. Payment settles only after a successful result.
Inputs: id (required), params.
describe_endpointDescribe endpointAInspect
Return the input schema, example, path, and price for one paid endpoint. This does not run the endpoint.
Inputs: id (required).
list_apisList APIsBInspect
List the public MCP servers. Each server is one API.
Inputs: no named parameters.
search_endpointsSearch endpointsBInspect
Search paid endpoints by id, title, description, or path. Optional api is a product slug or title.
Inputs: query (required), api.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Discover and call pay-per-request (x402) APIs, ranked by reliability, latency and price.
Paid API Integration Intelligence API via x402. Unpaid tool calls return 402.
1Paid Crypto Payments API via x402. Unpaid tool calls return 402.
1Search and call pay-per-request data services, paying in USDC on Base with x402.
Related MCP Servers
- AlicenseAqualityDmaintenanceSearch 14,000+ x402-enabled HTTP APIs by keyword. Agents pay $0.01 USDC per search via x402 micropayments on Base mainnet — no API keys or accounts required.142 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to call 93 pay-per-call machine-to-machine services spanning web scraping, crypto sentiment, market data, on-chain analytics, social and threat intelligence, vulnerability scanning, and micro-SaaS utilities. Payments are settled in USDC on Arbitrum via the x402 protocol using a wallet header, so no API keys, signups, or billing setup are required.MIT
- AlicenseNot gradedqualityCmaintenancePay-per-call AI microservices settled in USDC on Base via the x402 (HTTP 402) protocol. 28 tools including web search, summarization, extraction, code review, deep research, crypto safety, sanctions screening and on-chain data — no accounts or API keys.4 npmApache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search and verify machine-payable HTTP 402/x402 APIs using live probe data, providing ranked results by liveness, uptime, price, and trustworthiness.-
Glama MCP Gateway
Add one secure layer between your agents and this server.