Brickroad
Brickroad
IndexSignalsBlog
/Index//

Product

  • Information Frontier Agent
  • Vendor Management Agent
  • Product Tour
  • Pricing

Solutions

  • All Solutions
  • Atlas
  • Wayfinder
  • Horizon

Suppliers

  • Sell Your Data
  • Start Onboarding
  • Programmatic Data License

Community

  • Public Index
  • Signals
  • Blog

Company

  • About
  • Team
  • Careers
  • Brand

Connect

  • LinkedIn
  • X
PrivacyTermsCookies

© 2026 Brickroad

/Index/X402-agent-pay/X402-agent-pay
XA

X402-agent-pay

X402-AGENT-PAYManage supplier listing

A settlement ledger that carries the semantic context the blockchain discards. Every payment settling through /x402/settle writes one atomic row in the same request with a fixed nine-field schema: payment_id, payer (agent or wallet that paid), payee (agent or wallet that received), amount_usdc, fee_usdc (the protocol fee), status, tx_hash (the Base L2 transaction hash acting as the verifiable receipt), metadata, and settled_at. The metadata field is what makes this a distinct asset rather than a chain mirror — it records what was actually bought as a resource label, the partner, and the context. The documentation gives the concrete example that the chain knows only that wallet A sent wallet B ten cents, whereas the ledger records that the payment was a market-data query to a finance agent; a sample response shows amount 0.10 USDC, payee a named agent, and resource labelled as on-chain DeFi data. The stated product intent is to convert the flat ledger into a payment knowledge graph of counterparties, frequency and categories so an agent can reason that it relies on one agent for crypto data and another for market analysis

Open buyer room →
X402-agent-pay/X402-agent-pay
SampleCoverage

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks X402-agent-pay and files the sample in your catalog — private to you.

Start 7-day trial→Nothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry
Financial Exchanges & DataApplication Software
Instruments
cryptoequities
Categories
AlternativeReferenceSentiment
Regions
US
Sample tickers
COINSQPYPLHOODVMAAMZNSHOP
Dataset card
Type
not stated
Format
Tabular ledger rows exposed as JSON via API and mirrored from Base L2 settlement, with each row carrying its own on-chain verification pointer — so records are independently checkable against the public chain rather than trusted on assertion. The knowledge-graph layer is derived as a triple structure over counterparties, frequency and categories. Delivery is HTTP-native against a hosted facilitator rather than a self-hosted library
Volume
Row count likely modest — settlement volume appears small by the site's own illustrative figures — but the per-row label is uniquely valuable. Each settlement contributes a resource-category label plus an agent-to-agent edge, so the derived graph is more informative than the row count suggests. Two components would be genuinely hard to replicate: the historical resource labelling, which cannot be backfilled onto chain data retroactively, and the agent identity resolution that lets payer and payee be named agents rather than anonymous addresses
Users
N/A as a consumer base — a payment rail with a hosted facilitator, priced per settlement, plus a white-label offering where teams run private rails under their own brand. Scale estimate: tens of integrating agent builders (inferred from a niche single-product site with no customer logos, no team page, no funding record, and a small set of sibling product pages)
History
1 years
Update frequency
not stated
Growth
Active with an expanding product surface rather than proven volume: a live hosted facilitator at /x402/settle, a documented API and learn section, an AgentCore integration page, and an enterprise white-label offering covering custom rails, private and encrypted stealth settlement, voice-initiated commerce, and a dedicated facilitator for teams deploying agents at scale. No customer names, case studies or transaction figures are published
Launched
~2025-2026 (inferred: the rail exists specifically for x402, which only became a neutral governed standard in 2026, and the illustrative sample settlement on the recall page is dated mid-2026; no corporate record or founding statement exists)
Delivery
not stated
Entity mapping
not stated
Sample
not stated
Point-in-time
not stated
Licence
not stated

supplier index read from their site

X402-agent-pay has not added their own details yet. Not yet on file:

  • Dataset
  • Data dictionary
  • Coverage
  • Provenance
  • Rights & data handling