Agent-native USDC payment routing

Payments for agents buying digital work.

AlgoCard connects sellers, buyers, and agents through pay codes, agent wallets, and policy-aware USDC settlement. It is checkout for humans and payment transport for software.

Create pay route
Price a digital service call in USDC.

Limits checked before signing.

Payment stack
Control plane and settlement path

User approval

Pera wallet owns pairing and checkout signatures.

Agent settlement

Dedicated wallets pay within Convex limits on Algorand.

Three-sided market

Sellers create supply. Buyers create demand. Agents connect the transaction.

Bridge

Agents

Agents become the transaction layer between demand and supply. They can discover services, request quotes, create orders, and pay from bounded wallets when policy allows.

MCP tools
Agent wallets
Spend limits

How the loop closes

A payment path for programmable marketplaces.

The seller can run a storefront agent. The buyer can bring a purchasing agent. AlgoCard gives both sides a common transaction primitive: create a payable intent, check policy, sign, settle, and audit.

1

Seller exposes a product, service, dataset, or API-priced action.

2

Agent creates a pay code or pays directly from a funded wallet.

3

Buyer approves through Pera, or pre-authorized limits allow autonomous spend.

4

USDC settles on-chain and AlgoCard records the payment event.

Signed identity checks

The same wallet flow can prove who is on the other side.

AlgoCard can use a zero-value Algorand transaction with a one-time note to prove wallet control. That makes support, refunds, and agent-to-user interactions harder to spoof without adding passwords or account recovery theater.

Verify a support agent

A merchant can ask the agent wallet to sign a zero-value challenge before a customer trusts instructions, links, or payment requests.

Confirm refund ownership

A buyer requesting a refund can prove they still control the original wallet, reducing impersonation and social-engineering risk.

Bind identity to audit

The signed note creates a timestamped proof that connects a wallet, a request, and an action without storing passwords or shared secrets.

Why this changes the market

Digital commerce is becoming programmatic, but payments still assume a human at every step.

Agents can search, compare, compose, and execute work across the internet. The missing layer is a payment protocol that respects custody, delegation, limits, and low-value transactions. AlgoCard turns payment into a capability agents can call without removing the buyer from control.

Micropriced by default

The platform can support $0.10 unlocks, per-call pricing, and small autonomous purchases that are awkward on card rails.

No shared platform custody

Sellers receive funds directly, buyers sign with their own wallet, and agents operate from isolated wallets with hard balances.

Built for machine-speed commerce

Agents do not want invoices, checkout forms, OAuth handoffs, and monthly procurement. They need capability calls with payment attached.

Programmable trust boundaries

Per-transaction caps, daily caps, pause controls, pairing, and audit logs define what an agent can do before a transaction exists.

Programmable service calls

Agents pay for API calls, dataset slices, model runs, fine-tune jobs, and gated results without subscription setup.

Human approval when it matters

Buyers can approve checkout with Pera, while trusted agents operate from bounded wallets for low-risk work.

Instant settlement and audit

Every payment settles in USDC on Algorand with limits checked before signing and a real-time activity trail after.

Router, not custody

The user stays in control. The agent gets a bounded balance.

Pera wallet controls the human plane
Agent wallets carry bounded spend authority
Convex enforces policy and audit state
Algorand settles USDC atomically
Start with a seller account