TRANSACTION GUARDIAN / XRPL TOLL BOOTH

See the risk.
Keep the
decision.

Transaction-risk reports for developers and AI agents. Add a risk signal between building an Ethereum transaction and deciding to sign it.

A project of Cargo1500 LLC. No meeting required.

RECORDED EXAMPLE29 SEP 2026

DAI TOKEN APPROVAL

An unlimited allowance.
A reason to review.

High riskReported result
// abridged risk fields
{
  "risk_level": "high",
  "reason_codes": [{
    "code":
    "UNLIMITED_APPROVAL_GRANTED"
  }]
}
Execution
Local Ethereum-mainnet fork
API payment
XRP Ledger mainnet
Verification
Signature + request binding
Internal, operator-funded verification. This abridged display is not a complete signed response or a live check. Read the proof record ↗
THE DISTINCTION THAT MATTERS

The report informs your policy.
Your system controls the signature.

01 / A BOUNDED PROOF

One concrete result.
Not a blanket promise.

On September 29, an operator-funded /tx-simulate-risk call returned a verified, signed high-risk report for an unlimited DAI approval. The payment receipt and XRP settlement were checked separately. Published verification record ↗

01

Simulate, don’t broadcast

The recorded Ethereum transaction ran on a local mainnet fork. It was not broadcast as a real token approval. Example scope ↗

02

Authenticate the report

The v0.8 format binds the report to the request. Callers must verify the signature, request hash, key and freshness. Verification requirements ↗

03

Apply your own decision

A proposed integration could pause an unlimited approval for review. Your application remains responsible for whether to reject, review or sign.

This is internal product verification, not a customer case study or evidence that every transaction type works correctly. Proof limitations ↗

02 / KNOW THE LIMITS

Useful evidence.
Explicit boundaries.

Start with the limitations, not an assumption of safety.

Read the full integration guide ↗

A signature is not a safety guarantee.

It authenticates the report, not the correctness or completeness of the analysis. A low-risk result does not mean a transaction is safe. Report limits ↗

Payment evidence is separate.

The v0.8 report does not sign the XRP receipt or contain raw simulation success, revert, gas or trace fields. Verify the relevant evidence separately. Response formats ↗

Invalid requests can be charged.

Payment currently precedes request-body validation. There is no promised refund or free retry. Review current payment terms before authorizing a call. Charging policy ↗

03 / START WITH A REAL WORKFLOW

Would this help
your agent decide?

Ask for a short written example of the input, risk result and verification steps. Tell us what your existing checks already cover.

Request a written example

Opens your email app. No wallet connection.