A storefront, and agents that can take an order inside a limit.
The storefront is a placed app with its data beside it. Skerry gives each agent that serves it scoped keys, spend limits and approvals. Skerry states what is live and what is not, and so does this page.
In short
Commerce on Praecise Cloud pairs a storefront with its data and Skerry payment limits for the agents that serve it. This page is for shops and marketplaces, and states what is sandbox, test mode or coming soon. Start with the storefront, then add a sandbox key.
00
At a glance.
Sandbox
Agent payments.
Sandbox keys work immediately; live keys need approval.
Test mode
Card and wallet payments.
Processed by Stripe, in test mode only, and not open for live payments.
Coming soon
Agent checkout.
Agents paying merchants is not available yet.
01
What is available, and what is not yet.
- 01
Agent payments
API keys scoped per agent, spend limits, approval workflows and revocation.
- 02
Virtual accounts and stablecoin
Routing across USD and EUR virtual accounts issued by Bridge, rule-triggered conversion from stablecoin to fiat, payouts and an exportable record of movement.
- 03
Card and wallet payments
Hosted checkout, payment links, refunds, disputes and subscriptions, processed by Stripe. Not open for live payments.
- 04
Agent tooling
An MCP server, an OpenAPI 3.1 reference and webhooks.
- 05
Agent checkout, separate agent identities and wallets, stablecoin-backed cards
Not available yet.
02
How a store runs here.
- 01
Place the storefront
A Node app or a static export behind the edge.
The storefront is placed like any web app, with a domain and certificate, and its credentials kept outside the release.
- 02
Keep the data beside it
Orders and catalogue live next to the app.
SQL and document stores are provisioned next to the workload.
- 03
Scope the agent
One key per agent, with a limit.
Skerry API keys are scoped per agent, with spend limits, approval workflows and revocation.
- 04
Reach it by tool
Agents use an MCP server.
Skerry offers an MCP server, an OpenAPI 3.1 reference and webhooks.
- 05
Hold the money with partners
Skerry is software, not a bank.
Bridge and Stripe hold and move funds and perform the regulated acts under their own licences.
- 06
Give the agent an address
Customers can write back.
Inbox gives a support agent its own mailbox on your domain, with a searchable record of every reply.
03
Build, Place, Operate for a shop.
Build
Write the store and its agent.
The storefront is an app. The agent that answers customers or takes orders is a Harness folder.
Place
Domain, data and keys.
Place the app, provision its stores, and create Skerry sandbox keys for the agent.
Operate
Approve what matters.
A workflow can stop at an approve step for a refund, and an agent's spend stays inside its limit.
04
Shapes of shop.
- 01
A storefront with a support agent
The agent answers from your policies and replies from its own Inbox address.
- 02
A booking agent that settles through Skerry
Sandbox today; live keys on approval.
- 03
A shop whose refunds wait for a person
A Harness workflow stops at an approve step, then resumes.
- 04
Payouts from a stablecoin balance
USD and EUR payouts through Skerry's partners, with an exportable record of movement.
- 05
A marketplace that onboards businesses
Skerry orchestrates the KYB flow; the partner makes the verification decision.
- 06
Agent checkout
Agents paying merchants. Coming soon, not available yet.
05
Next pages.
06
Praecise accounts are by invitation. Open the console, or talk to us.
New to Praecise Cloud? Accounts are set up with the Praecise team: talk to us, then sign in to the Cloud section of Praecise Spaces with an email code.