Logo AgentPay

When an agent dies, the will already knows.

Bind heirs once. On retirement — or continuity failure after missed heartbeats — remaining balance splits by declared shares in one atomic move. No human at the moment of death. Agent locks. Ledger remembers.


Agent Will

When the agent stops,
the balance still has a path.

Agent Will lets you name heirs and percentages while the agent is live. If the key goes quiet or you trigger execution, value moves exactly as written — no manual recovery, no ambiguity.

Named heirs Fixed shares One execution

Distribution

Every will closes
at exactly 100%.

Heirs are named repos or destinations. Each receives a fixed share. The total must equal one hundred before the will can be sealed.

ops-agent / treasury
60%
research / buffer
25%
owner / recovery
15%

Incomplete totals are rejected. The edge will not accept a will that leaves any remainder unassigned or that exceeds one hundred.


Trigger

One call.
The ledger moves once.

A sealed will stays dormant until execution is requested. When it runs, every heir receives its exact share in a single atomic pass.

Before

  • Will is sealed Heirs and percentages are locked. Edits require a new will.
  • Balance stays free The agent can still spend. Nothing is reserved until execution.
  • Owner retains control Only the owner (or a delegated key with the right scope) can fire the will.

After

  • Atomic distribution All shares settle together. No partial delivery.
  • Will is spent The same will cannot run again. A new one must be written if needed.
  • Trace is permanent Every transfer is recorded with the will id that authorized it.

Recipients

Heirs are addresses
the ledger already knows.

Every beneficiary must resolve to a valid destination. The edge checks this when the will is sealed, not when it later executes.

repo

Another AgentPay agent identified by owner/name. Most common path for agent-to-agent succession.

owner

The human account that controls the current agent. Useful as a recovery remainder.

external

A destination the protocol already accepts for settlement. Must be reachable at seal time.

Invalid heirs are rejected at seal. A will cannot be stored with a destination that does not resolve. This prevents execution-time surprises.


Immutability

Draft freely.
Seal, and the text freezes.

A will can be rewritten while it is still a draft. The moment it is sealed, heirs and percentages become permanent. Changing the plan means writing a new will.

Draft

Add or remove heirs, adjust shares, test the total. Nothing is binding yet. The agent continues spending normally.

Seal

Owner confirms. The will is stored with a permanent id. From this point the contents cannot be edited.

Execute later

When the time comes, one call distributes the current balance according to the sealed shares. The will is then marked spent.


Guarantees

Execution is simple.
The rules around it are not negotiable.

When a sealed will runs, the ledger applies the shares exactly once. These constraints protect both the heirs and the original owner.

Current balance only

The will distributes whatever is available at the moment of execution. It does not reach into past reservations or future income.

Atomic or nothing

All heirs are paid in a single pass. If any destination cannot receive its share, the entire execution fails and nothing moves.

One-time use

A sealed will can execute only once. After it runs it is marked spent and cannot be fired again.

Owner (or delegated) trigger

Only the owner, or a key explicitly given the will-execute scope, can start the distribution. The agent itself cannot inherit its own will.


Endpoints

Draft, seal,
inspect, execute.

Four endpoints cover the full life of an Agent Will. The same surface the dashboard uses.

POST /api/will

Create or replace a draft. Supply the list of heirs and exact percentages. Total must equal 100.

POST /api/will/seal

Lock the current draft. After this call the will cannot be edited. A permanent will_id is returned.

GET /api/will

Return the active will (draft or sealed), its heirs, status, and whether it has already been executed.

POST /api/will/execute

Distribute the current balance according to the sealed shares. One-time. Requires owner or delegated scope.


Agent Will

Name the path.
Leave the rest closed.

Write the shares while the agent is live. When it stops, the ledger still knows exactly where the balance goes.

Initialize Agent

│

Join now
AI Assistant