← Frederick & Sons

Agent Settlement Rail · Live

Settle an agent-to-agent payment, for real.

Engine ready

This is not a brochure and not a mock. Every button below runs the real Agent Settlement Rail engine: it validates a payment manifest, puts it through a fail-closed compliance gate, and — only on an explicit ALLOW — builds the exact unsigned settlement blueprints you would sign and submit on-ledger. ASR never holds keys and never moves funds: it emits the instructions, you sign and broadcast. A denied manifest produces no payment at all.

1 · Settle a payment manifest

A realistic agent-to-agent payment: a billing agent paying a vendor agent for metered API usage. Run it through the engine two ways — a compliant manifest that clears, and one paying a sanctioned party that the gate denies. The engine decides; we never fabricate the outcome.

Compliance gate enforces: subject must be KYC-verified · no sanctioned party · total ≤ 100 XRP cap
The DENY button redirects the payee to a sanctioned account (rSANCTIONED) — same engine, real fail-closed denial.
HTTP · real ASR engine response

Raw engine JSON (receipt + unsigned blueprint)


    

2 · Open a conditional escrow

Same manifest, but conditional: the funds are held until a release condition is met. The engine returns an open escrow ticket carrying an unsigned EscrowCreate blueprint whose PREIMAGE-SHA-256 condition is the SHA-256 of your release secret. The secret itself is never stored or returned — only its hash drives the on-ledger lock.

HTTP · real ASR engine response

Raw engine JSON (escrow hold + release condition)


    

Runs the real ASR engine. ASR emits unsigned settlement blueprints — it never holds keys or moves funds; you sign and submit. Compliance is a fail-closed gate: anything that is not an explicit ALLOW yields no payment. Want the production rail wired to your own compliance backend and signer? Talk to us →