AgentFeed on Algorand MCP server

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:wGHE2Pwdvd7S12BL5FaOP20EGYesN73ktiC1qzkkit8= 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 whose body carries the route, the price, the asset and what the payment unlocks, with the payment challenge itself base64 in the PAYMENT-REQUIRED header. The tape behind it has recorded close to 900 symbols on Binance, Bybit and OKX since July 8 2026, and over the seven full days before September 16 2026 it averaged about 73,000 liquidation rows a day.

What it sells

Five endpoints, priced in USDC, paid per request over x402 with no account, no API key and no signup. They are published under /v2.

The five paths these routes were first published under, the /v1 ones, still answer. Same handlers, same paywall, same prices, each with its own resource URL. An agent holding an old URL is not broken by the move. Nothing advertises /v1 any more, though: the catalog, the manifest, the landing page and the MCP server list only /v2, and nothing new should be built against the old paths.

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.

The fifth route sells history. It returns the complete recorded liquidation history for one symbol across all three exchanges, from that symbol's first observation on this tape through to now, bucketed hourly or daily, at 5.00. No other route here looks back further than seven days, and that is the whole difference: a liquidation record cannot be backfilled after the fact, so depth is the part that is genuinely scarce. Coverage is stated per symbol rather than per tape, because a symbol first appears whenever it first liquidated, which can be weeks after the tape itself began, and the payload carries that symbol's own coverage start so our start date is never mistaken for the market's.

Calling every route once costs 5.2 USDC. The live figure is published at /catalog as sweeppriceusdc and is computed from the catalog rather than typed, so if this line ever disagrees with it, the endpoint is right and this file is stale.

Global x402 Challenge qualification

Entered as a Composite project: five endpoints under one 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 the tests that check them iterate over every route the service answers on rather than sampling one, so a route that lost either would fail the suite.

The tag rides in accepts[].extra, which is where the leaderboard reads it, not in resource.tags. It travels there alongside the asset decimals and the feePayer the facilitator advertises, because ExactAvmScheme merges that extra rather than replacing it.

Shortened. The full README is on GitHub.