APIbase

What whiteknightonhorse/APIbase MCP server does

whiteknightonhorse/APIbase MCP server presents a unified MCP interface for calling external API services. Its documented catalog covers 1,378 tools from 395 providers, while the supplied tool list describes the control layer used to discover endpoints, inspect schemas, execute requests, and manage payments. Example API areas mentioned in the listing include travel, prediction markets, crypto, and weather.

The central fetch tool sends HTTP requests with authentication and payment handling. It can retry a request after a SIGN-IN-WITH-X challenge and pays only when the route continues to return HTTP 402. Results include response data and final headers; when available, payment information includes the price, transaction hash, and raw receipt proof.

How it works

Before calling an endpoint for the first time in a session, use check_endpoint_schema. It returns the origin's input and output schema plus its stated authentication mode. A sample request body can optionally be used to probe an endpoint without payment and obtain a price quote, which is useful for variable or range-based pricing.

discover_api_endpoints lists routes available from an API origin, including descriptions and payment or SIWX guidance. search finds relevant paid services when the required origin is unknown; it should not replace direct discovery when a known registered origin already matches the task. The fetch tool handles both SIWX and paid routes regardless of the advisory auth mode.

Payments use USDC. The wallet is created automatically at ~/.agentcash/wallet.json when balance or account tools are first used. get_balance reports the combined balance across supported networks, while list_accounts provides per-network addresses, balances, and deposit links. bridge moves USDC between supported networks, and sessions_close finalizes an MPP payment channel when given the channel ID and original URL.

Setup and configuration

The hosted configuration is an MCP URL:

{
  "mcpServers": {
    "apibase": { "url": "https://apibase.pro/mcp" }
  }
}

The README lists compatibility guidance for Claude Desktop, Cursor, Windsurf, OpenAI Agents SDK, LangChain, Google ADK, CrewAI, and Microsoft Copilot Studio. Self-hosting uses Docker Compose after cloning the repository, copying .env.example to .env, and setting POSTGRES_PASSWORD, X402_PAYMENT_ADDRESS, and provider keys. The documented production stack uses PostgreSQL, Redis, and a Node.js/TypeScript API server.

Tools and capabilities

• Inspect endpoint schemas and optional live price quotes.
• Discover routes and search for unfamiliar paid API services.
• Execute HTTP requests with SIWX and x402 payment handling.
• View, fund, and bridge wallet balances across supported networks.
• Set a maximum USD amount allowed for each fetch request.
• Redeem invite codes for free USDC on Base.
• Close MPP payment channels and retrieve settlement information.

Limitations and notes

Payment calls require available USDC, and bridging can incur fees. report_error is intended only for critical MCP tool bugs, not ordinary balance, network, or HTTP 4xx errors. Endpoint auth guidance is advisory because fetch handles both SIWX and paid routes. For unfamiliar endpoints, skipping schema inspection can lead to HTTP 400 errors caused by incorrect field names. whiteknightonhorse/APIbase MCP server also persists wallet and settings data locally when using the documented default paths.