writrail

Permission infrastructure for onchain agents

Autonomy,
with terms.

Your agent’s next move.
Your terms of execution.

We’re shaping a layer that connects what you authorize with what an agent can do onchain.

Explore the flow
Infrastructure coming soon
An orange execution unit passing through a precision metal gate on parallel rails

Readable mandates.

Scoped actions.

Traceable receipts.

The next layer of delegation

More agency.
Clearer authority.

As agents start to act onchain, every instruction needs a boundary.

Which asset? Which action? How much? For how long? Writrail’s vision is to make those terms readable to people and enforceable at execution.

We’re starting with the connection between a user’s mandate, an agent’s action, and the record it leaves behind.

Follow the architecture

One continuous relationship

From permission
to proof of action.

Authority, made legible

Put intent into terms.

Define the agent, allowed action, spending cap and expiry in one mandate. The goal: know exactly what you’re handing over.

AgentAllocation agentPermissionSwap onlyBudget100 USDCWindow24 hours
Illustrative architecture. Wallet and execution integrations are planned.

Take the idea for a run

Set the terms.
See what happens.

A small, interactive example of delegated authority. Change an action, run it, or revoke the mandate.

The agent’s next action

Ready when you are.

Run 20 USDC, then try 90. See how the remaining allowance changes the outcome.

Execution record

0 actions

Your first action will appear here.
Each record stays linked to this mandate.

The direction ahead

A common language
for delegated capital.

We want wallet teams and agent builders to share a clearer way to request authority, check its limits, and follow what happens next.

Wallet integrations & execution tooling
Coming soon

Writrail / The concept

Authority should
be understandable.

Writrail’s proposed role is to connect readable mandates, scoped execution and traceable records for onchain agents.

We intend to explore existing smart-account and delegation standards, starting with EVM use cases. Actual enforcement will require wallet or contract integration; the on-page example only illustrates the idea.

Permission checks cannot establish that a strategy is profitable or eliminate smart-contract risk. A receipt records an action; it does not guarantee its quality.

Technical background, not announced integrations. No protocol or token has been launched through this website.