How can creators get paid when AI agents cite their work?

Archived dispatch

Lowconfidence— Contains synthetic demo material; its measurements cannot support factual conclusions.

Sep 17, 2026, 3:34 PM · llm:deepseek:deepseek-v4-flash

§ IIThe reading1 cited

Lowconfidence— Contains synthetic demo material; its measurements cannot support factual conclusions.deep researchpreview plan 2/2 claimsportfolio 2/3 · evidence 50%

Illustrative demo content: synthetic sources and measurements are not factual research evidence. Source provenance and payment status are separate; inspect the receipt for settled, pending or simulated payments. Settlement does not authenticate a source's claims.

Creators can be paid through a system that separates the cost of opening source content from the reward for citing it . An access toll purchases a read through the source's x402 endpoint, while a citation reward is a separate payment considered after the answer is written and its evidence checked . Cached content can avoid a new access toll while still contributing to an answer and qualifying for a citation reward, and a paid read does not guarantee a citation reward . The agent divides the research budget into an access budget and a citation pool using the configured citation-pool ratio .

For the second question, 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; a model-proposed weight does not choose a recipient or change the source's payout authority . When no citation qualifies, the citation pool stays unspent, while access tolls already settled remain paid . The receipt distinguishes settled and pending payment records .

Regarding how access tolls are paid, the sources indicate an access toll purchases a read through the source's x402 endpoint , and x402 revives the dormant HTTP 402 'Payment Required' status as a real payment rail where a server responds 402 with machine-readable payment requirements and the client signs a payment authorization and retries. However, the sources do not provide a detailed step-by-step mechanism for how the toll payment is technically executed beyond this.

Evidence ledger — recorded source excerpts

Research targets are unverified topics. Coverage is an estimate of excerpt support, not proof of entailment, factual truth or a complete answer.

Requested topic (unverified): “How can creators get paid when AI agents cite their work?”
50% estimated
“A citation reward is a separate payment considered after the answer is written and its evidence checked.” [S1] How Keryx pays cited creators
Requested topic (unverified): “How does Keryx pay content access tolls and distribute USDC creator rewards according to cited contributions?”
60% estimated
“Keryx resolves those weights and allocates the citation pool using integer micro-USDC amounts.” [S1] How Keryx pays cited creators
“Creator payment calls then use the source's authoritative payment terms; a model-proposed weight does not choose a recipient or change the source's payout authority.” [S1] How Keryx pays cited creators

What if a source were missing?

Temporarily leave out one source to see which research targets retain excerpts in this report.

Inspect without

Showing the original excerpt ledger.

How can creators get paid when AI agents cite their work?
1 recorded excerpt remain.
Inspect remaining excerpts
“A citation reward is a separate payment considered after the answer is written and its evidence checked.”
S1 · Keryx Engineering (first-party) · How Keryx pays cited creators · version sha256:f254c14408c3e9e9a7773d4e31a9f4bc98ff58b630ffcbc870f6b5262f0fb561
How does Keryx pay content access tolls and distribute USDC creator rewards according to cited contributions?
2 recorded excerpts remain.
Inspect remaining excerpts
“Keryx resolves those weights and allocates the citation pool using integer micro-USDC amounts.”
S1 · Keryx Engineering (first-party) · How Keryx pays cited creators · version sha256:f254c14408c3e9e9a7773d4e31a9f4bc98ff58b630ffcbc870f6b5262f0fb561
“Creator payment calls then use the source's authoritative payment terms; a model-proposed weight does not choose a recipient or change the source's payout authority.”
S1 · Keryx Engineering (first-party) · How Keryx pays cited creators · version sha256:f254c14408c3e9e9a7773d4e31a9f4bc98ff58b630ffcbc870f6b5262f0fb561

Targets are requested topics, not verified assertions. Excerpts do not prove truth or independent corroboration. This view keeps the answer, confidence and payments unchanged and makes no new requests.

Research evidence matrix

Compare unverified research targets with cited sources and inspect recorded excerpts. An empty cell means no inspectable excerpt was recorded; it does not establish whether a claim is true, false, or disputed. Coverage and agent confidence do not prove entailment, measured accuracy or complete synthesis.

