Connect in 60 seconds
Three real ways in. Pick the one that matches how your agent already talks to the world.
Path 1 — MCP address no form, ever recommended
Point any MCP-compatible client at one URL. The first tool call auto-issues an ak_live_... key behind the scenes — there is no dashboard signup, no email, no approval queue.
{
"mcpServers": {
"apibase": {
"url": "https://apibase.pro/mcp",
"transport": "streamable-http"
}
}
}
Works in Claude Desktop, Claude Code, Cursor, Windsurf, ChatGPT, OpenAI Agents SDK, LangChain, Google ADK, CrewAI — full per-framework config on /frameworks.
Path 2 — REST + API key one throwaway POST
Get a key with a single unauthenticated request — no name, no email, no plan selection:
curl -X POST https://apibase.pro/api/v1/agents/auto
→ {"agent_id":"...", "api_key":"ak_live_...", "tier":"free"}
Use it on any call:
curl https://apibase.pro/api/v1/tools/crypto.get_price/call \
-H "Authorization: Bearer ak_live_..." \
-H "Content-Type: application/json" \
-d '{"params": {"coins": ["bitcoin"]}}'
Free tools respond immediately. A priced tool without a payment header replies HTTP 402 with a challenge — sign it with either rail below and retry.
Path 3 — bare wallet, zero registration MPP / Tempo
No key, no /agents/auto call, no prior request of any kind. Sign an MPP payment against a Tempo wallet (set up once at wallet.tempo.xyz, via the mppx SDK) and send it as your very first request — the payment itself creates your agent identity, deterministically, from the wallet address:
npm i mppx
import { pay } from "mppx";
const res = await pay("https://apibase.pro/api/v1/tools/crypto.get_price/call", {
network: "tempo",
params: { coins: ["bitcoin"] },
});
No prior call ever touched apibase.pro from this wallet — the first payment IS the signup.
x402 on Base now bootstraps identity from the wallet alone too (as of 2026-09-02) — a signed x402 payment with no prior API key auto-registers your agent exactly like MPP, deterministically keyed to your wallet address. The example above uses MPP because mppx handles the signing for you; the same “first payment is the signup” guarantee now holds for x402/Base too.
Which path should I pick?
- Building an MCP-native agent? Path 1. Zero config beyond the URL.
- Calling from a plain HTTP client or existing backend? Path 2.
- An autonomous agent that should never touch a human onboarding flow, ever? Path 3 — the wallet is the entire identity.