Your licence, your money, your providers. SwapEazi is the decision before each payout.

A file first. Then one call before each payout.

The pilot needs no integration. After it, SwapEazi sits in your release flow as one API or MCP call, with a queue for the payouts a person has to sign off.

Pilot: file in, report out

You send an export of past payouts. They are replayed through the same engine: the route each would have taken under your objective, its release-by date, the approval tier your limits put it in, and what is unknown. Nothing to connect.

Before each payout

One call, POST /api/v1/agent/run, returns for each payout the route under your objective, the release-by date, the approval tier and a signed decision record. An AI agent does the same steps over MCP with route_intent, approval_status and record_release. Try it on sample instructions at /agent.

Approval queue

A payout above the agent's own limit waits for the person your policy names. They approve or reject it with a reason, and the decision is signed onto the agent's record. See the queue with demo data at /approvals.

Recurring payouts

A remembered payout can repeat weekly or monthly. Each cycle is routed again, and a reminder goes out a set number of banking days before its release-by date, with last cycle's landing and any change of route.

Corridor alerts

Recent news and official notices on the corridors you pay into are attached to each payout's options and sent as alerts on watched payouts. News is shown beside a route; it never removes one.

Specifications

OpenAPI at /api/openapi.json, the MCP manifest at /.well-known/mcp.json, and keys and guides on Developers.

What is read, what is kept, and where.

Each statement here is what the code does today. Anything not settled in code is listed under “On request” below rather than stated.

Statements and payout files

Read for one request and not stored. Stripe, PayPal and Adyen payout exports are read by fixed column readers with no AI; other files go to the AI reader. Only the economics of each measured payment are kept.

Names and account numbers

The export readers never take names, emails, card details, descriptions or transaction ids out of a file. Output from the AI reader is verified again so a name or account number cannot reach the result. A payout held for approval carries a beneficiary label read from the instruction, never an account number, and release records refuse anything shaped like one.

Agent runs

A run is returned to the caller and not kept. Payouts held for approval are kept in the organisation's approval queue; items sent from the public demo go to a separate demo queue.

AI processing

Where it is switched on, files and instructions are sent to Anthropic's Claude for that one read. Without it, payout instructions are read by a plain parser, and a file that needs the AI reader is declined with a message rather than guessed at.

Where data is kept

The site and API run on Netlify. Release records, approval queue items and introduction requests are kept in Netlify Blobs. Transactional email, such as keys, approval requests and reminders, is sent through Resend. The full sub-processor list is on Security.

Keys

An organisation key is shown once when it is issued; only its SHA-256 hash is kept, so it cannot be read back. A key acts for its own organisation, and a request naming a different organisation is refused.

Free use

Anonymous use is capped per caller per day. Callers are counted by a hash of their address, never the address itself.

Retention

A request to be introduced to a provider is kept for 24 months, then deleted, or sooner if you ask, as the privacy notice states.

Every decision signed. Every release chained.

A response in a log proves nothing, since a log can be edited. A signed record, checkable against a published key, proves what was decided, about which payout, and when.

Signed records

Agent decisions, approval decisions, release records and reconciliations are signed with Ed25519. Each record names the key that signed it, so it still verifies after a key rotation. Where no signing key is set, a record carries its hash and says it is unsigned; there is no fallback key.

Anyone can verify

Free and without an account: /api/v1/attestations/verify, the MCP tool swapeazi_verify_record, or offline against the public keys published as a JWK set at /api/v1/attestations/keys.

Release records, chained

Each release record carries the hash of the one before it, per organisation, and is never edited. With the organisation's key, GET /api/v1/releases/verify-chain recomputes every hash and names the first record that does not hold.

Approvals in the chain

An approver's decision is hashed onto the agent's decision record and signed. A second decision on the same payout is refused.

Agent limits

Your policy sets two amounts. At or below the first, the agent may release alone; up to the second, only with a recorded approval from the role you name; above it, not at all. An amount that cannot be converted to your policy currency is never released alone.

Evidence and unknowns

Every fact on a route is labelled as a verified fact, a provider claim, an inference or unknown. What is not known is listed with the result, not guessed.

What is in place, and what is on request.

The detail, including how to report a vulnerability, is on Security. In short:

In transit

HTTPS on every request, with HTTP Strict Transport Security (two years, includeSubDomains, preload), a content security policy, X-Frame-Options DENY and nosniff on every response.

Secrets

Credentials are held as environment variables on the deployment platform, never in source control. The privileged database key stays server side.

Access

API access is by key: an organisation key for that organisation's own records, a router key for the router. Free use without a key is capped per caller per day.

Certifications

None is claimed on this page. Ask, and we answer as things stand.

A paid pilot, then per payout.

Published prices and what each includes are on Pricing.

Start with your own payouts.

Tell us who you are, the corridors you pay out on and roughly how many payouts a month. We reply by email. For a security questionnaire or a data processing agreement, say so in the subject.