API AND MCP
Receipts for your bots and agents
The same receipts as the boards, over a metered REST API. Every fill is graded at 1h, 24h and 7d, and every answer comes back as JSON your code can act on. Nothing here signs or trades.
Get a key
One call, no email. A free key carries 5,000 credits and 60 requests a minute. The key is shown once and stored only as a hash, so keep it somewhere safe.
curl -X POST https://infomo.app/api/v1/signup \
-H "content-type: application/json" \
-d '{"label":"my-bot"}'Call the API
Send the key in the x-api-key header. Every response carries your balance in x-credits-remaining. A missing or wrong key returns 401, going over the rate returns 429, and an empty balance returns 402. GET /api/v1/me shows what a key has used and what is left.
curl -H "x-api-key: YOUR_KEY" "https://infomo.app/api/v1/receipts?limit=5"Endpoints
| Endpoint | What it returns | Credits |
|---|---|---|
| GET /api/v1/receipts | Scorecards: early rate, hit rates, exit quality, late rate and 30-day PnL | 1 |
| GET /api/v1/fade | The fade index: traders whose buys most often arrive after the move | 1 |
| GET /api/v1/consensus | Coins several well-scored traders bought inside a window | 2 |
| POST /api/v1/copy-sim | Replay copying a trader with your size, minimum buy, stop and target | 2 |
| GET /api/v1/leaderboard | The current fomo leaderboard snapshot | 1 |
| GET /api/v1/traders | Tracked traders ranked by score | 2 |
| GET /api/v1/traders/{handle} | One trader's profile, stats, positions and recent fills | 2 |
| GET /api/v1/trades | Recent fills across tracked traders | 1 |
| GET /api/v1/alerts | The live tape | 1 |
| GET /api/v1/tokens | Coins seen, with their last price | 1 |
| GET /api/v1/token/{pair} | Holders of one coin, with receipts attached | 2 |
| GET, POST, DELETE /api/v1/subscriptions | Webhook or Telegram alerts for this key | 1 |
| GET /api/v1/health | Row counts | 0 |
The full machine-readable spec is at /api/v1/openapi, and a plain-text guide for language models is at /llms.txt.
Alerts
Live alerts come with the holder tier, planned, not live yet. A holder key subscribes a webhook or a Telegram chat with POST /api/v1/subscriptions to Proven trader buys, consensus forming and a watchlist of up to 25 traders (/api/v1/watchlist), lists them with GET, and switches one off with DELETE.
MCP for agents
The MCP server answers questions instead of returning rows, so an agent asks who was early rather than parsing fills. Point any MCP client at https://infomo.app/mcp (Streamable HTTP) and send your key as Authorization: Bearer YOUR_KEY. Tool calls spend credits from the same balance as the API; connecting and listing tools is free.
claude mcp add --transport http infomo https://infomo.app/mcp \
--header "Authorization: Bearer YOUR_KEY"For Cursor and other clients that take a JSON config:
{
"mcpServers": {
"infomo": {
"url": "https://infomo.app/mcp",
"headers": { "Authorization": "Bearer YOUR_KEY" }
}
}
}| Tool | What it answers | Credits |
|---|---|---|
| search_traders | Find graded traders by handle, ordered by receipts score. | 1 |
| trader_receipts | One trader's scorecard: receipts score, early and late rates, hit rates, 30-day PnL and record strength. | 1 |
| grade_call | What the price did after each of a trader's recent fills. | 1 |
| who_was_early | Traders who bought a coin before it rose, ranked by how far it rose in the hour after their buy. | 1 |
| conviction_delta | A trader's buys and sells per coin over the last 30 days: accumulating or distributing. | 1 |
| consensus | Coins several high-scoring traders bought in the same window. | 2 |
| copy_sim | How copying a trader with your rules (size, minimum buy, stop, target) would have played out, fees and slippage included. | 2 |
| fade_index | Traders whose buys most often arrive after the move. | 1 |
What it is not
- Read-only. It never connects a wallet, places an order or holds funds.
- Not investment advice. A score describes past timing, not future returns.
- Not affiliated with FOMO Labs. It reads public trades from fomo.family.