Keryx
Dispatch wire
PAID@circle-research+$0.018
PAID@402.org+$0.020
PAID@arc-docs+$0.011
PAID@fieldguide.dev+$0.016
PAID@stables-weekly+$0.009
PAID@agent-econ+$0.022
PAID@circle-research+$0.014
PAID@arc-docs+$0.008
PAID@circle-research+$0.018
PAID@402.org+$0.020
PAID@arc-docs+$0.011
PAID@fieldguide.dev+$0.016
PAID@stables-weekly+$0.009
PAID@agent-econ+$0.022
PAID@circle-research+$0.014
PAID@arc-docs+$0.008
← All wanted claims
Wanted claim · openDemand with a receipt
A claim Keryx was paid to support

How does x402 technically implement or transform HTTP 402 into an agent payment rail?

Coverage
0%
finished short
Reader demand
1×
paid dispatches; agent retries excluded
Last measured
Sep 21
from a public dispatch receipt
Inspect the failed dispatch ↗

This is an invitation, not a guaranteed bounty.

Offer a post only after Keryx judges its public RSS preview relevant. Once the source is registered, indexed, and ownership-verified, Keryx sponsors one bounded retry with at most $0.05 on Arc testnet. A payout happens only when the paid full text supplies qualifying evidence, the agent cites it, and Circle settlement succeeds.

Already listed? Offer the exact article.

Keryx rechecks your registry authority and public preview, then guarantees this version a place in the retry. The agent still decides BUY or SKIP; only grounded, settled evidence fills the claim.

Would Keryx buy your feed for this claim?

The agent sees your recent titles and summaries — the same free preview a listed source gets judged on. Takes a few seconds.

“How does x402 technically implement or transform HTTP 402 into an agent payment rail?”