A cross-protocol agent payment and authorisation ledger

A cross-protocol agent payment and authorisation ledger — the differentiator is that one wallet observes all three emerging rails simultaneously rather than one. AP2 path: per-agent ECDSA keypairs provisioned at signup, a public key endpoint for verifier resolution, MCP signing tools for intent, cart and payment mandates, an inbound payment endpoint performing full mandate-chain verification, plus beneficiary resolution, audit trail, key revocation and idempotency records. x402 path: HTTP 402 pay-per-request micro-settlements in USDC on Base via Coinbase CDP with gas sponsorship and per-agent caps enforced at the wallet layer rather than the application layer. ACP path: Shared Payment Token issuance in production with merchant-and-cart-scoped one-time card tokens and a VGS forward-proxy handling real card data for PCI purposes, with Stripe as the PSP intermediary. Around this sit agent-linked virtual cards with per-agent daily limits, an accountable ownership model organising agents under principals with ledger and payment activity review, and per-agent communication resources

Open buyer room →

Sample

Brickroad customers

Sample this dataset before you buy it.

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

Start 7-day trialNothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry: Transaction & Payment Processing ServicesApplication Software
Instruments: equitiescrypto

Dataset card

Type: not stated
Format: Tabular ledger and audit records plus cryptographic artefacts: signed mandate objects (intent, cart, payment) forming verifiable chains, per-agent public keys, SPT and virtual-card provisioning records, and settlement rows spanning two very different rail types — stablecoin settlement on Base and tokenised card settlement through a PSP. Access is API plus a single MCP endpoint that any compatible LLM client can call, which means the ledger is designed to be queried programmatically by agents as a first-class consumer
Volume: Modest row volume, but structurally the richest single corpus identified in this pass because it spans three rails at once. Two components would be hard to replicate: the signed mandate chains, which record what a human authorised and cannot be reconstructed after the fact, and the cross-rail view of the same agent's spending behaviour. A caution on apparent scale — the 50M+ transactions figure quoted for x402 refers to the protocol's ecosystem-wide history across Coinbase and others, not this wallet's own volume, and must not be read as their corpus size
Users: N/A as a consumer base — B2B infrastructure sold to teams deploying agent fleets, with sign-up and sign-in surfaces and a contact-sales flow explicitly for fleet deployment. Institutional estimate: tens of deploying teams (inferred from a young single-product site, no customer logos or case studies, no funding or headcount record, and a contact page labelled Coming soon for fleet deployment)
History: 1 years
Update frequency: not stated
Growth: Active with a broad surface shipped quickly and some honesty about its edges: three protocol implementations claimed live in production, an MCP endpoint, per-agent cards, principal accounts, communication resources, multiple use-case pages, and integrations with MCP clients including Claude, Cursor, Windsurf and MCP Inspector. Multiple features are marked coming soon, and the protocol page carries explicit caveats that availability depends on the configured integration
Launched: ~2025-2026 (inferred: the product requires AP2 v0.1, x402 and ACP, all of which are 2025-2026 vintage specifications, and the homepage interface mock carries 2026-dated UI; no corporate record, funding history 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