Help

Glossary

One-line definitions of the terms used across the docs.

このページはまだ翻訳されていません。英語版を表示しています。

The words the docs and the API use, in one line each.

Terms

TermDefinition
SlugA model's one id, such as claude-sonnet-5.5. Other spellings resolve to it.
SpellingAn alternative id for a slug: <vendor>/<slug>, a dashed Anthropic id, or <slug>:free.
CatalogEvery model you can call, with prices, context and providers. Listed equals callable.
WaterfallA model's ordered list of rungs.
Rung (route, lane)One way to reach a model: a provider and its model id.
FailoverMoving a request to the next rung after a provider failure, before any output.
Route depthPosition of the serving rung; 0 is the first.
Platform-fundedA rung paid with your credits at catalog price.
Pass-through (BYOK)A rung on your own provider key; your provider bills you.
BYOKBring your own key: connecting your own provider account.
Experiential CloudServing capacity Experiential manages, shown as provider experiential_cloud.
CreditOne cent of platform usage.
Nano-USDThe API's money unit: 1,000,000,000 nano-USD is $1.
HoldA reserved worst-case cost while a request runs; it settles to the actual cost.
Card verificationA temporary $1 hold that unlocks free and promotional models.
Plan discountA percent off list on eligible models for Pro, Max and Ultra.
Daily included allowanceThe credits per UTC day a plan's discounts and plan-free models can use.
Rate-limit tierYour organization's requests and tokens per window, set by what you bought.
Free coreThe free allowance on a few models for verified organizations.
PromotionA time-bound free or discounted offer on a model, with token limits.
Cache readInput tokens served from a provider's prompt cache, at the cached rate.
Cache writeInput tokens stored into a provider's prompt cache, at the write rate.
Prompt captureThe organization switch that stores prompts and responses.
ZDRZero data retention: the provider keeps no request content.
ZDR on requestA route that keeps no content when the request carries a zero-retention constraint.
No-trainingRouting only to providers that do not train on API data.
Provider policyYour organization's rules for which providers requests may reach.
IdentityA group of keys (a team, a product) for usage, budgets and guardrails.
Provisioning keyA key that can also create and revoke other keys.
GuardrailsContent checks you configure per identity on requests and completions.
safety_identifierYour end customer's opaque id, used by resellers for attribution.
Uncensored modelA model with reduced refusals, subject to content moderation.
See also
FAQShort answers
RoutingWaterfalls and failover
Data controlsZDR and capture
Plans and pricingTiers and discounts