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 13 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.005000 fetch USDC reserved.

Free-preview pre-check maps an actionable source to every sub-claim (2/2); paid reading may proceed within the budget.

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 only indirectly: it is a first-party engineering note about a 'Keryx paid research job' and an 'independent Keryx buyer client' that separates quoting, buying and recovering a research job. This gives topical context that Keryx involves paid research jobs and a buyer client, but it never defines what Keryx is as a product, protocol, or service.

Sub-claim "How does Keryx's research API work?": 40% covered by S1 — S1 describes the buyer client's workflow in some detail: the quote command sends an unsigned request and validates a returned payment challenge; the buy command obtains a fresh quote, checks payment policy, writes a durable job journal, signs once and submits once; each purchase needs a new private job directory; the journal records the normalized request, payment terms, nonce and deterministic job identifier; a second durable boundary is written before submission; keys and signatures are not journaled; the job identifier grants bearer access to the result; the service receipt reports evidence coverage separately. However, this is the buyer client's purchase/recovery flow, not the research API itself. The passages do not specify API endpoints, request/response schemas, authentication, how a research job is actually executed, or how results are retrieved. The referenced implementation files are only linked, not included.

Coverage for both sub-claims is below 0.5, but none of the affordable skipped sources (all priced at $0.002–$0.005, within the $0.005 remaining budget) address Keryx or its research API. The skipped items concern USDC settlement, x402 payment rails, nanopayments, idempotency keys, gardening, console repair, Stripe risk, Ethereum agent triage, crypto market commentary, ontologies, AI model adoption, agent memory, DeFi, Coinbase, Russian crypto law, onchain euro/dollar gaps, esoteric cosmology, human evolution, and x402 settlement latency. None would fill the identified gaps, so buying them would not improve coverage. The actual gaps (definition of Keryx and the research API's endpoints/schema/execution/result retrieval) would require the linked first-party implementation references (docs/buyer-agent.md and lib/a2a/research-package.ts), which are not among the purchasable skipped sources.

Final check — "What is Keryx?": 30% assessed by S1

Final check — "How does Keryx's research API work?": 10% assessed by S1

Final coverage assessment — The supplied source is a first-party engineering note about recovering a Keryx paid research job. It provides only indirect context for what Keryx is (a paid research service with a buyer client, service fee, creator budget, and research results) and does not explain how Keryx's research API works. It describes buyer-side quoting, buying, and recovery mechanics, but no API endpoints, request/response formats, authentication, or research API workflow. 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 10%: “This first-party note describes the buyer client at repository commit 9ea84fa.”

Verified — S1 supports claim 1 at 70%: “The independent Keryx buyer client separates quoting, buying and recovering a research job.”

Verified — S1 supports claim 2 at 60%: “The quote command sends an unsigned request and validates the returned payment challenge.”

Verified — S1 supports claim 2 at 70%: “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 40%: “A successful quote does not pay or start research.”

Verified — S1 supports claim 2 at 40%: “Each purchase needs a new private job directory.”

Verified — S1 supports claim 2 at 60%: “Before signing, the journal records the normalized request, payment terms, nonce and deterministic job identifier.”

Verified — S1 supports claim 2 at 50%: “A second durable boundary is written before the signed submission is sent.”

Verified — S1 supports claim 2 at 40%: “Private keys and payment signatures are not written into the journal.”

Verified — S1 supports claim 2 at 40%: “The job identifier itself is sensitive because it provides bearer access to the research result.”

Verified — S1 supports claim 2 at 50%: “The client uses the caller's already-funded wallet; it does not automatically fund or deposit for it.”

Verified — S1 supports claim 2 at 40%: “The all-in ceiling includes both the service fee and creator budget.”

Verified — S1 supports claim 2 at 40%: “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.”

Verified — S1 supports claim 2 at 40%: “The package is best effort, with provisional completion objectives and no promised remedy.”

Verified — S1 supports claim 2 at 40%: “Unused creator reserve under the fixed-price package is not an automatic refund.”

Verified — S1 supports claim 2 at 40%: “Buyers should inspect both the research result and its economics before judging the outcome.”

Verified — S1 supports claim 2 at 40%: “Creator amounts can also be settled, pending or unknown; the client must not silently turn missing accounting into zero.”

Drafted answer citing 1 source(s)

Confidence: Low — 2 sub-claims remain below the evidence threshold.

Keryx Engineering (first-party) contributed 100% → reward $0.005

Settled $0.005 citation reward → 0x6644A7C63C559454e77D5834554DCa3a60fcFDA2 (92b856ae-e…)

Done. Spent $0.005 across 1 confirmed/simulated payment(s) to creators.