Agentic Commerce · UCP + AP2 + x402 + Stripe

Agents that can pay.
Under governance.

Full UCP (Universal Commerce Protocol) implementation — Google's open standard for agentic commerce. Product discovery, checkout, identity linking, order management, AP2 mandates, x402 stablecoins, and Stripe — all governed by the same spending policy.

Talk to Sales Read the Docs

Three Payment Protocols

One governance layer. Three payment rails.

Every transaction — whether stablecoin, mandate, or card — goes through the same spending policy, approval workflow, and audit trail.

x402 Protocol

Coinbase + Cloudflare

Internet-native payments via HTTP 402. Agents pay for x402-protected APIs autonomously using USDC stablecoins on Base network. Instant settlement. No intermediaries.

USDC on Base HTTP 402 @x402/hono Instant settlement

AP2 Protocol

Google · Agentic Payments

Mandate-based authorization for agentic purchases. Three mandate types: IntentMandate (budget envelope), CartMandate (specific items), PaymentMandate (exact amount). Human pre-approves the envelope, agent spends within it.

Intent Mandates Cart Mandates ECDSA Signatures RFC 8785 Canonical

Stripe

Traditional Payment Rails

Enterprise billing via Stripe Connect. Agent spending tracked against subscription budgets. Revenue share for blueprint and skill authors. Monthly invoicing with detailed usage reports.

Stripe Connect Revenue Share Monthly Invoicing Multi-currency

Spending Governance

Every cent is governed.

Agents don't spend freely. Every transaction passes through the AP2 spending policy — the same governance layer regardless of payment rail.

The spending pipeline

Agent wants to pay
  → Check: Does this agent have spending permission? (106-permission RBAC)
  → Check: Is there an active mandate for this merchant/amount? (AP2)
  → Check: Would this exceed the daily/monthly budget limit?
  → Check: Does this require human approval? (governance policy)
  → If approved → Execute payment (x402 / Stripe)
  → Log to audit trail (hash-chained, SOX-grade)
  → Notify management chain (FYI, non-blocking)

Budget Limits

Per-agent, per-team, per-workspace spending caps. Daily, monthly, per-transaction. Configurable in governance policy.

Approval Workflows

High-value transactions require human approval. Manager notified. Approval/rejection logged. Timeout configurable.

Merchant Allowlists

Restrict which external services agents can pay. Per-agent or per-team. Deny-by-default for new merchants.

Complete Audit Trail

Every transaction logged: agent, amount, merchant, mandate, approval status, timestamp. Hash-chained. SIEM-exportable.

Two-Sided Commerce

Accept payments AND make payments.

MeetLoyd enables both sides of the agentic economy.

Accept payments (Server-side)

Protect your APIs with x402 middleware. External agents pay in USDC to access your services. Coinbase-hosted facilitator handles settlement. One line of code.

app.use('/api/premium/*', createX402Middleware(config))

Make payments (Client-side)

Your agents pay for external x402-protected APIs. Wallet keys encrypted in vault (same AES-256 as LLM API keys). AP2 spending policy controls every transaction.

MCP tool: x402_pay → policy check → sign → settle

Agents that can pay.Under governance.