Glossary
Agined's words, in plain language.
The terms you meet in the product, the docs and the record, in four groups. Each term has its own link, so you can send someone straight to it.
01
The catalogue and how agents reach it.
- Catalogue
- The signed list of actions you publish. Publishing turns it into a versioned registry, signed with Agined's Ed25519 key, and the gateway loads only a registry that verifies.
- Action
- One thing an agent may call: a name, input and output schemas, a risk class, the scopes needed, a meter and a confirmation rule.
- Surface
- Your published catalogue as agents see it, served on a host: your own domain or an agined.com subdomain.
- A2PI
- Agentic AI Processing Interface, the name Agined gives to what it is: an interface that lets AI agents call your API under your rules.
- Transport
- The protocol an agent uses to reach an action: REST, MCP, ChatGPT Apps, Gemini, Perplexity, Claude Cowork, A2A or NLWeb. Every transport meets the same gate.
- MCP
- Model Context Protocol. Agents list your actions as tools and call them. Agined's own MCP server is at mcp.a2pi.app/mcp.
- A2A
- Agent2Agent protocol. Agined publishes an agent card for a surface and answers tasks at /a2a; each task runs one action through the gate.
- NLWeb
- A way for agents to find what a site can do in natural language. Agined publishes its manifest at /.well-known/nlweb.json.
- Well-known file
- A discovery document at a fixed path under /.well-known/ that agents read first, such as openapi.json or the MCP server description.
- ActionFlow
- The composer for multi-step flows: typed nodes you connect, run by hand, on a schedule, on events or over MCP.
- Workspace
- The unit that holds your data, keys and settings. A workspace is bound to a data region when you create it.
02
Control over every call.
- Gate
- The ordered checks a call passes before your backend sees it: scope, policy, mandate, access mode, limits and approval. A refusal names the gate that stopped it.
- Policy
- Rules with the effect permit or forbid, written over action, risk class, assurance level, mandate, time windows and more. The first rule that matches decides.
- Decision receipt
- The record of one policy decision, written in the answer the agent gets and on your chain. A refusal names the policy hash and the rule that matched.
- Risk class
- How serious an action is: read, mutation, destructive or billing impacting. It sets the default confirmation rule for platform actions.
- Approval
- A person's sign-off before a call runs. The call waits with HTTP 412 while the request goes to an approver, and the decision is signed.
- Mandate
- Standing authority for an agent, with limits on actions, spend and expiry. The gateway checks each call against it before the call runs.
- Sub-mandate
- A mandate minted from another one. It can only be narrower than its parent, and revoking the parent stops every child.
- Confirmation token
- A single-use token minted for one call. The gateway burns it when the call runs, so it cannot be replayed.
- Kill switch
- A way to switch off an actor, an action, a domain or a whole surface. Agined first counts what the switch would have refused over the last hour.
- Actor
- An agent or client that calls your surface. Each one is listed with its identity, assurance level, spend and decisions, and can be quarantined.
- Idempotency key
- A header that makes a retried call run once. A finished call replays its stored answer for 24 hours.
03
Evidence and the record.
- Hash chain
- A record in which each entry carries the hash of the one before it, so a change anywhere breaks every later link. Each workspace has its own chain.
- Witness
- The evidence-grade record of a consequential agent action. Witness records are hash-chained, append-only and exportable.
- Checkpoint
- Once a day Agined rolls the head of every workspace chain in a region into one Merkle tree and signs it, linked to the previous checkpoint.
- Anchor
- A checkpoint timestamped through OpenTimestamps, which commits it to the Bitcoin blockchain, so it provably existed before that block.
- Attestor
- Agined's service for signed receipts about what software did outside the agent loop. Anyone with the public key can verify a receipt.
- Attestor receipt
- An Ed25519-signed statement that one operation happened. It verifies against a public key at a stable URL, without logging in.
- Notarian seal
- A signed snapshot of evidence, anchored with OpenTimestamps.
- Dispute packet
- One file that proves a call, an approval or a meter event: the record, the chain segment, the Merkle path, the checkpoint and the anchor when there is one.
- Verifier
- A tool that checks a packet, chain or checkpoint offline, with no account and no call to Agined.
- Tops
- The ledger of what Agined's own infrastructure did on your workspace: every ingest, export, key issue and admin read. You can read it; Agined cannot edit it.
04
Metering, regions and the platform.
- Metering
- Every call writes a meter event (the call, the response bytes or a path), kept in segments with inclusion proofs, so each usage line traces back to its calls.
- Access mode
- Free, keyed or paid, set per action. It is checked at the gate on every call.
- Consumer
- A company whose agents call your surface. It has its own account and keys, which you can suspend or revoke one at a time.
- Region
- Where a workspace's data is stored: one of seven Cloudflare regions, or the workspace's own Amazon Aurora database on Scale and Enterprise.
- Refusal code
- A typed reason with a fixed HTTP status, so an agent can tell a missing scope from a used-up quota or a pending approval.