Why is per-citation settlement fairer than a flat per-fetch toll?
9/19/2026, 5:31:42 AM · llm:deepseek:deepseek-v4-flash
The dispatch, itemised.
Breaking down: "Why is per-citation settlement fairer than a flat per-fetch toll?"
Identified 3 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 26 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 2/2 positive proposal(s): 2 cached + 0 fresh, predicting 3/3 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 (3/3); paid reading may proceed within the budget.
Top-reputation source on this subject (81% citation rate, avg weight 0.95) and the preview directly addresses per-citation payments weighted by contribution — the core of why per-citation settlement is fairer than a flat toll. Cached, so free reuse. — selected for the claim-aware evidence portfolio (targets claims 1, 2; 0 fetch USDC, 1 attention slot).
First-party Keryx engineering doc with full text (3473 bytes) explicitly covering access tolls, citation rewards, contribution weights and settlement limits — directly explains the flat per-fetch toll model and how per-citation rewards are distributed. Low past citation rate, but uniquely on-point and cached. — selected for the claim-aware evidence portfolio (targets claims 2, 3; 0 fetch USDC, 1 attention slot).
Reputable on this subject (50% citation rate) but preview only covers x402 settlement latency on Arc, tangential to the fairness/distribution question. Cached, so cheap to reuse for background on settlement mechanics. — cached bytes are free, but this read does not clear the attention gate (EV 0.40, minimum 0.45, with a required claim target).
Only 11% citation rate and preview is about x402 finalization timing, not per-citation vs flat-toll fairness. Redundant with Arc Settlement Benchmarks for the settlement-timing angle.
Never cited in 6 prior reads on this subject; preview only describes x402 as an HTTP 402 payment rail, not the per-citation vs flat-toll fairness argument.
Never cited on this subject; preview covers USDC instant settlement, which does not address per-citation fairness or flat-toll comparison.
Idempotency keys for retries are unrelated to per-citation settlement fairness or toll models.
Gardening content, entirely off-topic.
Retro console repair, entirely off-topic.
Stripe travel-fraud analysis is unrelated to citation settlement fairness; also not cached.
AI agents against Ethereum protocol code is unrelated to payment fairness or toll models.
Bitcoin rally commentary does not address per-citation settlement fairness; not cached.
Agent harness/framework article, no bearing on citation-weighted payment fairness.
Metadata-only, no preview content, and off-topic (model adoption).
Metadata-only content-safety post, off-topic.
Metadata-only memory-access complexity post, off-topic.
Coinbase response to WSJ about proprietary trading, unrelated to citation settlement fairness.
FCA/HTX regulatory settlement talks, unrelated to per-citation payment fairness.
Dollar-euro onchain stablecoin gap, unrelated to citation-weighted rewards.
Esoteric mythology content, entirely off-topic.
Creator AI apology commentary, off-topic; not cached.
Agent spend wallet ready: 0x72449d71ea6a955aD4d4d22C2fDAcdFCA622b9BE (balance sufficient)
Reused cached Onchain Micropayments Digest — Per-citation payments weighted by contribution (free) — S1
Reused cached Keryx Engineering (first-party) — How Keryx pays cited creators (free) — S2
Sub-claim "Why is per-citation settlement considered fairer than a flat…": 60% covered by S1, S2 — S1 directly states the fairness principle: a fair model pays each cited source in proportion to its contribution, so heavily-relied-upon sources earn more and lightly-used ones less. S2 supports the separation of access cost from citation reward (a paid read does not guarantee a citation reward), which implicitly contrasts per-citation rewards with a flat access toll. However, neither source explicitly argues why this is fairer than a flat per-fetch toll; the comparative fairness rationale is only implied, not stated.
Sub-claim "How does per-citation settlement distribute USDC creator rew…": 70% covered by S1, S2 — S2 explains the mechanism: the model proposes contribution weights for accepted sources, Keryx resolves those weights and allocates the citation pool using integer micro-USDC amounts, only evidence-ledger-accepted sources enter allocation, and creator payment calls use the source's authoritative payment terms. S1 adds that multi-author works can split a single reward across contributors automatically. The explicit 'USDC' label is not stated in the passages (micro-USDC amounts are), and the full weighting formula is not given, leaving a small gap.
Sub-claim "What does a flat per-fetch toll mean in Keryx's content acce…": 40% covered by S2 — S2 states that Keryx separates the cost of opening source content from the reward for citing it, and mentions access tolls already settled remain paid, implying a per-access payment. But it does not define what a 'flat per-fetch toll' means, nor specify that the toll is flat or charged per fetch. Only partial contextual support.
Coverage is adequate overall (0.4–0.7). The main gaps are the explicit comparative fairness argument and the definition of a flat per-fetch toll. None of the skipped sources address citation settlement, contribution-weighted rewards, or Keryx's access toll model; they concern x402 latency, USDC settlement speed, idempotency, or unrelated topics. No affordable skipped source would fill these gaps, so no purchase is recommended.
Final check — "Why is per-citation settlement considered fairer than a flat…": 80% assessed by S1
Final check — "How does per-citation settlement distribute USDC creator rew…": 80% assessed by S1, S2
Final check — "What does a flat per-fetch toll mean in Keryx's content acce…": 10% assessed by S2
Final coverage assessment — S1 directly states the fairness principle: each cited source is paid in proportion to its contribution, with heavily-relied-upon sources earning more and lightly-used ones less. S2 provides first-party detail on how the citation pool is allocated in integer micro-USDC by resolved contribution weights, but it does not explicitly say the settlement is in USDC, nor does it define a flat per-fetch toll. Neither source defines what a flat per-fetch toll means in Keryx's content access toll model; S2 only distinguishes access tolls from citation rewards and notes that cached content can avoid a new access toll. The assessment does not establish a complete supported answer for every requested part.
Synthesizing a grounded answer from 2 source(s)…
Relevance review returned; only checked excerpts can retain support, and review cannot raise it.
Verified — S1 supports claim 1 at 80%: “A fair model pays each cited source in proportion to its contribution to the final answer.”
Verified — S1 supports claim 1 at 70%: “Heavily-relied-upon sources earn more; lightly-used ones earn less.”
Verified — S2 supports claim 2 at 40%: “The model proposes contribution weights for accepted sources.”
Verified — S2 supports claim 2 at 90%: “Keryx resolves those weights and allocates the citation pool using integer micro-USDC amounts.”
Verified — S2 supports claim 3 at 40%: “Keryx separates the cost of opening source content from the reward for citing it.”
Below reward gate — S2 supports claim 3 at 30%: “Cached content can avoid a new access toll while still contributing to an answer and qualifying for a citation reward.”
Drafted answer citing 2 source(s)
Confidence: Low — 1 sub-claim remains below the evidence threshold.
Onchain Micropayments Digest contributed 40% → reward $0.01
Keryx Engineering (first-party) contributed 60% → reward $0.015
Paid $0.006 citation reward → Mara Okoye; Circle confirmed settlement even though the paid route acknowledgement failed.
Paid $0.004 citation reward → Devin Park; Circle confirmed settlement even though the paid route acknowledgement failed.
Paid $0.015 citation reward → 0x6644A7C63C559454e77D5834554DCa3a60fcFDA2; Circle confirmed settlement even though the paid route acknowledgement failed.
Done. Spent $0.025 across 3 confirmed/simulated payment(s) to creators.
Onchain Micropayments Digest
batched
Onchain Micropayments Digest
batched
Keryx Engineering (first-party)
batched
> ⚠ Low confidence — 1 sub-claim remains below the evidence threshold within budget. Treat this as provisional.
Per-citation settlement is considered fairer than a flat per-fetch toll because it pays each cited source in proportion to how much it actually contributed to the final answer, rather than charging the same amount for every fetch regardless of use: heavily-relied-upon sources earn more, while lightly-used ones earn less . In Keryx's model, the cost of opening source content is separated from the reward for citing it , so a flat per-fetch toll corresponds to the access toll for opening content, whereas the citation reward is a separate payment considered only after the answer is written and its evidence checked .
Regarding how per-citation settlement distributes USDC creator rewards according to cited contributions: the model proposes contribution weights for accepted sources, and Keryx resolves those weights and allocates the citation pool using integer micro-USDC amounts . Only sources accepted by the evidence ledger enter this allocation , and creator payment calls then use the source's authoritative payment terms, with a model-proposed weight not choosing a recipient or changing the source's payout authority . When no citation qualifies, the citation pool stays unspent, while access tolls already settled remain paid .
As for what a flat per-fetch toll means in Keryx's content access toll model: the sources state that Keryx separates the cost of opening source content from the reward for citing it , and that cached content can avoid a new access toll while still contributing to an answer and qualifying for a citation reward . However, the provided passages do not explicitly define a "flat per-fetch toll" as such, so that specific terminology is not directly answered by the sources.
Evidence ledger — quotes verified before rewards
Why is per-citation settlement considered fairer than a flat per-fetch toll?
80%“A fair model pays each cited source in proportion to its contribution to the final answer.” [S1] Per-citation payments weighted by contribution
“Heavily-relied-upon sources earn more; lightly-used ones earn less.” [S1] Per-citation payments weighted by contribution
How does per-citation settlement distribute USDC creator rewards according to cited contributions?
80%“The model proposes contribution weights for accepted sources.” [S2] How Keryx pays cited creators
“Keryx resolves those weights and allocates the citation pool using integer micro-USDC amounts.” [S2] How Keryx pays cited creators
What does a flat per-fetch toll mean in Keryx's content access toll model?
10%“Keryx separates the cost of opening source content from the reward for citing it.” [S2] How Keryx pays cited creators
Footnotes — each one pays its author
- 1Per-citation payments weighted by contributionOnchain Micropayments Digest40%+$0.01
- 2How Keryx pays cited creatorsKeryx Engineering (first-party) · 2026-09-0860%+$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
2 exact cited article versions still match Keryx's current index. The one cited source Keryx follows a feed for 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.