Funding API built for AI agents

What this is

Most data APIs assume a human signed up, picked a plan, rotated a key. Agents don't sign up — they make requests. This API is wired for that: an HTTP 402 returns the payment requirements, the agent signs a USDC transfer on Base via x402, and the data comes back. The same surface ships as an MCP server (@usenami/funding-mcp) so any MCP-aware client gets the endpoints as tools.

• Agent builders shipping autonomous trading or research agents that need fresh funding data per decision cycle.
• Claude / Cursor / ElizaOS users who want funding data as a tool surface without writing a connector.
• Multi-agent swarms where each agent has its own wallet and you bill per agent.
• Researchers running long-running notebooks that occasionally need a snapshot — paying $0.001 beats maintaining a key.

Endpoints

The endpoints below are live on api.usenami.io. Prices are per call in USDC, settled on Base via x402 — no signup, no API key, no monthly minimum. Full spec at /.well-known/x402.json.

Often used alongside (same API, same pricing model):

Quickstart

Claude Desktop / Cursor / ElizaOS: add the MCP server, the funding tools appear automatically. No HTTP plumbing.. The free endpoints (/v1/health, /v1/venues/list, /v1/venues/health, and the preview routes) return without payment so you can validate connectivity before any USDC moves.

// claude_desktop_config.json
{
  "mcpServers": {
    "usenami-funding": {
      "command": "npx",
      "args": ["-y", "@usenami/funding-mcp"]
    }
  }
}

// Then ask the agent:
//   "List the funding spread for BTC, ETH, and HYPE across all venues
//    and skip same-oracle pairs."
//
// Behind the scenes:
//   1. Agent calls funding_spread + oracle_families tools
//   2. MCP server hits /v1/perp/funding-spread and /v1/perp/oracle-families
//   3. x402 layer pays $0.002 total in USDC on Base
//   4. JSON returns, agent reasons over it

What you actually get

The honest disclaimer: x402 is still early — most clients need a wallet that holds a small USDC balance on Base. We support both per-call x402 and a more traditional REST + API-key subscription at /api-docs; pick whichever model fits the agent's life cycle. The same data flows through both.

FAQ