Shared limits and receipts for AI agent actions
Anlyon enforces one shared allowance, approvals bound to the exact request, and provider-verified outcomes on the actions AI agents take through it.
Anlyon enforces one shared allowance, approvals bound to the exact request, and provider-verified outcomes on the actions AI agents take through it, so adding agents or sessions never adds a way around the limit.
Your agent names an action and passes input. Anlyon holds the credential, makes the call, and returns a receipt with a grade.
First governed action in ten minutes
Let an agent update a file on GitHub without holding your token. End with a receipt graded confirmed.
Govern any HTTP API
Declare what an action changes, and put it under a limit.
What you get
- A shared limit. Every agent, session and key in the environment draws from the same limit, reserved before dispatch. A new session or key does not get a new allowance. See Impact limits.
- A bound approval. The human approves the exact change, and that exact change is what runs. See Bound approvals.
- A receipt with a grade. Confirmed means a read-back matched. Acknowledged means the provider accepted the request and nothing read it back. Unknown means no usable response. Anlyon does not send it again. It stays unknown until a read-back or an operator settles it. Failed, refused and denied mean it did not run. See Receipts and grades.
Works on any API
Put any HTTP API your agent calls under a shared limit, an exact approval and a graded receipt. Declare it as an action over HTTPS. Stripe refunds, GitHub file updates and Resend email sends come with read-back built in, and a verify rule adds it to anything else.
| Action | What it covers |
|---|---|
| Stripe refunds | A refund of an explicit amount on a payment intent, counted in the action’s currency. |
| GitHub file updates | One existing text file, on a branch you name that is not the default branch. |
| Resend email sends | A limit counted in emails, one per recipient. Confirmed is Resend’s record of the send, not inbox delivery. |
| Any HTTPS API | A declared action. You state what one call changes and how to read the result back. |
How it behaves
- Anlyon governs the calls routed through an action. Keep the provider credential in the vault so the action is the path to the provider.
- A limit and a grade apply to a governed action. A governed action has an adapter or a declaration.
- A limit belongs to one environment. Each environment has its own.
- A declared action grades
confirmedwhen its read-back rule matches. With no read-back rule it gradesacknowledged. - A receipt is a database record with provider evidence.
Concepts
Actions
Define a call once, then let your agent invoke it by name.
Impact limits
One allowance for every agent, session and key in an environment.
Bound approvals
An approval tied to the exact request, target and version.
Receipts and grades
What ran, what the provider recorded, and how sure the record is.
Governed effects
The record behind every governed action, from preview to outcome.
Idempotency and retries
Replay an invocation without repeating a side effect.
Secrets
Store a credential outside the model and bind it to a host.
API keys
Create environment-scoped keys and grant only the scopes a caller needs.
When something goes wrong
When the limit is hit
What a refusal looks like, and what to do next.
When approval expires or changes
What happens to a request after its review goes stale.
When the outcome is unknown
How an unknown receipt settles, and what you must not retry.
Build and operate
- Use the TypeScript SDK, the Python SDK or the Anlyon CLI.
- Connect a coding agent with the agent setup prompt, or see how agents can read these docs.
- Separate staging from production with Environments, and route sensitive calls to a person with Approvals.
- Find every operation in the API reference.