What is Keryx and how does its research API work?
9/21/2026, 2:35:11 AM · llm:deepseek:deepseek-v4-flash
The dispatch, itemised.
Breaking down: "What is Keryx and how does its research API work?"
Identified 2 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 15 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 2/2 claim(s) above the evidence floor with $0.000000/$0.002500 fetch USDC reserved.
Free-preview pre-check maps an actionable source to every sub-claim (2/2); paid reading may proceed within the budget.
First-party Keryx engineering doc, full text (3071 bytes), and the only source that directly addresses Keryx itself and its paid research job flow (quoting, journaling a purchase, resuming a job). Highest reputation on this subject (47/100, 7 citations). Already cached, so reuse is free and it directly supports both 'What is Keryx?' and 'How does the research API work?' — selected for the claim-aware evidence portfolio (targets claims 1, 2; 0 fetch USDC, 1 attention slot).
Cached abstract about USDC onchain settlement; only tangentially related to Keryx's research API and says nothing about what Keryx is. Low reputation (13/100) and redundant with other settlement sources.
Cached abstract on x402 as an agent payment rail — background context for Keryx's payment mechanics, but it never mentions Keryx or its research API, so it cannot answer either sub-claim.
Cached abstract on nanopayment floors; relevant to pricing mechanics generally but not to defining Keryx or describing its research API.
Cached abstract on idempotency keys; generic distributed-systems advice with no Keryx or research-API content.
Gardening content, entirely off-topic for Keryx or its research API.
Retro console repair content, entirely off-topic.
Stripe event promo about AI risk; no Keryx or research-API substance.
Ethereum Foundation post on running AI agents against protocol code — adjacent agent-workflow context, but nothing about Keryx or its research API.
Bitcoin rally commentary; uncached and irrelevant to defining Keryx or its API.
Latent.Space piece on ontologies for AI agents; useful agent-architecture background but does not describe Keryx or its research API.
Metadata-only entry with no preview text; cannot establish relevance to Keryx or its API.
Metadata-only Hugging Face post on agent memory; no preview and no Keryx-specific content.
Metadata-only Vitalik post on low-risk DeFi; no preview and unrelated to Keryx's research API.
Coinbase response to the WSJ about proprietary trading; no Keryx or research-API relevance.
Russian crypto regulation news; unrelated to Keryx or its research API.
CoinDesk piece on the dollar/euro onchain gap; stablecoin-market analysis with no Keryx content.
Esoteric mysticism content, entirely off-topic.
Human-evolution research summary, entirely off-topic.
Arc settlement latency benchmarks for x402; relevant to Keryx's settlement rail but not to defining Keryx or explaining its research API. Read once before and never cited on this subject.
x402 finality timing overview; payment-rail context only, no Keryx or research-API detail.
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 Keryx?": 30% covered by S1 — S1 identifies Keryx as a paid research service with a buyer client, service fee, creator budget, and research packages, but it is a first-party engineering note on buyer recovery and does not give a definition or overview of what Keryx is as a product/protocol.
Sub-claim "How does Keryx's research API work?": 40% covered by S1 — S1 describes parts of the buyer client flow: quoting sends an unsigned request and validates a payment challenge; buying obtains a fresh quote, checks payment policy, writes a durable job journal, signs once and submits once; job identifiers grant bearer access; service receipts report evidence coverage. However, it does not describe the research API itself (endpoints, request/response schema, authentication, or how research is requested/retrieved), so only a partial answer is provided.
Coverage is partial but the remaining budget is only $0.0025, and none of the skipped sources are affordable at that price or relevant to Keryx or its research API. No purchase is recommended.
Final check — "What is Keryx?": 30% assessed by S1
Final check — "How does Keryx's research API work?": 40% assessed by S1
Final coverage assessment — The supplied source is a first-party engineering note about recovering a Keryx paid research job. It identifies Keryx as a paid research service/protocol with a buyer client, but it does not define what Keryx is beyond that context. It describes parts of the buyer-side workflow—quoting, buying, journaling, signing, submitting, and inspecting results/economics—but it does not explain how Keryx's research API itself works (e.g., endpoints, request/response schema, authentication, job lifecycle from the API side, or how research is executed). The referenced implementation links are not included as passages, so they cannot be used to fill the gap. 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.
Verified — S1 supports claim 1 at 40%: “This first-party note describes the buyer client at repository commit 9ea84fa.”
Below reward gate — S1 supports claim 1 at 10%: “It is not a report of external adoption.”
Verified — S1 supports claim 2 at 60%: “The independent Keryx buyer client separates quoting, buying and recovering a research job.”
Verified — S1 supports claim 2 at 70%: “The quote command sends an unsigned request and validates the returned payment challenge.”
Verified — S1 supports claim 2 at 40%: “A successful quote does not pay or start research.”
Verified — S1 supports claim 2 at 80%: “The buy command obtains a fresh quote, checks the payment policy again, writes a durable job journal, signs once and submits once.”
Verified — S1 supports claim 2 at 70%: “Before signing, the journal records the normalized request, payment terms, nonce and deterministic job identifier.”
Below reward gate — S1 supports claim 2 at 30%: “A completed job means execution finished, not that the answer was adequately supported.”
Verified — S1 supports claim 2 at 40%: “The service receipt reports evidence coverage separately.”
Drafted answer citing 1 source(s)
Confidence: Low — 1 sub-claim remains below the evidence threshold.
Keryx Engineering (first-party) contributed 100% → reward $0.0025
Settled $0.0025 citation reward → 0x6644A7C63C559454e77D5834554DCa3a60fcFDA2 (7602f6c0-1…)
Done. Spent $0.0025 across 1 confirmed/simulated payment(s) to creators.
> ⚠ Low confidence — 1 sub-claim remains below the evidence threshold within budget. Treat this as provisional.
The supplied source does not define what Keryx is beyond identifying it as the publisher of a first-party engineering note about a buyer client . It states that the note describes the buyer client at repository commit 9ea84fa and that it is not a report of external adoption . No passage in the source provides a general definition of Keryx as a product, protocol, or organization, so that part of the question remains unanswered.
Regarding how the research API works, the source describes the buyer client's workflow rather than a formal API specification. The independent Keryx buyer client separates quoting, buying and recovering a research job . The quote command sends an unsigned request and validates the returned payment challenge , and a successful quote does not pay or start research . The buy command obtains a fresh quote, checks the payment policy again, writes a durable job journal, signs once and submits once . Before signing, the journal records the normalized request, payment terms, nonce and deterministic job identifier . The source also notes that a completed job means execution finished, not that the answer was adequately supported , and that the service receipt reports evidence coverage separately . The source does not describe any HTTP endpoints, request/response schemas, authentication mechanisms, or other API-level details, so those aspects of how the research API works remain unanswered.
Evidence ledger — quotes verified before rewards
What is Keryx?
30%“This first-party note describes the buyer client at repository commit 9ea84fa.” [S1] Recovering a Keryx paid research job
How does Keryx's research API work?
40%“The independent Keryx buyer client separates quoting, buying and recovering a research job.” [S1] Recovering a Keryx paid research job
“The quote command sends an unsigned request and validates the returned payment challenge.” [S1] Recovering a Keryx paid research job
“A successful quote does not pay or start research.” [S1] Recovering a Keryx paid research job
“The buy command obtains a fresh quote, checks the payment policy again, writes a durable job journal, signs once and submits once.” [S1] Recovering a Keryx paid research job
“Before signing, the journal records the normalized request, payment terms, nonce and deterministic job identifier.” [S1] Recovering a Keryx paid research job
“The service receipt reports evidence coverage separately.” [S1] Recovering a Keryx paid research job
Footnotes — each one pays its author
- 1Recovering a Keryx paid research jobKeryx Engineering (first-party) · 2026-09-08100%+$0.0025
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.
Exact receipt still current
1 exact cited article version still match Keryx's current index. The source cited here has published nothing new since this dispatch settled.
Carries this dispatch’s question as context — never its answer. The next dispatch is read from sources bought for it.