Research target by cited source evidence matrix
Research target (unverified)	Inspection status	[S1] How Keryx pays cited creatorsPublication: Keryx Engineering (first-party)Published: 2026-09-08T00:00:00.000Z
How can creators get paid when AI agents cite their work?	Recorded excerpt	Inspect 1 excerpt A citation reward is a separate payment considered after the answer is written and its evidence checked.
How does Keryx pay content access tolls and distribute USDC creator rewards according to cited contributions?	Recorded excerpt	Inspect 2 excerpts Keryx resolves those weights and allocates the citation pool using integer micro-USDC amounts. Creator payment calls then use the source's authoritative payment terms; a model-proposed weight does not choose a recipient or change the source's payout authority.

Reference export

1 article references. Recorded titles, links and dates; observed scholarly records also include supplied authors, DOI and journal metadata with read limits. Review metadata before using in a paper. Import RIS into Zotero with File → Import.

Cited sources and references

1How Keryx pays cited creatorsKeryx Engineering (first-party) · 2026-09-08100%$0.025 planned

Spent$0.025

To creators100%

Decisions0 bought · 2 cached · 19 skipped

llm:deepseek:deepseek-v4-flashArc Testnet · historical

Decision log · 51 steps

§ IThe decision$0.025 settled / $0.05

50%$0.025 under cap

Decompose

Breaking down: "How can creators get paid when AI agents cite their work?"

Decompose

Identified 2 research target(s) to investigate; these are not established facts

Decompose

Deep mode: up to 4 paid/cached reads plus one bounded gap-expansion pass when needed.

Discover

Discovered 21 verified source(s)

Discover

Recalled 60 past runs on this subject — how these sources performed when they were available.

Discover

ERC-8004 reputation loaded — composite scores on this subject.

Pre-check

Claim-aware portfolio selected 2/3 positive proposal(s): 2 cached + 0 fresh, predicting 2/2 claim(s) above the evidence floor with $0.000000/$0.025000 fetch USDC reserved.

Pre-check

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

DecideCACHE

Keryx Engineering (first-party) — How Keryx pays cited creators$0.002 · EV 90%

First-party Keryx engineering note directly titled 'How Keryx pays cited creators' — covers access tolls, citation rewards, exact-quote evidence checks, contribution weights and settlement limits. This is the single most on-point source for both the core question and the Keryx mechanism subclaim, and it's already cached (free reuse). Full text (3473 bytes) not just an abstract. Reputation 54/100 with 7 citations on this subject. — selected for the claim-aware evidence portfolio (targets claims 1, 2; 0 fetch USDC, 1 attention slot).

DecideCACHE

Agent Economy Weekly — x402 turns HTTP 402 into an agent payment rail$0.004 · EV 80%

Agent Economy Weekly's x402 rail piece explains how a server demands payment and an agent pays inline — the payment plumbing underlying creator tolls/rewards. Highest-volume citable source here (29/38 runs, 76%) with strong reputation 61/100. Cached, so free. — selected for the claim-aware evidence portfolio (targets claims 1, 2; 0 fetch USDC, 1 attention slot).

DecideSKIP

Stablecoin Ledger — Stablecoins as the unit of account for agents$0.003 · EV 60%

Stablecoin Ledger covers USDC as the unit of account for agents — relevant to how creator rewards are denominated and settled. Cached and cheap; reputation 41/100 with 16 citations. Abstract only, so it answers the denomination angle, not the full payout mechanism. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.025000 fetch-budget caps, so this proposal stays unspent.

DecideSKIP

Arc Settlement Benchmarks — Measuring x402 settlement latency on Arc$0.003 · EV 40%

Arc Settlement Benchmarks measures x402 batched-settlement latency/finality on Arc — supports the settlement-feasibility side of paying creators via x402 tolls. Cached, free; weaker reputation (10/100) and abstract-only, so secondary. — cached bytes are free, but this read does not clear the attention gate (EV 0.40, minimum 0.45, with a required claim target).

DecideSKIP

Web Payments Review — How long do x402 payments take to finalize?$0.002 · EV 35%

Web Payments Review gives end-to-end x402 settlement timing, a supporting detail for whether micro-tolls to creators can finalize cheaply. Cached and free, but low reputation (18/100) and only 2 prior citations; abstract only. — cached bytes are free, but this read does not clear the attention gate (EV 0.35, minimum 0.45, with a required claim target).

DecideSKIP

Onchain Micropayments Digest — Nanopayments and the $0.000001 floor$0.005 · EV 35%

