Permissions & executionAgent permissions & execution
The Owner reviews a policy and public key, the Agent signs independently, and authorization and payment states remain visible. Explore the permission lifecycle through a local demonstration.
Tech stack
01 / Permissions & execution
The Owner reviews an existing policy, limits, recipients and validity before granting a Session. The execution service signs independently, separating Agent payments from routine Owner actions.
02 / Permissions & execution
A 101 MockUSDC over-limit request is rejected during API preparation. After revocation, a previously signed operation sent directly to the bundler is rejected on-chain. These demonstrate separate checks.
THE BUSINESS & VALUE FLOW
Funds pay for tools and services. An Owner supplies a controlled budget, the Agent pays under authorization, and the provider receives a fee. The product connects task costs to execution authority.
Choose the asset, limits and permitted recipients
Review an existing policy and set expiry
The Agent signs and submits payment independently
Inspect spending and revoke when the task ends
In the demo, an Agent pays 1 MockUSDC. After Owner revocation, subsequent payments under that Session are rejected.
A budget, execution path and expense record for paid tool usage.
Customize an internal enterprise tool or develop a service priced by team, account or usage.
Provider charges, chain execution, account maintenance and infrastructure contribute to the cost of a task.
The current authorization and execution flow is demonstrated on local chain 1337. Real providers, LLM decisions and service billing are custom integration directions. No native reward token is required.
BUILT BEHIND THE EXPERIENCE
A Node runner signs operations that pass through the API, Alto Bundler and EntryPoint into smart-account execution.
Guard validates authorization. The local demo also rejects an operation signed before revocation but submitted afterward.
Separate chain confirmation from API registration. Retry synchronization without repeating a successful authorization transaction.
BUILT BY 0xF1 / 2026-10-19
My development focus connects Owner authorization, an independent Node signer and smart-account execution, including revocation and recovery after synchronization failures.
The local demo submits a previously signed operation directly to the bundler after revocation; it is rejected on-chain. This differs from an API preparation limit check, so the page explains each verification layer separately.
The permission-focused Owner workspace is implemented. Real providers, LLM decisions and full policy creation require separately scoped integration.
EXPLORE THE PRODUCT
An Owner grants a Session, an Agent signs independently, and the Owner revokes it when the job ends. Explore payments, synchronization and rejection after revocation.
Connect task budgets, execution and expense visibility to paid tool calls, internal automation or a wallet permission center.
After authorization, the Agent signs in its own runtime. The Owner does not need to sign each payment.
No. Authorization uses the Agent public address; its private key stays in its execution environment.
Agent Wallet Guard / FONE
Ask an engineering question, share a product idea or discuss collaboration, deployment or extending the software. A short message is enough.
Allow Google Analytics to measure visits and page use? Your inquiry name, email and message are not sent to Analytics. Privacy information