What is the current status of the Keryx MCP server payment pilot?
9/20/2026, 5:43:36 PM · llm:deepseek:deepseek-v4-flash
The dispatch, itemised.
Breaking down: "What is the current status of the Keryx MCP server payment pilot?"
Identified 1 research target(s) to investigate; these are not established facts
Deep mode: up to 4 paid/cached reads plus one bounded gap-expansion pass when needed.
Discovered 21 verified source(s)
Recalled 60 past runs on this subject — how these sources performed when they were available.
ERC-8004 reputation loaded — composite scores on this subject.
Claim-aware portfolio selected 1/1 positive proposal(s): 1 cached + 0 fresh, predicting 1/1 claim(s) above the evidence floor with $0.000000/$0.025000 fetch USDC reserved.
Free-preview pre-check maps an actionable source to every sub-claim (1/1); paid reading may proceed within the budget.
First-party Keryx engineering note on paid research jobs, buyer recovery, citation rewards and x402/USDC — the closest match to the Keryx MCP server payment pilot status, and it's full_text (3071 bytes) already cached, so free reuse. Reputation 43/100 with 6 citations on this subject. — selected for the claim-aware evidence portfolio (targets claim 1; 0 fetch USDC, 1 attention slot).
Arc Settlement Benchmarks measures x402 batched-settlement latency on Arc testnet — directly relevant to whether the Keryx MCP payment pilot (x402 on Arc) is live and how it settles. Cached, so reuse is free; lower reputation (16/100) caps value. — cached bytes are free, but this read does not clear the attention gate (EV 0.40, minimum 0.45, with a required claim target).
Web Payments Review covers x402 end-to-end settlement timing, useful background for the pilot's payment rail status. Cached and cheap; reputation only 24/100, so it's supporting color rather than the answer. — cached bytes are free, but this read does not clear the attention gate (EV 0.35, minimum 0.45, with a required claim target).
Agent Economy Weekly explains x402 as an agent payment rail (HTTP 402), the protocol underlying the Keryx MCP payment pilot. Cached, high reputation (47/100, 10 citations), but abstract only and not Keryx-specific. — cached bytes are free, but this read does not clear the attention gate (EV 0.35, minimum 0.45, with a required claim target).
Onchain Micropayments Digest on nanopayment floors and batched settlement is the strongest-reputation source here (59/100) and speaks to the economics of a per-call MCP payment pilot, though it won't state pilot status directly. Cached, free. — cached bytes are free, but this read does not clear the attention gate (EV 0.30, minimum 0.45, with a required claim target).
Stablecoin Ledger's USDC instant-settlement abstract is generic stablecoin background with no Keryx MCP pilot detail; low reputation (12/100) and redundant with the x402-specific cached sources.
Distributed Systems Notes on idempotency keys is generic reliability advice, never cited on this subject (0/100 reputation), and does not address the Keryx MCP payment pilot.
Stripe Blog has good reputation (57/100) but this specific piece is about travel/leisure fraud attempts, unrelated to the Keryx MCP payment pilot; paying $0.002 for an off-topic abstract is not worth it.
Ethereum Foundation protocol priorities abstract is about EF cluster planning, not Keryx's MCP payment pilot or x402 settlement.
Cointelegraph's ECB survey on euro-area crypto acceptance is macro merchant-adoption news, not the status of the Keryx MCP payment pilot.
Latent.Space on ontologies and the semantic web is AI-agent theory, never cited on this subject, and says nothing about Keryx MCP payment status.
Simon Willison's LLM release note is metadata_only (0 plaintext bytes) about a library release, unrelated to the Keryx MCP payment pilot.
Hugging Face coding-agent memory post is metadata_only with no preview content and no bearing on the Keryx MCP payment pilot.
Vitalik's low-risk DeFi essay is metadata_only and about Ethereum DeFi strategy, not the Keryx MCP payment pilot.
Coinbase's 2022 response to the WSJ is about proprietary trading allegations, irrelevant to the Keryx MCP payment pilot.
Decrypt's Russia crypto-law story concerns trading legality and payment bans in Russia, not Keryx's MCP payment pilot.
CoinDesk's dollar-vs-euro onchain gap is stablecoin market analysis, tangential to the Keryx MCP payment pilot status.
Esoteric essay on Isis is entirely off-topic for the Keryx MCP payment pilot.
Conzit piece on India's UPI merchant-fee model is unrelated to Keryx's MCP payment pilot and would require a fresh payment.
Gardening article on no-dig raised beds has no connection to the Keryx MCP payment pilot.
Retro console recapping guide is completely off-topic for the Keryx MCP payment pilot.
Agent spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)
Reused cached Keryx Engineering (first-party) — Recovering a Keryx paid research job (free) — S1
Sub-claim "What is the current status of the Keryx MCP server payment p…": 10% covered by S1 — S1 is a first-party Keryx engineering note about recovering a paid research job via the buyer client (quoting, buying, resuming, reconciliation). It explicitly states it is not a report of external adoption and never mentions an 'MCP server' or a 'payment pilot' status. It provides only topical context about Keryx payment mechanics, not the requested pilot status.
The only gathered source (S1) is a first-party engineering note on buyer-side job recovery; it does not address the status of any Keryx MCP server payment pilot and explicitly disclaims being an adoption report. All skipped sources concern unrelated topics (x402 settlement latency, USDC finality, idempotency keys, Stripe fraud, ECB crypto payments, etc.) and none would plausibly report the status of a Keryx MCP server payment pilot. Buying them would not fill the identified gap, so no purchase is recommended despite the low coverage.
Final check — "What is the current status of the Keryx MCP server payment p…": 0% assessed
Final coverage assessment — The only supplied source is a first-party engineering note about recovering a Keryx paid research job. It describes buyer-client mechanics such as quoting, buying, resuming, and reconciliation, but it does not state the current status of any Keryx MCP server payment pilot. No pilot status, phase, launch state, adoption, or operational result is provided. The assessment does not establish a complete supported answer for every requested part.
Synthesizing a grounded answer from 1 source(s)…
Relevance review returned; only checked excerpts can retain support, and review cannot raise it.
Below reward gate — S1 supports claim 1 at 0%: “It is not a report of external adoption.”
Below reward gate — S1 supports claim 1 at 0%: “This first-party note describes the buyer client at repository commit 9ea84fa.”
Rejected 0 invalid evidence span(s) and 1 unsupported citation marker(s); rejected markers cannot receive citation rewards.
No citation passed the evidence gate — the $0.025000 citation pool stays unspent; settled access tolls still stand.
Drafted answer citing 0 source(s)
Confidence: Low — no citation passed the evidence gate.
Done. Spent $0 across 0 confirmed/simulated payment(s) to creators.
Payouts to cited creators appear here.
The provided sources do not describe a "Keryx MCP server payment pilot," so its current status cannot be determined from these passages. The only relevant source is a first-party engineering note about the Keryx buyer client, which explicitly states it "is not a report of external adoption". That note describes the buyer client's quoting, buying, and recovery behavior at a specific repository commit, but it contains no information about an MCP server payment pilot, its participants, or its status. Therefore, the current status of the Keryx MCP server payment pilot is unanswered by the supplied sources.
Evidence ledger — quotes verified before rewards
What is the current status of the Keryx MCP server payment pilot?
0%No reward-qualifying evidence
Portable research receipt
Take the evidence trail with you
One deterministic JSON bundle binds the answer, visible decisions, exact article versions, claim evidence and a Circle-settlement snapshot under SHA-256. Retain the digest to detect later changes; the self-check is not a publisher or Keryx signature.
Carries this dispatch’s question as context — never its answer. The next dispatch is read from sources bought for it.