Onchain Micropayments Digest on nanopayments/batching is relevant to making per-citation creator payouts economical at sub-cent scale. Cached, free; reputation 16/100 and abstract-only, so marginal. — cached bytes are free, but this read does not clear the attention gate (EV 0.35, minimum 0.45, with a required claim target).

DecideSKIP

Latent.Space — React for Agents: Astro Creator Brings Hooks to his Meta-Harness, Flue$0.004 · EV 30%

Latent.Space has the best reputation here (64/100) and full text, but this specific piece is about agent harnesses/hooks, not creator compensation — only tangentially touches agent architecture. Cached, so free to reuse, but weak topical fit. — cached bytes are free, but this read does not clear the attention gate (EV 0.30, minimum 0.45, with a required claim target).

DecideSKIP

Cointelegraph.com News — Coinbase lets businesses accept USDC payments from AI agents$0.002 · EV 30%

Cointelegraph reports Coinbase enabling businesses to accept USDC payments from AI agents — adjacent evidence that agent-to-business USDC payment rails exist, which is the substrate for creator tolls. Cached, free; low reputation (3/100), abstract only. — cached bytes are free, but this read does not clear the attention gate (EV 0.30, minimum 0.45, with a required claim target).

DecideSKIP

CoinDesk: Bitcoin, Ethereum, Crypto News and Price Data — Bitcoin and Ether bears get decimated amid 'squeeze-led' rally and Musk's X wants to pay creators in stablecoins: Crypto week in 5 stories$0.002 · EV 25%

CoinDesk roundup mentions X wanting to pay creators in stablecoins — a direct, if shallow, data point on creator payouts via stablecoins. Cached, free; CoinDesk has 0 citations on this subject and the item is a broad news digest, so low weight. — cached bytes are free, but this read does not clear the attention gate (EV 0.25, minimum 0.45, with a required claim target).

DecideSKIP

Decrypt — Binance Opens the Door to AI Agents That Can Trade Crypto for You$0.002 · EV 20%

Decrypt covers Binance opening to AI agents that trade crypto — shows agent-driven crypto payment activity but not creator citation payouts. Cached, free; reputation 8/100, abstract only. — cached bytes are free, but this read does not clear the attention gate (EV 0.20, minimum 0.45, with a required claim target).

DecideSKIP

Stripe Blog — Giving agents the ability to pay$0.002 · EV 20%

Stripe's 'Giving agents the ability to pay' describes programmatic agent payment credentials (SPT/one-time cards) — a parallel mechanism to x402 tolls, useful as contrast. Cached, free; Stripe Blog has 0 citations on this subject. — cached bytes are free, but this read does not clear the attention gate (EV 0.20, minimum 0.45, with a required claim target).

DecideSKIP

The Coinbase Blog - Medium — Coinbase Cloud launches platform for web3 developers$0.003 · EV 10%

Coinbase Cloud developer-platform launch from 2022 is about blockchain API access, not agent payments or creator rewards — stale and off-topic despite the stablecoins/USDC tag.

DecideSKIP

Ethereum Foundation Blog — The triage is the product: running AI agents against Ethereum's protocol code$0.002 · EV 8%

Ethereum Foundation post on running AI agents against protocol code is about security triage, not creator compensation or citation payouts. No target support.

DecideSKIP

Distributed Systems Notes — Idempotency keys prevent double-spends$0.003 · EV 8%

Idempotency keys for double-spend prevention is generic distributed-systems material; only a distant implementation detail for payment rails, not about creator payouts.

DecideSKIP

Garden & Soil Monthly — Building a no-dig raised bed$0.002 · EV 0%

Gardening article on no-dig raised beds is entirely unrelated to agent payments or creator rewards.

DecideSKIP

Retro Game Hardware — Recapping a 1990s console$0.002 · EV 0%

Retro console recapping is unrelated to the question.

DecideSKIP

Inner Axiom — The Codex — The Pleiades, the Seven Sisters in Taurus and Orion$0.002 · EV 0%

Esoteric mythology piece on the Pleiades is unrelated to agent payments or creator compensation.

DecideSKIP

Conzit Labs — Hank Green's AI Apology: A Content Creator's Reflection$0.002 · EV 15%

Hank Green's AI apology touches creator authenticity/AI, but the preview shows no payment or citation-reward mechanism, and it is not cached (would cost $0.002 for a 104-byte abstract). Not worth the toll.

DecideSKIP

