AgentFeed MCP server
Commit Nov 14, 2026Provides crypto market data, Solana pre-trade checks, and NLP utilities for AI agents via the x402 payment protocol.
Also known as seekdaseek/agentfeed
- Stars
- 0
- Tools
- 102
- Downloads, 30 days
- —
- Latest version
- 2.12.0
- Last commit
- Nov 14, 2026
- License
- MIT
What is AgentFeed MCP?
AgentFeed provides crypto market data, Solana pre-trade checks, and NLP utilities for AI agents via the x402 payment protocol. It exposes 102 tools, such as get_morning_brief, get_move_alert, get_anomaly_flag.
Summary generated from the project's README
About AgentFeed MCP server
AgentFeed provides a specialized suite of tools for AI agents to access live cryptocurrency market data and perform linguistic tasks. It offers unique access to a continuous liquidation tape from Bybit, OKX, and Binance, which includes historical data that is no longer publicly available from those exchanges. Developers can use this server via MCP-native frameworks like Claude and Cursor, or through standard HTTP requests.
Transactions are handled through the x402 payment protocol, allowing agents to pay per call using USDC or native network tokens. This system requires no accounts or subscriptions, though prepaid keys are available for bots unable to use x402. The service supports multiple networks including Solana, Base, Polygon, Arbitrum, and others. Beyond market data like open interest and funding rates, the server includes utilities for OCR, translation, summarization, and OFAC sanctions screening.
What you can do with it
- 1Analyze historical liquidation dataAn AI agent can query the continuous liquidation tape to study market cascades across major exchanges.
- 2Execute NLP utility tasksAn agent can be tasked with summarizing text, translating languages, or extracting specific data points from documents.
Written from the project's README. Every use case is checked against a quote from it.
How to install AgentFeed MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall AgentFeed MCP in Claude Code
$ claude mcp add --transport http agentfeed https://x402.ochinimus.app/mcpInstall AgentFeed MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"agentfeed": {
"url": "https://x402.ochinimus.app/mcp"
}
}
}Install AgentFeed MCP in VS Code
.vscode/mcp.json
{
"servers": {
"agentfeed": {
"type": "http",
"url": "https://x402.ochinimus.app/mcp"
}
}
}Install AgentFeed MCP in VS Code CLI
$ code --add-mcp '{"name":"agentfeed","type":"http","url":"https://x402.ochinimus.app/mcp"}'Install AgentFeed MCP in Codex
$ codex mcp add agentfeed --url https://x402.ochinimus.app/mcpInstall AgentFeed MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.agentfeed] url = "https://x402.ochinimus.app/mcp"
Install AgentFeed MCP in Gemini CLI
$ gemini mcp add -s user --transport http agentfeed https://x402.ochinimus.app/mcpInstall AgentFeed MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"agentfeed": {
"url": "https://x402.ochinimus.app/mcp",
"type": "http"
}
}
}AgentFeed MCP tools 102
Detected from the READMEget_morning_briefget_move_alertget_anomaly_flagget_squeeze_scoreget_liq_historyget_liq_heatmapget_cascade_historyget_venue_liq_shareget_cascade_forecastget_peg_universeget_peg_sessionsget_peg_deviation
Show all 102 toolsShow fewer tools
get_exit_methodget_exit_quoteget_recent_liquidationsget_cascade_alertget_cascade_scanget_liquidation_leadersget_liquidation_statsget_liq_pulseget_liq_feedget_funding_radarget_market_stateget_funding_extremesget_open_interestget_oi_spike_scanget_basisget_volatilityget_funding_historyget_top_moversget_perpget_funding_pulseget_orderbook_imbalanceget_orderbook_wallsget_spotget_sol_priceget_btc_priceget_eth_priceget_funding_rateget_market_snapshotget_positioningget_trade_contextget_hl_whalesget_wallet_holdingsget_token_metadataget_token_riskget_token_holdersget_wallet_activityget_priority_feesget_jito_tipsget_sol_networkget_sol_token_checkget_sol_token_flowget_sol_holder_clustersget_base_gasget_base_balanceget_honeypot_checkget_base_launchesget_sec_filingsget_insider_tradesget_sec_8kget_web_markdownget_pdf_markdownget_macro_calendarget_fx_ratesget_tradfi_radarget_equity_24hget_tradfi_perpsget_sanctions_checkget_email_verifyget_domainget_papersget_paperget_wikiget_qrget_hashget_timeget_convertget_pkg_checkget_tx_precheckget_company_checkget_rwa_yieldsget_x402_lintget_x402_testget_claim_checkget_site_signalsget_cascade_backtestget_ocrget_summarizeget_extractget_translateget_classifyget_injection_checkget_transcribeget_signal_boardget_coin_signalget_fear_greedget_last_liquidationget_cascade_forecast_freeget_forecast_questionget_forecast_recordpricing
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableseekdaseek/agentfeed is public and reachablegithub.com/seekdaseek/agentfeed ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-14github.com/seekdaseek/agentfeed ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model102 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 98 msPass
README
View on GitHubAgentFeed
Crypto market data for AI agents (liquidations, funding, open interest, prices), Solana pre-trade checks, OFAC sanctions screening, scholarly papers, utilities and fixed-purpose language tasks (OCR, translate, summarize, extract, classify, prompt-injection check, transcribe). Pay per call in USDC. No accounts, no subscriptions, and no API key needed (prepaid keys are optional, for bots that cannot pay x402).
AgentFeed sells live trading data through the x402 payment protocol on Solana, Base, Polygon, Arbitrum, Arc, Optimism, Monad and Avalanche, and on request on Celo, HyperEVM, Unichain, Scroll, SKALE Base, BNB Chain, Ethereum, Robinhood Chain, World Chain, Sei and X Layer (GET /api/<route>|<network>). An agent hits an endpoint, gets a 402 Payment Required with the price, pays a fraction of a cent in USDC (or the dollar token the network names) from its own wallet, and receives the data — in about two seconds, gas sponsored by the facilitator.
Two rails, same data:
| Rail | Endpoint | For |
|---|---|---|
| MCP (Streamable HTTP) | https://x402.ochinimus.app/mcp |
Claude, Cursor, MCP-native frameworks |
| HTTP (x402) | https://x402.ochinimus.app/api/* |
Anything that speaks HTTP |
What makes this different: the liquidation tape
We run our own liquidation collector across Bybit, OKX and Binance — every USDT-margined perpetual on all three, recorded continuously since 2026-07-08.
The size of that tape is not a claim, it is a query. Measured 2026-09-28 06:56 UTC:
| Rows | 4,924,729 |
| Distinct perp markets, whole tape | 907 |
| Distinct perp markets, last 7 days | 861 — binance 728 · bybit 693 · okx 454 |
| Range (UTC) | 2026-07-08 16:42:32 → 2026-09-28 06:56:17 |
It grows while you read this: the row count above and the one you get from the same query five minutes later will not match.
The 7-day figure is published live by the service itself at
/ under coverage.perp_markets_7d, recomputed from the tape
rather than restated, so this README can be checked against it rather than believed.
This data cannot be bought. Not from us, not from anyone:
- Binance deleted their liquidation archive.
liquidationSnapshotno longer exists ondata.binance.vision— the directory is an empty shell. Verified 2026-07-12. - Bybit has never published historical liquidation data.
- OKX offers a 7-day rolling REST window and nothing more.
There is no public historical liquidation dataset for any major venue, at any price. The only way to hold this data is to have been recording it.
And here is exactly where our data is weak
Being straight about this matters more than the marketing:
| Venue | Feed | Complete? |
|---|---|---|
| Bybit | allLiquidation |
✅ Yes. Every liquidation, 500ms cadence. The only complete, unthrottled public liquidation stream among the major perp venues. |
| Binance | !forceOrder@arr |
❌ No. Snapshot only — max one order per symbol per 1000ms, per Binance's own docs. allForceOrders REST is unmaintained. |
| OKX | liquidation-orders |
❌ No. Max one update per second per contract. |
| Hyperliquid | — | ⛔ Not included. Hyperliquid exposes no public liquidation stream. WsTrade carries no liquidation marker; the data lives only in user-scoped streams. Capturing it requires running a node. |
Binance and OKX rows are a structural undercount, and the undercount is worst during cascades — exactly when the data matters most. This is true of every liquidation dataset on the market, including the well-known ones. Most don't say so.
Bybit rows are the highest-integrity part of the dataset. Weight accordingly.
The side field, which most datasets get wrong
Three exchanges, three conventions. We normalize all of them:
- Bybit
Sis already the position side (Buy= a long was liquidated). Passed through. - Binance
Sis the order side — aSELLorder is what closes a long. Flipped. - OKX exposes
posSideexplicitly. Mapped.
In our output: Buy = a LONG was liquidated. Sell = a SHORT was liquidated. Invert this
and every long/short ratio you compute is backwards for some venues.
Notional uses filled_qty × avg_fill_price — what actually executed — not limit_price × requested_size.
Price index
Every paid route, cheapest question last. Generated from
/.well-known/x402.json,
read 2026-11-01 — names, prices and routes are the manifest's, not a copy kept
in sync by hand. What each one returns is under
102 tools, word for word as
the service publishes it.
| Tool | Price | Route |
|---|---|---|
buy_key_pass |
$25 | /api/keys/buy-pass |
buy_key_signals_pass |
$25 | /api/keys/buy-signals-pass |
buy_key_20 |
$20 | /api/keys/buy-20 |
topup_key_20 |
$20 | /api/keys/topup-20 |
buy_key_5 |
$5 | /api/keys/buy-5 |
topup_key_5 |
$5 | /api/keys/topup-5 |
buy_key_1 |
$1 | /api/keys/buy-1 |
buy_key_day_pass |
$1 | /api/keys/buy-day-pass |
buy_key_signals_day_pass |
$1 | /api/keys/buy-signals-day-pass |
get_x402_test |
$1 | /api/x402-test |
get_cascade_backtest |
$0.5 | /api/cascade-backtest |
buy_key_trial |
$0.25 | /api/keys/buy-trial |
get_company_check |
$0.25 | /api/company-check |
get_claim_check |
$0.15 | /api/claim-check |
get_squeeze_score |
$0.1 | /api/squeeze-score |
get_cascade_scan |
$0.05 | /api/cascade-scan |
get_liq_history |
$0.05 | /api/liq-history |
get_peg_universe |
$0.05 | /api/peg-universe |
get_tx_precheck |
$0.05 | /api/tx-precheck |
get_x402_lint |
$0.05 | /api/x402-lint |
get_ocr |
$0.04 | /api/ocr |
get_translate |
$0.04 | /api/translate |
get_cascade_history |
$0.03 | /api/cascade-history |
get_morning_brief |
$0.03 | /api/morning-brief |
get_peg_sessions |
$0.03 | /api/peg-sessions |
get_extract |
$0.025 | /api/extract |
get_sol_token_check |
$0.025 | /api/sol-token-check/{mint} |
get_anomaly_flag |
$0.02 | /api/anomaly-flag |
get_base_launches |
$0.02 | /api/base-launches |
get_cascade_forecast |
$0.02 | /api/cascade-forecast |
get_exit_quote |
$0.02 | /api/exit-quote |
get_funding_extremes |
$0.02 | /api/funding-extremes |
get_funding_radar |
$0.02 | /api/funding-radar |
get_hl_whales |
$0.02 | /api/hl-whales |
get_liq_heatmap |
$0.02 | /api/liq-heatmap |
get_liquidation_leaders |
$0.02 | /api/liquidation-leaders |
get_market_state |
$0.02 | /api/market-state |
get_move_alert |
$0.02 | /api/move-alert |
get_oi_spike_scan |
$0.02 | /api/oi-spike-scan |
get_peg_deviation |
$0.02 | /api/peg-deviation |
get_pkg_check |
$0.02 | /api/pkg-check |
get_rwa_yields |
$0.02 | /api/rwa-yields |
get_site_signals |
$0.02 | /api/site-signals |
get_summarize |
$0.02 | /api/summarize |
get_token_holders |
$0.02 | /api/token-holders/{mint} |
get_tradfi_radar |
$0.02 | /api/tradfi-radar |
get_transcribe |
$0.02 | /api/transcribe |
get_venue_liq_share |
$0.02 | /api/venue-liq-share |
get_wallet_activity |
$0.02 | /api/wallet-activity/{wallet} |
get_papers |
$0.015 | /api/papers |
get_basis |
$0.01 | /api/basis |
get_cascade_alert |
$0.01 | /api/cascade |
get_equity_24h |
$0.01 | /api/equity-24h |
get_honeypot_check |
$0.01 | /api/honeypot-check |
get_insider_trades |
$0.01 | /api/insider-trades |
get_liquidation_stats |
$0.01 | /api/liquidation-stats |
get_open_interest |
$0.01 | /api/open-interest |
get_orderbook_imbalance |
$0.01 | /api/orderbook-imbalance |
get_orderbook_walls |
$0.01 | /api/orderbook-walls |
get_pdf_markdown |
$0.01 | /api/pdf-markdown |
get_sec_8k |
$0.01 | /api/sec-8k |
get_signal_board |
$0.01 | /api/signal-board |
get_token_risk |
$0.01 | /api/token-risk/{mint} |
get_top_movers |
$0.01 | /api/top-movers |
get_trade_context |
$0.01 | /api/trade-context |
get_volatility |
$0.01 | /api/volatility |
get_sanctions_check |
$0.008 | /api/sanctions-check/{address} |
get_sol_holder_clusters |
$0.008 | /api/sol-holder-clusters/{mint} |
get_sol_token_flow |
$0.008 | /api/sol-token-flow/{mint} |
get_wallet_holdings |
$0.008 | /api/wallet-holdings/{wallet} |
get_base_balance |
$0.005 | /api/base-balance |
get_base_gas |
$0.005 | /api/base-gas |
get_classify |
$0.005 | /api/classify |
get_convert |
$0.005 | /api/convert |
get_domain |
$0.005 | /api/domain/{domain} |
get_email_verify |
$0.005 | /api/email-verify |
get_funding_history |
$0.005 | /api/funding-history |
get_funding_pulse |
$0.005 | /api/funding-pulse |
get_funding_rate |
$0.005 | /api/funding-rate |
get_hash |
$0.005 | /api/hash |
get_jito_tips |
$0.005 | /api/jito-tips |
get_liq_pulse |
$0.005 | /api/liq-pulse |
get_macro_calendar |
$0.005 | /api/macro-calendar |
get_market_snapshot |
$0.005 | /api/market-snapshot |
get_paper |
$0.005 | /api/paper/{doi} |
get_perp |
$0.005 | /api/perp |
get_positioning |
$0.005 | /api/positioning |
get_priority_fees |
$0.005 | /api/priority-fees |
get_qr |
$0.005 | /api/qr |
get_recent_liquidations |
$0.005 | /api/liquidations |
get_sec_filings |
$0.005 | /api/sec-filings |
get_sol_network |
$0.005 | /api/sol-network |
get_time |
$0.005 | /api/time |
get_token_metadata |
$0.005 | /api/token-metadata/{mint} |
get_tradfi_perps |
$0.005 | /api/tradfi-perps |
get_web_markdown |
$0.005 | /api/web-markdown |
get_wiki |
$0.005 | /api/wiki |
get_coin_signal |
$0.004 | /api/coin-signal/{coin} |
get_injection_check |
$0.004 | /api/injection-check |
get_fx_rates |
$0.002 | /api/fx-rates |
get_btc_price |
$0.001 | /api/btc-price |
get_eth_price |
$0.001 | /api/eth-price |
get_liq_feed |
$0.001 | /api/liq-feed |
get_sol_price |
$0.001 | /api/sol-price |
get_spot |
$0.001 | /api/price |
Two payment protocols on one 402
Every paid route answers 402 with an x402 v2 challenge in the PAYMENT-REQUIRED header, and
the same challenge as an x402 v1 body ({x402Version: 1, accepts}) for Base and Solana. Pay with
PAYMENT-SIGNATURE (v2, any rail) or X-PAYMENT (v1 on Base or Solana, verified and settled
through the CDP facilitator's v1 kinds; Polygon and Arbitrum have no v1 kind there and stay v2).
Eight networks are in every 402 and eleven more are offered on request (see "Pay on any chain"); Algorand is built but switched off, see "Algorand is switched off" below. Each network is settled by
exactly one facilitator: CDP for Solana, Base, Polygon, Arbitrum and World Chain; Circle's Facilitator Service for Arc, to a
dedicated Arc address; GoPlausible for Algorand (switched off); Ultravioleta for Optimism, Monad, Avalanche, Celo, HyperEVM, Unichain, Scroll,
SKALE Base, BNB Chain, Ethereum and Robinhood Chain; PayAI for Sei and X Layer. payments.js gives each facilitator client only
its own networks, so a payment on one network can never reach another's facilitator.
Every paid route also carries MPP tempo/charge challenges in WWW-Authenticate (Tempo
mainnet, chain 4217, OUSD first, then USDC.e, at the route's price; no fee payer, the payer pays
gas). Only signed transactions (pull mode) are accepted: the server validates the transfer, runs
the request, and broadcasts it only when the response is below 400, so a failed call is never
charged; an already-broadcast hash credential is refused. /api/sol-price and /api/btc-price
additionally carry an MPP solana/charge challenge. All of them ride the same response, so
a client settles with whichever protocol it speaks. The two live in disjoint header namespaces, so an x402-only client never sees the MPP
one and is unaffected.
$ curl -si https://x402.ochinimus.app/api/btc-price # 2026-09-23 09:18:09 UTC
HTTP/2 402
payment-required: eyJ4NDAyVmVyc2lvbiI6MiwiZXJyb3IiOiJQYXltZW50IHJlcXVpcmVkIiwi…
www-authenticate: Payment id="T0-lA4BfXXpf3GvzGklT8YobRJwSlEu8AXu9ZLz5VOg",
realm="x402.ochinimus.app", method="solana", intent="charge",
request="eyJhbW91bnQiOiIxMDAwIiwiY3VycmVuY3ki…",
expires="2026-09-23T09:23:09.919Z", opaque="eyJfbXBweF9zY29wZSI6…"
Base64-decoded, that MPP request is the whole quote:
{
"amount": "1000",
"currency": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
"recipient": "4a8o45skRPcyjAdyR8yES215Swvh8uTpZD6KLarhxCJ7",
"methodDetails": {
"decimals": 6,
"network": "mainnet",
"recentBlockhash": "6e6NEAxddHca5ipHioSwZRhcGcSL4rW4q18AYszfnxyv",
"tokenProgram": "TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA"
}
}
Note what is not there: no feePayer. The client pays its own transaction fee and the
server holds no funded signing key, which is the difference between the MPP challenge and the
Solana x402 one sitting beside it in the same response.
Replay is refused, not merely discouraged. A settled signature is claimed atomically in SQLite before the resource is served, so two processes racing the same credential produce exactly one 200 and one refusal — covered by tests that fork real worker processes rather than stubbing the race.
The layer is fail-soft by design. If it cannot initialise it logs [mpp] DISABLED: <cause>
and the service keeps serving x402 on every route rather than taking the paid surface down
with it. Which routes are gated is published live at / and in /.well-known/x402.json under
mpp.routes, so the advertised set is always whatever is actually mounted.
AgentFeed is one of several merchants accepting MPP on Solana mainnet — the Foundation's own
Google proxy and smartmoney-market in solana-foundation/pay-skills do too.
Upstream work this produced
solana-foundation/pay-kit #328 |
fix(mpp): send preflightCommitment with sendTransaction so confirmed-only blockhashes are accepted — a challenge blockhash minted at confirmed is rejected by a preflight bank that defaults to finalized, so a client that pays fast always fails. Open, approved, 44/44 checks green, mergeable/clean (read 2026-09-23) |
solana-foundation/surfpool #813 |
fix(core): make blockhash handling honor commitment and preflightCommitment — merged 2026-09-21 by MicaiahReid, opened by EfeDurmaz16, who had reviewed #328. Its description explains why the bug above was invisible in CI: "This hid a deterministic mainnet failure from pay-kit's Surfpool CI: solana-foundation/pay-kit#328." A sandbox that stamped an always-valid blockhash could not reproduce a finality race that mainnet reproduces every time |
solana-foundation/pay-skills #260 |
providers: add ochinimus/agentfeed |
solana-foundation/pay #469 |
pay hangs forever on paid routes in non-GUI contexts: the Touch ID gate polls for a prompt that cannot render |
The pay-kit fix ships here as mpp/patches/@solana+mpp+0.7.0.patch, applied by
patch-package on install and asserted by npm run verify-patch — the patch is a production
dependency, not a dev one, because a --omit=dev install would otherwise complete silently
unpatched.
Half price for high-frequency callers
A bot that calls often pays half the route's price, minimum $0.0005, through either of two schemes that ride the same 402 as the per-call accepts. Per-call prices do not change. The six prepaid-key purchase routes carry per-call accepts only. The Gateway accept is offered on Arc only: it was withdrawn from Base, Polygon and Arbitrum on 18 Oct 2026, because buyers whose client picked it as the cheapest accept of the chain signed a plain USDC authorization to the Gateway wallet, which is not a Gateway payment and was refused.
| batch-settlement | Circle Gateway nanopayment | |
|---|---|---|
| Networks | Base, Polygon, Arbitrum | Arc |
| Accept | scheme: batch-settlement |
scheme: exact, extra.name: GatewayWalletBatched |
| Pays | the treasury 0x22DB3A9686EE5261e7Bf3ed4f91277232E8076e6 |
Gateway seller 0xA853129ACF56A851f9d51CD8cb47619465260Fa9 |
| Buyer does once | opens a channel with one deposit (extra.minDeposit in the accept); every later call is an off-chain voucher |
deposits USDC into the GatewayWallet 0x77777777Dcc4d5A8B6E418Fd04D8997ef11000eE |
| Settlement | we claim the vouchers every 30 minutes | Circle batches the authorizations |
| Unspent money | comes back through the channel's timed withdrawal (24 h delay) | stays in the buyer's Gateway balance |
A call that answers 400 or more is never charged on either scheme.
Path parameters
Twelve routes take their argument as the last path segment: /api/wallet-activity/{wallet}, /api/token-risk/{mint}, /api/coin-signal/{coin},
/api/sanctions-check/{address}, /api/domain/{domain}, /api/paper/{doi} and the other six. In this README, in llms.txt and in
openapi.json, {wallet} marks the part you replace; it is not a URL. Every URL the service publishes for a caller to GET is a working example
instead: /.well-known/x402.json lists
https://x402.ochinimus.app/api/wallet-activity/Gack9UtqfeZxFA1LqeqjLgC3JGuD7rS6CsSHKoXsD4Tu as the resource and the {wallet} form as
resource_template; openapi.json gives each path parameter an example and the pattern, minLength and maxLength it must satisfy; the 402's Bazaar
declaration carries the same schema. The DOI example is published as one segment, /api/paper/10.1038%2Fnature14539 (the URL CDP's index already holds for this route); the
slash spelling /api/paper/10.1038/nature14539 is still served. CDP's /validate fails this one route on bazaar.routeTemplate.matches_resource with either spelling (it
behaves as if it decodes the path before splitting it, and a DOI always contains a slash); the other 90 priced routes validate. The existing ?doi= alias fails it too (measured: its 402 still names the template /api/paper/:doi); only a priced route whose template has no DOI in the path would pass, which is a route redesign and an open decision.
Trade-off, decided 29 Oct 2026: the catalogue lists these concrete example URLs, not the {wallet} templates. A directory that keys its listing on the URL
(Agent402 does) may therefore show a route twice, once from the catalogue and once from the 402's own route template. That is cosmetic. A listed URL that answers
400 is broken, which is what the literal templates were. To go back, change the concrete line in buildWellKnown (tools/discovery.js).
A value that can never be served is refused before the paywall. GET /api/wallet-activity/:wallet and GET /api/wallet-activity/notawallet answer
400 with the reason, the shape expected, a working example URL and "charged": false: no 402, no challenge, no prepaid-key reserve, nothing sent to a
facilitator (lib/param-guard.js, before every payment layer). The check is shape only and uses the validator the handler itself uses: a Solana wallet or
mint is 32 to 44 base58 characters, a coin 1 to 20 letters or digits, an address 14 to 120 letters and digits, a domain a public hostname, a DOI
10.xxxx/.... Whether the address has an account, the coin is listed or the DOI exists is still answered after payment, and a call that then answers 400 or
more is never settled on any rail (test/param-guard-real-server.test.js). Over MCP the same patterns are in each tool's input schema, so an impossible
argument is rejected before the payment prompt. MPP solana/charge settles on chain before the handler runs, so it is offered only on the two routes that take
no input (/api/sol-price, /api/btc-price); MPP tempo/charge and every x402 scheme settle after it.
Query parameters are checked before payment (R20f, 29 Oct 2026)
The same guard covers the values of query parameters that a route's handler would refuse with a 400 anyway: an integer outside its range
(/api/sol-token-flow/{mint}?swaps=5 needs 20 to 100), a word outside its list (?alg=md5, ?format=jpeg, ?length=long, ?class=bonds), a code of the wrong
shape (?base=EURO, ?lang=english, a 0x address that is not 40 hex digits), a url= that is not an absolute http or https URL (?url=example.com), a text or
data over the route's length cap (4,000 characters; 2,048 bytes), a schema= that is not the JSON object the route needs. Such a request answers 400 with error, param, expected, received,
a working example URL and "charged": false, before any 402 (lib/query-rules.js, mounted by lib/param-guard.js). The rules copy the handler's own checks and
read a value the way the handler does (Number() on the raw text, words lower-cased, an empty value is "not given"); test/query-guard-real-server.test.js runs the real
server twice, with the rules on and off, and requires that every value the guard refuses is refused by the handler with the same sentence. Not guarded, on purpose:
a missing parameter (the query-less URL of each route is the one every catalogue lists, and it stays a 402), symbols and tickers that need an upstream to be judged
(Hyperliquid's universe, the SEC list), URLs and free text, and limits the handler clamps instead of refusing (limit on /api/liquidations, window on
/api/cascade, and others). 52 rules on 30 routes today; the full list is lib/query-rules.js. The integer and number ranges are also in each MCP tool's input schema and in the minimum / maximum of openapi.json and of
the Bazaar declaration. AF_QUERY_GUARD=off in the environment (restart) switches the query rules off and leaves the path rules on.
Algorand is switched off (29 Oct 2026)
X402_ALGO=off is set on the live box. CDP's Bazaar validator (POST https://api.cdp.coinbase.com/platform/v2/x402/validate) parses every accept of a route, and a network id
outside the CAIP-2 grammar (namespace:reference, the reference 1 to 32 characters of [-_a-zA-Z0-9]) fails its required check parse; the whole route is then
rejected: invalid discovery configuration (measured on all 91 priced routes). The Algorand id that the GoPlausible facilitator publishes,
algorand:wGHE2Pwdvd7S12BL5FaOP20EGYesN73ktiC1qzkkit8=, is 44 characters with a trailing =. With the rail off 90 of the 91 routes validate (valid: true, simulation accepted, 25
of 25 checks pass); the 91st, /api/paper/{doi}, fails only bazaar.routeTemplate.matches_resource (see "Path parameters"). No payment was ever made on Algorand. The code stays (lib/rails.js); to offer the rail again, remove the line and restart, once CDP accepts the id
or the facilitator publishes a CAIP-2 one. test/caip2-networks.test.js fails if any other network id leaves the grammar.
AgentFeed MCP questions
How do I add AgentFeed MCP to Claude Code?
Run claude mcp add --transport http agentfeed https://x402.ochinimus.app/mcp in your terminal. Add --scope user to make it available in every project.
How do I add AgentFeed MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does AgentFeed MCP provide?
It exposes 102 tools, including get_morning_brief, get_move_alert, get_anomaly_flag, get_squeeze_score, get_liq_history.
How do I pay for the data?
Data is paid per call in USDC using the x402 payment protocol. An agent hits an endpoint, receives a 402 Payment Required response with the price, and pays from its own wallet.
Do I need an API key or a subscription?
No accounts, subscriptions, or API keys are required, though prepaid keys are an optional feature for bots that cannot handle 402 errors.
What kind of liquidation data do you provide?
The service runs a continuous liquidation collector across Bybit, OKX, and Binance, providing normalized data for all USDT-margined perpetuals.
Which networks are supported for payment?
Payments are supported on Solana, Base, Polygon, Arbitrum, Arc, Optimism, Monad, and Avalanche, with more available on request.