The safety layer for agent money · Arc testnet

Autonomy is
earned.

Repayd lets AI agents move with a spending boundary, a replayable decision trail, and recovery when something still slips through.

AGRBuilt for agents that act in the real world.
Real testnet receipts. Explicit assumptions.
ROUTINE PAYMENT
$180.00Allowlisted · within policy
!POLICY BLOCK
$900.00Reverted · no tokens moved
RECOVERY RECEIPT
$135.00COVEREDSame-block payout · Arc testnet
BOUNDARIES / RECEIPTS / RECOVERYFIG. 01 · REPAYD CONTROL PLANE
One protocol. Three lines of defense.Scroll to explore

Designed to plug into
the agent economy.

CircleArcThe GraphHederaENS

The missing primitive

Your agent can be autonomous
without being unaccountable.

Wallets gave agents the ability to act. Repayd gives the people around them a reason to let them.

01 / BOUNDARY01

Make the safe path the easy path.

Policies are enforced at the account, not remembered in a prompt. Known recipients pass. Unknown destinations pause.

ALLOW
01
HOLD
02
02 / EVIDENCE02

Replace “trust me” with “open the receipt.”

Every action keeps its source, transaction, block, and reason. Chain evidence and local reasoning never blur together.

CALLBLOCK✓ TXHASH
03 / RECOVERY03

Design for the moment prevention misses.

A covered verdict calls a mutual pool and routes the payout back to the owner. Recovery is a protocol action, not a support ticket.

OWNER RECEIVES$135

The live story

Set the boundary before
the first dollar moves.

The agent can propose. It cannot decide alone. Follow one payment through policy, settlement, and proof.

Known payees move. Unknown payees wait.

The agent proposes a payment. GuardAccount checks recipient, amount, velocity, and policy hash before anything reaches the world.

Open the policy workspace ↗
ALLOWLISTED
AgentPROPOSES
GuardENFORCES
WorldSETTLES
$180.00POLICY PASS · 01/04
per-transfer cap $200daily count 1 / 5recipient · Alice
CHAIN RECEIPTS · LOCAL JUDGMENTS · POOL PAYOUTSARC TESTNET / 5042002

The proof layer

Numbers are useful.
Receipts are better.

Everything shown in the demo is scoped, labeled, and traceable. What the chain proves and what the scenario constructs stay distinct.

$135 covered

A same-block recovery for a controlled miss.

Four routine payments, a frozen hold, a mined revert, a clean release, and a payout that closes the loop.

Open the live run ↗
25 / 100

Verdict and reputation mirrored into ERC-8004.

Agent 894341’s validation and covered feedback are indexed on The Graph, alongside the protocol’s own risk data.

Read the agent record ↗

Designed as a control plane

One safety story.
Every surface accounted for.

Repayd’s job is not to replace your stack. It makes autonomous payments legible across it.

Arc

Settlement

Policy and recovery contracts on the Arc testnet, with explorer-ready receipts.

Arc explorer ↗
  • Six contracts on Arc testnet
  • Caps: 200/tx · 1,000/day · 5 tx
  • 30-tx run, 6/6 checks passed
  • $135 same-block payout
The Graph

Memory

Protocol state and ERC-8004 mirrors become one queryable, composable record.

See the record ↗
  • repayd-risk-arc v0.1.3
  • repayd (ERC-8004) v0.1.1
  • Joined by agentId
  • Agent 894341: score 25, −2500@2dp
Hedera

Metering

x402 access and HCS audit trails show the surface beyond a single chain.

Follow the story ↗
  • x402 via Blocky402 facilitator
  • 0.001 ℏ settled per request
  • HCS topic 0.0.10493275
  • Schedule 0.0.10493353
ENS

Identity

A public résumé layer for agents with a history worth discovering.

Explore identity ↗
  • atlasrepayd.eth on Sepolia
  • ENSv2 permissioned resolver
  • Full résumé in text records
  • Resolved, not fixture data

No hidden footnotes

Good safety UX makes the limits obvious.

Start with the story. Inspect the assumptions when you want the depth. The product should never make you decode its architecture before you can use it.

Is this a live product? +

It is a testnet prototype with real Arc transactions and mintable Demo USDC. It demonstrates the protocol behavior; it is not real-money insurance.

What does the watcher actually prove? +

The watcher and attack facts in the demo are explicitly local, scripted inputs. Chain receipts remain chain receipts. Repayd does not label a local signer as a live TEE.

What should I do first? +

Open the live demo, press Run demo, and follow the event journal. Then open the Agent record to see the evidence and standard-registry mirror.

A safer default for agent economies

Let intelligence move.
Give risk a boundary.

Explore the live testnet story. No wallet connection required. No black boxes required.

Start the live demo
LIVE · ARC TESTNETDemo runner idle · live state appears when a run is active.Start a live run ↗