Simon Willison's Weblog — There's No Limit to How Bad Code Can Get$0.003 · EV 5%

Simon Willison piece on code quality is metadata-only (0 plaintext bytes) and off-topic; no preview content to justify a purchase.

DecideSKIP

Hugging Face - Blog — Nemotron 3.5 Content Safety: Customizable Multimodal Safety for Global Enterprise AI$0.003 · EV 5%

Hugging Face Nemotron content-safety post is metadata-only and about model safety, not creator payments.

DecideSKIP

Vitalik Buterin's website — Low-risk defi can be for Ethereum what search was for Google$0.004 · EV 10%

Vitalik's low-risk DeFi post is metadata-only (no preview text) and about DeFi risk, not agent citation payments to creators.

Fetch

Agent spend wallet ready: 0x72449d71ea6a955aD4d4d22C2fDAcdFCA622b9BE (balance sufficient)

Fetch

Reused cached Keryx Engineering (first-party) — How Keryx pays cited creators (free) — S1

Fetch

Reused cached Agent Economy Weekly — x402 turns HTTP 402 into an agent payment rail (free) — S2

Re-evaluate

Sub-claim "How can creators get paid when AI agents cite their work?": 80% covered by S1 — S1 directly answers the general mechanism: Keryx separates access tolls (paid reads via x402) from citation rewards, allocates a citation pool to accepted sources by resolved contribution weights, and pays creators using the source's authoritative payment terms. It notes cached content can still qualify and that paid reads don't guarantee rewards. Minor gap: it is one first-party system's approach, not a general survey of all payment models.

Re-evaluate

Sub-claim "How does Keryx pay content access tolls and distribute USDC …": 70% covered by S1 — S1 explains access tolls purchase reads through the source's x402 endpoint, the research budget is split into an access budget and citation pool via a configured ratio, the model proposes contribution weights for accepted sources, Keryx resolves weights and allocates the citation pool in integer micro-USDC amounts, and creator payment calls use the source's authoritative payment terms. Gap: the passage does not explicitly state that creator rewards are paid in USDC (only micro-USDC amounts and a Circle transfer reference imply it), and it does not detail the exact weight-resolution formula.

Re-evaluate

Coverage is adequate for both sub-claims via S1, which directly describes Keryx's access-toll and citation-reward mechanism. Remaining gaps (explicit USDC denomination, exact weight formula, broader creator-payment landscape) are minor and not clearly filled by any affordable skipped source; the skipped items concern x402 latency, stablecoin unit-of-account, agent trading, or unrelated topics, so no purchase is warranted.

Sufficiency

Final check — "How can creators get paid when AI agents cite their work?": 100% assessed by S1

Sufficiency

Final check — "How does Keryx pay content access tolls and distribute USDC …": 100% assessed by S1

Sufficiency

Final coverage assessment — S1 directly answers both sub-claims: it explains that Keryx separates access tolls from citation rewards, uses an access budget and citation pool, allocates the pool in integer micro-USDC based on accepted source contribution weights, and pays creators through the source's authoritative payment terms. S2 only provides general x402 context and does not address creator payment or Keryx's USDC distribution. No requested part remains missing.

Synthesize

Synthesizing a grounded answer from 2 source(s)…

Evidence

Relevance review returned; only checked excerpts can retain support, and review cannot raise it.

Evidence

Below reward gate — S1 supports claim 1 at 30%: “Keryx separates the cost of opening source content from the reward for citing it.”

Evidence

Verified — S1 supports claim 1 at 50%: “A citation reward is a separate payment considered after the answer is written and its evidence checked.”

Evidence

Verified — S1 supports claim 2 at 60%: “Keryx resolves those weights and allocates the citation pool using integer micro-USDC amounts.”

Evidence

Verified — S1 supports claim 2 at 60%: “Creator payment calls then use the source's authoritative payment terms; a model-proposed weight does not choose a recipient or change the s…”

Evidence

Below reward gate — S2 supports claim 2 at 10%: “x402 revives the dormant HTTP 402 'Payment Required' status as a real payment rail.”

Evidence

Rejected 0 invalid evidence span(s) and 1 unsupported citation marker(s); rejected markers cannot receive citation rewards.

Synthesize

Drafted answer citing 1 source(s)

Verdict

Confidence: Moderate — 1 evidence-verified source cover every sub-claim, but corroboration or support strength is limited.

Attribute

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

