agentfeed-algo

A paid x402 data API on Algorand. It sells a cross venue liquidation tape per call in USDC, and it tells you when it does not know.

Built for the Algorand Foundation Global x402 Challenge.

Live on Algorand mainnet

https://algo.ochinimus.app

network   algorand:wGHE2Pwdvd7S12BL5FaOP20EGYesN73k
asset     USDC, ASA 31566704
facilitator  https://facilitator.goplausible.xyz
catalog   https://algo.ochinimus.app/catalog
manifest  https://algo.ochinimus.app/.well-known/x402

Free to inspect, paid to read. Call any route without payment and you get a 402 carrying the price, the asset and what the payment unlocks. The tape behind it currently covers around 710 symbols and 50,000 liquidation rows per day across Binance, Bybit and OKX.

What it sells

Four endpoints, priced in USDC, paid per request over x402 with no account, no API key and no signup.

Liquidation volume for one symbol over a window, split by exchange and by whether longs or shorts were liquidated, at 0.02 USDC. A cascade score, which measures whether that volume arrived as a single burst or spread evenly, at 0.05. The full symbol universe the tape saw in a window, so a caller can tell coverage from silence, at 0.10. Per exchange reporting integrity, at 0.03.

Calling every route once costs 0.2 USDC. That number is computed from the catalog, not typed into the README, so it cannot drift.

Global x402 Challenge qualification

Entered as a Composite project: four endpoints under one project sharing a single payTo address.

Every route carries the required x402-global-challenge tag and declares a Bazaar discovery extension, so an agent that has never heard of this service can find it, read what each route costs, and construct a valid request from the listing alone. Both are applied in compileCatalog and buildRoutes rather than written per route, so neither can be forgotten on one endpoint, and there are tests asserting all four carry them.

Settlement runs through the GoPlausible facilitator on Algorand mainnet. Two payments have completed end to end.

Use it from an agent

The endpoint is a URL, which is invisible to the thing meant to pay for it. So this ships an MCP server too.

npx -y @seekdaseek/agentfeed-algo-mcp

Or in an MCP client config, as a server named agentfeed-algo running npx -y @seekdaseek/agentfeed-algo with the binary agentfeed-algo-mcp, and one environment variable, ALGO_PAYER_MNEMONIC, holding the mnemonic for an Algorand account that has USDC and is opted in to asset 31566704.

Six tools. Four paid, one per route. Two free: catalog lists everything sold and what it costs, and payer_status reports your balances and anything blocking payment. Both work with no key at all, so you can install this, look at what exists, and decide afterwards whether to fund anything.

Payment comes from your own account. There is no key of ours in the loop and no account to create.

An unmeasured response comes back as a tool error rather than as data. The HTTP layer already refuses to bill it, but an agent reading a tool result needs the same signal, and a hole that looks like an answer is worse than no answer.

The thing that makes it worth paying for

Every response carries its own status, and there are three of them.

Measured means we asked and got an answer.

Absent means we asked and the market had none. No liquidations in the window is a real finding about a quiet market, and a buyer can act on it.

Unmeasured means our own lookup failed. A rate limit, a locked database, a query that threw. This is not a finding, it is the absence of one.

An unmeasured response returns 503 and is never billed, even though payment was already verified by the time we find out. That costs us the sale on purpose. Once an agent is paying per call, the worst product you can sell is a zero you invented, because the caller has no way to tell it from a real one. A feed that says when it does not know is worth mor

... View full README on GitHub