| Term | Meaning |
|---|---|
| Organization | The top-level account boundary — your company or personal space on the grid. Members, teams, projects and wallets each belong to exactly one organization. (API payloads call it a tenant.) |
| Team | A group of members inside an organization that owns projects. Team membership alone grants no project rights. |
| Project | The unit that consumes and pays. It holds the wallet, the product assignments, the API keys and the sandbox products; every call names one. |
| Personal workspace | The organization provisioned automatically on your first sign-in, with a managed team, a managed project and a wallet — no setup required. |
| Project Wallet | The money attached to one project. Every call reserves and settles against it, and a project without funds cannot call a paid product. |
| Top-up | An organization Owner adding funds to a project wallet. |
| Micro-USD | The ledger unit: one millionth of a US dollar. Every price, hold and charge is integer micro-USD. |
| Reservation | The hold placed on the project wallet when a call is admitted, covering the call's maximum possible cost. |
| Settlement | Once the provider answers, the actual metered cost is charged against the reservation. |
| Release | The unused part of a reservation returned to the available balance — in full when a call is refused before reaching a provider. |
| Product | A model or media capability defined by the platform and offered for consumption at a frozen price. |
| Product version | The immutable published snapshot of a product — provider, model and price never change once published. |
| Deployment | The reviewed, published form of a product: immutable, priced, and the thing an assignment refers to. |
| Assignment | Binding an exact published product version to a project. Without one the project cannot invoke the product; removing one refuses new calls immediately. |
| Invocation policy | An Owner-managed named restriction — model allowlist, daily/monthly spending ceilings, an output-token cap, guardrail packs — scoped to an organization or one project. Every applicable policy stays in force at once. |
| Guardrail pack | PII, secret and prompt-injection screening composed into an invocation policy at observe, mask or block strength. A block happens before any money is reserved. |
| API key | A project-bound bearer credential (aig_…) for the /v1 API. One key belongs to exactly one project, is revealed once at creation, and can carry its own model list, spending limit and expiry. |
| Playground | The in-console chat surface. It uses your signed-in session instead of a key, but shares the API's admission, reservation and settlement path — real calls, real charges. |
| Sandbox product | A project-private flow built in the studio from typed nodes, callable only by its owning project. It never appears in any catalogue. |
| Revision | An immutable saved state of a sandbox product's graph and contract. Activating a revision deploys it; a saved revision never changes. |
Glossary
The grid's vocabulary in one place.
Was this page helpful?Thanks — noted.