What are the key findings in "Recovering a Keryx paid research job"?
9/11/2026, 6:51:41 AM · llm:deepseek:deepseek-v4-flash
The dispatch, itemised.
Breaking down: "What are the key findings in "Recovering a Keryx paid research job"?"
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 52 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.015000 fetch USDC reserved.
Free-preview pre-check maps an actionable source to every sub-claim (1/1); paid reading may proceed within the budget.
Exact title match to the question — first-party Keryx engineering note on recovering a paid research job, full_text (3071 bytes) already cached at $0.002. Directly answers claim 0. Reputation 50/100 but it is the primary source for this exact topic. — selected for the claim-aware evidence portfolio (targets claim 1; 0 fetch USDC, 1 attention slot).
USDC onchain settlement speed is tangential to buyer recovery of a Keryx job; abstract only, no direct bearing on claim 0.
x402 payment rail background is adjacent context but does not describe job recovery mechanics; abstract too thin to answer claim 0.
Nanopayment floor economics unrelated to recovering a paid research job.
Idempotency keys are conceptually related to avoiding double payment on resume, but the source is generic distributed-systems material, not Keryx recovery specifics.
Gardening content, entirely off-topic.
Retro console repair, entirely off-topic.
Stripe event promo about AI risk, no relevance to Keryx job recovery.
EF post on AI agents triaging protocol code; different domain, no recovery workflow detail.
ECB merchant crypto acceptance survey, unrelated to Keryx buyer recovery.
Ontologies/semantic web for agents; no connection to paid-job recovery.
Metadata-only Anthropic model news, off-topic and no readable content.
Metadata-only agent memory post, unrelated to Keryx recovery.
Metadata-only Vitalik DeFi essay, off-topic.
Coinbase WSJ rebuttal about proprietary trading; unrelated to Keryx job recovery.
Russia crypto law news, unrelated.
Dollar/euro onchain gap analysis, no bearing on recovery mechanics.
Esoteric Bible numerology, entirely off-topic.
Job application AI doom loop article; unrelated to Keryx paid-job recovery despite 'job' keyword.
Arc x402 settlement latency benchmarks; adjacent infrastructure context but not about recovering a Keryx job.
x402 finalization timing overview; tangential to buyer recovery workflow.
Agent spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)
Reused cached Keryx Engineering (first-party) — Recovering a Keryx paid research job (free) — S1
Sub-claim "What are the key findings reported in "Recovering a Keryx pa…": 90% covered by S1 — S1 is the full-text first-party note itself and explicitly reports the key findings: the buyer client separates quoting, buying, and recovering a research job; it uses a trusted treasury payee and an all-in price ceiling covering service fee and creator budget; it uses the caller's already-funded wallet without auto-funding; the buy command obtains a fresh quote, rechecks payment policy, writes a durable job journal, signs once and submits once; each purchase needs a new private job directory; the journal records normalized request, payment terms, nonce, and deterministic job identifier before signing, with a second durable boundary before submission; private keys and payment signatures are not journaled; the job identifier is sensitive bearer access; receipt snapshots are archived by digest and reconciliation may produce a different snapshot without erasing the older one; payment evidence and content delivery remain separate; a retained success response with a Circle reference is labeled seller-reported settlement, not independent Circle query or on-chain finality proof; without that response payment can remain unconfirmed; creator amounts can be settled, pending, or unknown and missing accounting must not silently become zero; buyers should inspect both the research result and its economics. Small gap: the excerpt is marked excerpted and omits some middle portions, so a few details may be missing, but the supplied passages directly answer the requested key findings.
Coverage is already adequate (0.9) from the first-party full-text note S1, which directly reports the key findings. The skipped sources are unrelated to the Keryx buyer recovery note (stablecoins, x402, nanopayments, idempotency, gardening, console repair, risk events, Ethereum agent triage, ECB merchant crypto acceptance, semantic web, AI model adoption, agent memory, DeFi, Coinbase, Russia crypto law, dollar/euro onchain gap, esoteric Bible reading, job applications, x402 latency/finalization). None would fill the small excerpt gap for this specific article, so no purchase is warranted.
Final check — "What are the key findings reported in "Recovering a Keryx pa…": 100% assessed by S1
Final coverage assessment — The single sub-claim asks for the key findings reported in the first-party Keryx note "Recovering a Keryx paid research job." The supplied full-text passages directly state several findings: the buyer client separates quoting, buying, and recovering a research job; it uses a caller-funded wallet and does not auto-fund; the buy command obtains a fresh quote, rechecks payment policy, writes a durable job journal, signs once, and submits once; each purchase needs a new private job directory; the journal records normalized request, payment terms, nonce, and deterministic job identifier before signing, with a second durable boundary before submission; private keys and payment signatures are not written to the journal; the job identifier is sensitive bearer access; receipt snapshots are archived by digest and reconciliation may produce a different snapshot without erasing the older one; payment evidence and content delivery remain separate; a retained success response with a Circle reference is seller-reported settlement, not independent Circle query or on-chain finality proof; without that response payment can remain unconfirmed even when a job exists; creator amounts can be settled, pending, or unknown and missing accounting must not silently become zero; buyers should inspect both the research result and its economics. These passages explicitly answer the requested key findings, so coverage is high. No requested part remains missing.
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 40%: “The independent Keryx buyer client separates quoting, buying and recovering a research job.”
Verified — S1 supports claim 1 at 40%: “The buyer provides a trusted Keryx treasury payee and an all-in price ceiling.”
Verified — S1 supports claim 1 at 40%: “The all-in ceiling includes both the service fee and creator budget.”
Verified — S1 supports claim 1 at 40%: “The client uses the caller's already-funded wallet; it does not automatically fund or deposit for it.”
Verified — S1 supports claim 1 at 50%: “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 1 at 40%: “Each purchase needs a new private job directory.”
Verified — S1 supports claim 1 at 50%: “Before signing, the journal records the normalized request, payment terms, nonce and deterministic job identifier.”
Verified — S1 supports claim 1 at 40%: “A second durable boundary is written before the signed submission is sent.”
Verified — S1 supports claim 1 at 40%: “Private keys and payment signatures are not written into the journal.”
Verified — S1 supports claim 1 at 40%: “The job identifier itself is sensitive because it provides bearer access to the research result.”
Verified — S1 supports claim 1 at 40%: “Receipt snapshots are archived by digest; reconciliation may later produce a different snapshot without erasing the older one.”
Verified — S1 supports claim 1 at 40%: “Payment evidence and content delivery remain separate.”
Verified — S1 supports claim 1 at 40%: “A retained success response with a Circle reference is labeled seller-reported settlement.”
Verified — S1 supports claim 1 at 40%: “It is not an independent Circle query or an on-chain finality proof.”
Verified — S1 supports claim 1 at 40%: “Without that response, payment can remain unconfirmed even when a job exists.”
Verified — S1 supports claim 1 at 40%: “Creator amounts can also be settled, pending or unknown; the client must not silently turn missing accounting into zero.”
Verified — S1 supports claim 1 at 40%: “Buyers should inspect both the research result and its economics before judging the outcome.”
Drafted answer citing 1 source(s)
Confidence: Moderate — 1 evidence-verified source cover every sub-claim, but corroboration or support strength is limited.
Keryx Engineering (first-party) contributed 100% → reward $0.015
Settled $0.015 citation reward → 0x6644A7C63C559454e77D5834554DCa3a60fcFDA2 (196898f2-0…)
Done. Spent $0.015 across 1 confirmed/simulated payment(s) to creators.
The note "Recovering a Keryx paid research job" is a first-party description of the buyer client at repository commit 9ea84fa, and it explicitly states it is not a report of external adoption . Its key findings concern how the buyer client handles quoting, buying, and recovering a research job .
On quoting and buying: the independent buyer client separates quoting, buying, and recovering a research job . The buyer supplies a trusted Keryx treasury payee and an all-in price ceiling, which includes both the service fee and creator budget . The client uses the caller's already-funded wallet and does not automatically fund or deposit for it . The buy command obtains a fresh quote, checks the payment policy again, writes a durable job journal, signs once, and submits once . Each purchase needs a new private job directory . Before signing, the journal records the normalized request, payment terms, nonce, and deterministic job identifier . A second durable boundary is written before the signed submission is sent . Private keys and payment signatures are not written into the journal, and the job identifier itself is sensitive because it provides bearer access to the research result .
On recovery and accounting: receipt snapshots are archived by digest, and reconciliation may later produce a different snapshot without erasing the older one . Payment evidence and content delivery remain separate . A retained success response with a Circle reference is labeled seller-reported settlement, and it is not an independent Circle query or an on-chain finality proof . Without that response, payment can remain unconfirmed even when a job exists . Creator amounts can be settled, pending, or unknown, and the client must not silently turn missing accounting into zero . Buyers should inspect both the research result and its economics before judging the outcome .
No unanswered parts of the research question remain based on the supplied passages.
Evidence ledger — quotes verified before rewards
What are the key findings reported in "Recovering a Keryx paid research job"?
50%“The independent Keryx buyer client separates quoting, buying and recovering a research job.” [S1] Recovering a Keryx paid research job
“The buyer provides a trusted Keryx treasury payee and an all-in price ceiling.” [S1] Recovering a Keryx paid research job
“The all-in ceiling includes both the service fee and creator budget.” [S1] Recovering a Keryx paid research job
“The client uses the caller's already-funded wallet; it does not automatically fund or deposit for it.” [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
“Each purchase needs a new private job directory.” [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
“A second durable boundary is written before the signed submission is sent.” [S1] Recovering a Keryx paid research job
“Private keys and payment signatures are not written into the journal.” [S1] Recovering a Keryx paid research job
“The job identifier itself is sensitive because it provides bearer access to the research result.” [S1] Recovering a Keryx paid research job
“Receipt snapshots are archived by digest; reconciliation may later produce a different snapshot without erasing the older one.” [S1] Recovering a Keryx paid research job
“Payment evidence and content delivery remain separate.” [S1] Recovering a Keryx paid research job
“A retained success response with a Circle reference is labeled seller-reported settlement.” [S1] Recovering a Keryx paid research job
“It is not an independent Circle query or an on-chain finality proof.” [S1] Recovering a Keryx paid research job
“Without that response, payment can remain unconfirmed even when a job exists.” [S1] Recovering a Keryx paid research job
“Creator amounts can also be settled, pending or unknown; the client must not silently turn missing accounting into zero.” [S1] Recovering a Keryx paid research job
“Buyers should inspect both the research result and its economics before judging the outcome.” [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.015
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.