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/AgentsPay/An intent-linked, append-only agent-spend ledger
A

An intent-linked, append-only agent-spend ledger

AGENTSPAYManage supplier listing

An intent-linked, append-only agent-spend ledger. Each transaction row binds six fields that payment networks do not carry together: agent identity, the human who owns that agent, the intent or task that triggered the spend, the policy verdict plus the specific rule that applied, the approver when one was required, and what actually settled. Around that core sit per-agent funded wallets with hard budgets (making budget-exhaustion events observable), spend controls recorded as caps, allowlists and velocity rules enforced before settlement, threshold approvals resolved one-tap approve or deny over Slack, email or webhook, and scoped virtual cards. Rail-neutral across AP2, ACP, x402 and MPP, with records exported to customer warehouses and via an audit API

Open buyer room →
AgentsPay/An intent-linked, append-only agent-spend ledger
SampleCoverage

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks AgentsPay 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
Transaction & Payment Processing ServicesApplication Software
Instruments
equities
Categories
AlternativeReferenceSentiment
Regions
US
Sample tickers
VMASQPYPLNUSHOPAMZNCRM
Dataset card
Type
not stated
Format
Tabular append-only event records delivered two ways — warehouse export and a programmatic audit API — which makes the corpus directly joinable rather than report-bound. Related objects are structured as well: policy rules with verdicts, approval events carrying approver identity and channel, per-agent wallet balances and budget states, and virtual-card provisioning records scoped per agent
Volume
Low absolute row count with unusually high field richness: each authorised transaction stores six linked fields including the triggering task intent, so information per row far exceeds a payment-network record. Est. low tens of thousands of audit rows to date. The asset compounds immediately because the ledger is append-only — every month of agent spend is permanent history, and the intent-to-payment link is the one field a competitor cannot backfill
Users
~10-100 paying accounts (inferred: no headcount or funding record exists, the contact page asks prospects how many agents they run and which stack they use, which is a hand-held early-sales motion, and there are no customer logos or case studies published)
History
1 years
Update frequency
not stated
Growth
Active and early — a broad current product surface (wallet, spend controls, approvals, virtual cards, audit trail, security, pricing, FAQ, blog) plus explicit rail-neutrality across AP2, ACP, x402 and MPP indicates active 2026 shipping into the agentic-payments wave. No customer logos, case studies or volume claims are published, so traction is unproven
Launched
~2025-2026 (inferred: no corporate or funding record surfaced, and the product is inseparable from the 2025-2026 agentic-payments protocol set — AP2, ACP, x402 — across which it claims rail-neutrality)
Delivery
not stated
Entity mapping
not stated
Sample
not stated
Point-in-time
not stated
Licence
not stated

supplier index read from their site

AgentsPay has not added their own details yet. Not yet on file:

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