opencommerce
Shop with the customer’s saved card and approval for each order.
Turn on opencommerce in an agent's abilities (features.opencommerce) to let it shop at 5,000+ stores through Agentcard using the shopper's own saved card. This is separate from agent wallets: wallet spending limits and approvals do not apply.
The agent shows the cart and total and waits for the shopper's explicit yes in a new chat message before confirming it. Only USD carts are supported. Agentcard may also ask the shopper to approve the order. The agent sends Vault, approval and store sign-in links verbatim; shoppers should never send card details in chat.
| Tool | Use |
|---|---|
opencommerce_buy | Search and build a cart with ask, or confirm the last shown cart hash after the shopper's yes. Supply exactly one. |
opencommerce_read | Read the conversation and reconcile an uncertain checkout without resending it. |
opencommerce_vault_link | Create a reusable link for the shopper to add a card. |
Opencommerce charges 1% per completed order. Keiki charges the organization a separate fee on placed orders from its ai_tokens platform credits, default 5% of the order total; the rate can be set in Autumn plan metadata as opencommerce_fee_pct. The fee applies whether the platform or organization supplies the Agentcard credentials. Reconciliation happens on the next buy or read; asynchronous webhooks are not included.
The platform's Agentcard company credentials are used by default. Organizations may override them with their own AGENTCARD_CLIENT_ID and AGENTCARD_CLIENT_SECRET developer secrets. Credentials and provider conversation IDs remain server-side.