Agents on AlgoCard
Let agents create payment links, verify wallets, and spend within limits.
AlgoCard gives sellers, buyers, and their agents one shared payment primitive: create a payable intent, prove wallet control when needed, sign with Pera or an agent wallet, then settle in USDC on Algorand.
Mental model
Seller
Creates products, services, and checkout links.
Buyer
Approves payment or delegates bounded spend.
Agent
Bridges discovery, ordering, payment, and verification.
AlgoCard
Routes policy-aware USDC settlement and audit state.
For sellers
Use agents as storefront support, checkout creation, and payment-status helpers. A seller can still run the whole flow from the dashboard.
Create a merchant profile in the dashboard.
Add a product or digital service.
Create a checkout link from the dashboard or let an agent create one.
Share the checkout link with a buyer, support agent, or purchasing agent.
For buyers
Use agents to find and buy digital work while you keep wallet control, approval authority, and spend limits.
Open a checkout link and approve with Pera Wallet.
Pair an agent wallet when you want an agent to spend from a bounded balance.
Set per-transaction and daily limits in the agent wallet control panel.
Use verification challenges when support or refunds need proof of wallet control.
Support and refund safety
Verification is a wallet signature, not another account.
A zero-value Algorand transaction with a one-time note can prove control of a wallet. Merchants can use this before trusting a support agent. Buyers can use it to prove they control the wallet tied to a refund request.
Support agent proof
Signed wallet challenges reduce spoofing without asking for private keys, passwords, or recovery phrases.
Refund ownership
Signed wallet challenges reduce spoofing without asking for private keys, passwords, or recovery phrases.
Audit trail
Signed wallet challenges reduce spoofing without asking for private keys, passwords, or recovery phrases.
For agent apps
Agents can read context, discover capabilities, then call MCP tools.
Human users should not need to read protocol docs. Agent apps can use the context and discovery endpoints below to understand how to interact with AlgoCard.
Common agent flows
Checkout link flow
resolve_merchant -> list_products -> create_pay_code -> share checkout URL -> get_pay_code
Agent wallet flow
create_agent_wallet -> user opens pairing URL -> user funds wallet -> get_agent_status -> agent_pay
Identity check flow
request_verification -> user signs zero-value note challenge -> check_verification
Available MCP tools
These are the current tools exposed by the AlgoCard MCP server. TestNet mode is intended for small demo balances and product validation.