APIbase
# APIbase.pro — The API Hub for AI Agents
Production MCP server: one endpoint gives AI agents access to 1388 tools from 397 providers, pay-per-call via x402 (USDC on Base) or MPP (USDC on Tempo).
[](https://github.com/whiteknightonhorse/APIbase/actions/workflows/security.yml)
[](https://github.com/whiteknightonhorse/APIbase/actions/workflows/deploy.yml)
[](https://opensource.org/licenses/MIT)
[](https://registry.modelcontextprotocol.io)
[](https://smithery.ai/servers/apibase-pro/api-hub)
[](https://www.mppscan.com/server/2ce70c5f97be51cfcabe13aad9b5f4beae6dc77be586357e04db17644729303d)
---
## Quick Start
```json
{
"mcpServers": {
"apibase": { "url": "https://apibase.pro/mcp" }
}
}
```
That's the Claude Desktop config. Cursor, Windsurf, OpenAI Agents SDK, LangChain, Google ADK, CrewAI, Microsoft Copilot Studio, and plain REST: **[apibase.pro/connect](https://apibase.pro/connect)**.
---
## For AI Agents
- **[llms.txt](https://apibase.pro/llms.txt)** — concise LLM context
- **[ai.txt](https://apibase.pro/ai.txt)** — plain-text agent discovery
- **[mcp.json](https://apibase.pro/.well-known/mcp.json)** — MCP server metadata
- **[openapi.json](https://apibase.pro/.well-known/openapi.json)** — OpenAPI 3.1 spec
- **[api-catalog](https://apibase.pro/.well-known/api-catalog)** — RFC 9727 discovery linkset
---
## Integrations & Registries
**[Full framework guides →](https://apibase.pro/frameworks)**
Registry listings: [Smithery](https://smithery.ai/servers/apibase-pro/api-hub) · [Glama](https://glama.ai/mcp/servers/whiteknightonhorse/APIbase) · [MCP Registry](https://registry.modelcontextprotocol.io) (`io.github.whiteknightonhorse/apibase`) · [PulseMCP](https://pulsemcp.com) · [MPPScan](https://www.mppscan.com)
---
## Self-Hosting
```bash
git clone https://github.com/whiteknightonhorse/APIbase.git && cd APIbase
cp .env.example .env # set POSTGRES_PASSWORD, X402_PAYMENT_ADDRESS, provider keys
docker compose -f docker-compose.yml -f docker-compose.prod.yml up -d
```
Full prerequisites, verification steps, and config reference: [`docs/self-hosting.md`](docs/self-hosting.md).
---
## Architecture
Single Node.js/TypeScript API server, PostgreSQL as the append-only financial source of truth, Redis for cache/rate-limiting only, multi-container Docker stack on one Hetzner server. Every tool call runs the same multi-stage pipeline (escrow-first, idempotent, fail-closed, content-moderated) — dual-rail payments (self-hosted x402 facilitator + MPP), error-code contract, and full container/pipeline detail (exact counts, live): [`docs/architecture.md`](docs/architecture.md).
## License
[MIT](LICENSE)
TDQS
Scored across 618 tools
Tools are organized by domain and subdomain, with clear, specific names (e.g., weather.weatherapi.current vs. noaa.weather.observation). Even similar tools have distinct sources and descriptions, making them easy to differentiate.
All tools follow a consistent dot-separated hierarchy (domain.subdomain.action) with no mixed naming conventions. Patterns like address.geocodio.geocode and weather.airnow.current_zip are uniform across the entire set.
With 618 tools, the server is far beyond the typical well-scoped range of 3-15. While it serves as a broad API aggregator, the sheer volume makes it unwieldy and hard to navigate for most use cases.
The tool set covers an extensive range of domains (weather, finance, health, travel, etc.) with deep data for many. Minor gaps exist (e.g., limited social media platforms), but overall it is surprisingly comprehensive for a single server.