Settle

Paid $0.025 citation reward → 0x6644A7C63C559454e77D5834554DCa3a60fcFDA2; Circle confirmed settlement even though the paid route acknowledgement failed.

Done

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

Read checkpoints

Read checkpoint evidence is unavailable for this report. Historical, private and unsupported native runs are not reconstructed.

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.

View JSON ↗Download

Manage question privacy

Recorded purchase outcomes

Did the exact article versions bought for this answer appear in its citations? This view scores retained BUY decisions against payment observations recorded in the same dispatch trace.

Recorded settlement bookkeeping only; Circle and chain settlement have not been independently rechecked here.

This is a partial retained trace sample, not a full payment ledger. An absent matching payment does not prove that no payment occurred; excluded and unconfirmed costs remain unknown.

Recorded network: eip155:5042002
Dispatch recorded at: 2026-09-17T15:34:01.274Z

Frozen testnet archive, captured 2026-10-03T00:26:18.665Z. This is historical testnet evidence, separate from current mainnet activity.

Archive source commit: f9dca8d04f4657abbf0153175feec65728ba6a99
Archive database SHA-256: c5d9c0d2bf01099de526d7510321eabd1b0e3519f2792d40b61e49062d766272

Participant cohort: unknown. No outside-customer usage is inferred.

0 scored exact-version purchases from 0 recorded BUY decisions; 0 BUY decisions unscored. 1 of 1 trace payment observations excluded.

Each unique source + item + content version with positive matching recorded settled access counts once. Duplicate BUYs, missing identities, zero/unconfirmed access and incompatible payment observations cannot create a scored purchase. CACHE and SKIP decisions are outside this sample.

Exact-version citation hit rate: Unmeasured
Recorded access cost of uncited purchases: Unmeasured

Predicted value and observed citations

Bins compare the recorded predicted value with citation occurrence in this one dispatch. Small samples do not validate a probability model.

Value band	Predicted mean (0–1)	Citation rate
0–0.2	Unmeasured	Unmeasured
0.2–0.4	Unmeasured	Unmeasured
0.4–0.6	Unmeasured	Unmeasured
0.6–0.8	Unmeasured	Unmeasured
0.8–1	Unmeasured	Unmeasured

Missed value, cost per supported claim, budget alternatives and counterfactual outcomes are unmeasured. No extra reading or learning was performed.

View outcome JSON Download outcomes Purchase outcomes across recent reports

A new follow-up runs on Arc mainnet with today’s sources and budget. Only the historical question supplies context.

Ask a follow-upNew dispatch · creators paid again

Carries this dispatch’s question as context — never its answer. The next dispatch is read from sources bought for it.

From the archive

Related dispatches

DispatchOct 9, 2026

Tôi cần viết hướng dẫn an toàn cho đồng nghiệp khi mua báo cáo Keryx. Đọc bài "Recovering a Keryx paid research job" từ Keryx Engineering (first-party). Viết bằng tiếng Việt tối đa 4 gạch đầu dòng: khi POST bị timeout phải giữ lại gì; dùng job ID cũ để xem kết quả thế nào; vì sao GET trả 404 chưa đủ kết luận thanh toán thất bại; phải giữ recovery file riêng tư ra sao. Dẫn trích đoạn đúng của bài, phân biệt hướng dẫn tài liệu với một giao dịch đã được kiểm chứng. Tổng phí nguồn/reward tối đa 0.08 USDC.

1 source cited$0.0400 recorded creator rewards

DispatchOct 12, 2026

If I were building a paid research agent, how would payment evidence when research delivery fails affect a design decision?

1 source cited$0.0300 recorded creator rewards

DispatchOct 12, 2026

What would I need to verify before relying on a claim about journaling a Keryx paid job before submission?

2 sources cited$0.0225 recorded creator rewards

DispatchOct 11, 2026

Đọc bài 'Recovering a Keryx paid research job' của nguồn đã đăng ký Keryx Engineering (first-party). Chỉ trả lời câu hỏi này bằng tiếng Việt: khi đã có một job nhưng không giữ được response có Circle reference, vì sao trạng thái thanh toán và creator accounting phải giữ là chưa xác nhận thay vì tự ghi bằng 0? Dẫn trích đoạn thật của bài và giữ phạm vi phiên bản tài liệu.

1 source cited$0.0250 recorded creator rewards

Browse the full archive ▸