Payments your agents can use, inside limits you set.
Skerry orchestrates payments across licensed partners, Bridge and Stripe, who hold and move the money and perform the regulated acts. Each agent has scoped keys, spend limits, approvals and revocation, and Skerry offers an MCP server and an OpenAPI reference. Skerry is a software layer: it is not a bank, a money transmitter or a licensed institution.
In short
Skerry orchestrates payments for agents across licensed partners Bridge and Stripe, with scoped keys, spend limits and approvals. It is for teams whose agents need to pay or be paid inside limits. Agent payments are sandbox today, so start with 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, test mode only.
Coming soon
Agent checkout and cards.
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 responsibility is split.
- 01
Skerry orchestrates
One programmable surface.
It routes the instruction and holds the state.
- 02
Bridge and Stripe execute
Regulated acts stay with licensed partners.
Virtual accounts, conversions and payment processing are performed under their own licences.
- 03
Partners decide verification
KYB is sequenced, not decided, by Skerry.
Skerry collects, submits and tracks status; the verification decision belongs to the partner.
- 04
Agents hold scoped keys
Limits per agent.
Spend limits, approval workflows and revocation apply to each key.
- 05
Tooling for agents
MCP, OpenAPI and webhooks.
An MCP server, an OpenAPI 3.1 reference and webhooks.
- 06
A record you can export
Records of movement.
Conversions with expiring quotes and an exportable record.
03
Use it from Cloud.
Build
Write the agent.
A Harness agent calls Skerry as a tool, through its MCP server or the OpenAPI reference.
Place
Create a sandbox key.
Create a key scoped to the agent, with a limit.
Operate
Approve and revoke.
Hold payments for approval and revoke a key at any time.
04
Payments that fit.
- 01
An agent that pays a supplier
Inside a spend limit, in sandbox today.
- 02
Payouts from a stablecoin balance
USD and EUR through partners.
- 03
Checkout for a storefront
Hosted checkout and payment links in test mode.
- 04
Subscriptions
Processed by Stripe, in test mode.
- 05
Onboarding a business
An orchestrated KYB flow.
- 06
Agent checkout
Coming soon.
05
Questions and answers.
- 01
What is Skerry?
A payment orchestration software layer for agents. Licensed partners Bridge and Stripe hold and move the money and perform the regulated acts.
- 02
Is Skerry a bank?
No. Skerry is not a bank, a money transmitter or a licensed institution.
- 03
What is live today?
Agent payments are sandbox today, with live keys on approval. Card and wallet payments are in test mode. Agent checkout, separate agent identities and wallets, and stablecoin-backed cards are coming soon.
- 04
How are agents limited?
Each agent has its own scoped key with spend limits, approval workflows and revocation.
- 05
How do I start?
Create a sandbox key scoped to the agent, then use Skerry's MCP server or OpenAPI 3.1 reference.
06
Next pages.
07
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.