Skerry: payments agents can make

Money is about to gain a new kind of sender. Agents will pay suppliers, settle invoices, refund customers and move treasury between currencies, often at hours when nobody is watching. The payment system they will use was designed around a person at a trusted screen pressing a button. The gap between those two facts is where the next generation of payment infrastructure will be built.

Skerry is Praecise's answer: payment rails for agents, including stablecoin settlement. It is global payment orchestration, one programmable surface over virtual accounts, stablecoin conversion and cross-border payouts. Bridge and Stripe perform the regulated acts under their own licences.

Payments assume a person

Every rail has its own onboarding, its own file format, its own settlement window and its own reconciliation. Each bank, each corridor and each country is another integration. That was tolerable when a finance team handled the exceptions by hand. It is not tolerable when the payer is software acting on instruction.

The industry has noticed. Google announced the Agent Payments Protocol in September 2025 so that an agent can prove a real user authorised a specific purchase. Visa followed in October 2025 with its Trusted Agent Protocol for agent-driven checkout. Meanwhile stablecoins gained a federal framework in the United States when the GENIUS Act was signed in July 2025. The direction is clear. Agents will pay, and some of what they move will settle in stablecoins. What businesses need is a single surface where that can happen under rules a person set.

One surface, integrated once

Skerry gives a business one programmable interface across accounts, rails and conversions, so it integrates once. It routes across USD and EUR virtual accounts issued by Bridge. It converts stablecoins to fiat automatically, triggered by the customer's own rules, with the partner performing the conversion. It orchestrates cross-border payouts and treasury, so corridors, cut-offs, balances and retries are configured rather than integrated country by country. It sequences end-customer KYB collection, submission and status tracking, with the partner making the verification decision.

The flow has three steps. Customers onboard inside your product, with Skerry sequencing the process and the partner performing the check. Rules for currency, corridor, cost and cut-off select the account and rail. Then Bridge and Stripe perform account issuance, payment processing, conversion and custody, and Skerry records the state and returns it to your systems.

The regulated act stays with the licensed institution

The framing is deliberate and exact. Skerry is a software company. It is the layer that holds the rails together. Bridge and Stripe perform the regulated acts under their own licences: Bridge for virtual accounts in USD and EUR, stablecoin-to-fiat conversion and custody of funds and digital assets, and Stripe for payment processing. Skerry does not operate as a bank and does not hold or take custody of client funds or digital assets.

For an executive, that division is what makes the product usable. Licensing, custody and verification decisions sit with institutions built and authorised to carry them. The business gets orchestration, routing and a record on top.

Built for agents, scoped by people

Skerry treats agents as callers that answer to a person. Agents act on API keys issued by a signed-in person and tied to a verified business or person and its wallets. Each operation names its scope, and a key narrower than the call is refused. Keys can be revoked from the console, and the next call is refused. Sandbox keys work immediately; live keys need approval for the project.

Money movement carries extra care. The payment tool asks the agent to confirm the amount and beneficiary with its principal and requires an idempotency key, so a retry never pays twice. Per-agent spending limits and expiry dates are available on request. Agents reach Skerry over MCP, an OpenAPI 3.1 reference and webhook events. Separate identities for machines and agents are coming soon, and agent checkout is available on request.

Stablecoins and treasury

Skerry supports USDC, EURC, USDB and USDT on Base, Ethereum, Solana and Tron. In the EU only MiCA-compliant coins are offered, so USDT is excluded there. Money comes in through USD and EUR virtual accounts, with deposits converting to stablecoin on arrival. Money goes out as USD by wire and ACH, EUR by SEPA, and stablecoin transfers to addresses or wallets. A standing conversion address converts and pays out incoming funds automatically.

GBP over Faster Payments, MXN over SPEI, BRL over PIX and stablecoin-backed cards are coming soon. Card endpoints are documented, but issuing is not yet enabled.

Who it is for

Skerry is for businesses that need cross-border payments and treasury management without a separate integration for each bank and country. It is for developers who want one API across accounts, rails and conversions. And it is for businesses deploying agents that make payments, where a CTO needs scoped, revocable keys and an executive needs to know that every payment traces to a person who allowed it.

How it connects

Skerry is the payments layer of the Praecise suite. Agents running on Praecise Cloud can call Skerry with their own keys. Ipnops runs payments, accounting, commerce and mail through agents inside limits the owner sets, and Skerry gives those agents rails that reach across borders and into stablecoins. Praecise Inbox keeps the conversations that lead to a payment in the same estate as the agent that made it.

Underneath sit the machines and operating system the suite runs on, Praecise Metal and Praecise Furcate.

Rails worth trusting

Agents will move money whether or not the rails are ready. The useful question is whether each payment can be scoped, refused, revoked and traced to a person, and whether the regulated act is performed by an institution licensed to perform it. Skerry is built on both answers. Read more on the Skerry page.