Core Concepts

Eight words carry the whole product. Learn them once and every console screen and API response reads clearly.

Organisation

The top-level container. Your float, policy, agents, operators, and decisions all belong to one org. Invited teammates become operators of that org.

Casper Float

The CSPR pool AgentOps signs from. You deposit into it, then assign per-agent budgets out of it. An agent’s budget is a claim on the float, not a separate wallet — which is why the org can never be drained past what it actually holds.

Agent

A machine actor authorised to request payments and actions. Each agent has an id (agt_...), its own key (ag_...), a budget, and an effective policy. Agents can be suspended or revoked at any time.

Delegated key

The agent’s own Casper keypair, held in the key vault, added to your account as an associated key at weight 1 once your master wallet signs the grant. It lets the agent transact alone while leaving key management to you alone. Distinct from the agent’s ag_ API key, which is only how it authenticates to AgentOps.

Guard Policy

The rules enforced before anything is signed. A policy sets:

• Spend cap — total that may be spent over the policy epoch.
• Per-action max — ceiling on any single authorization.
• Velocity limit — how many authorizations per hour.
• Rail permission — which rails this agent may use.
• Service scope — the allowlist of services it may pay (e.g. svc:casper-paid-api).

Rail

The kind of money movement being authorized. AgentOps is Casper-native:

• casper-x402 — paying an HTTP 402 paywalled API.
• cspr-trade — a CSPR.trade swap intent.
• casper-deploy — a direct on-chain deploy action.

Decision

The record of one authorization request. It carries the full intent, the policy it was judged against, the outcome (ALLOW / DENY), a human-readable reason, the signed header hash when signed, and timestamps. Decisions are immutable — a later state change adds a record, it never edits one.

Idempotency key

A caller-supplied string on every authorize call. Retrying with the same key returns the same decision instead of spending twice. Networks fail; agents retry. This is what keeps that safe.

Anchor

A SHA-256 fingerprint of a decision, written to the Casper GuardRegistry contract by a background worker. Re-anchoring the same decision with a different hash reverts on-chain — which is what makes the audit trail tamper-evident rather than merely stored.