Concepts
The terms these docs use: caller, supplier, provider, route, multiplier, tier, and settlement.
On this page
A short glossary. Each term means one thing everywhere in these docs.
Caller and supplier
A caller sends API requests and pays for them. A supplier connects an official provider credential and is paid when that capacity serves a request. One account can be both.
Provider
The kind of official access behind a route — for example OpenAI, Anthropic, Amazon Bedrock, or Vertex AI. Prices are set per provider. A provider is not a person: the people who connect credentials are suppliers.
Route
One supplier’s connected capacity: a saved credential plus the exact upstream models it can serve. Every request is served by one route. Callers never see which supplier owns it.
Official list price
The provider’s own published price for a model. AnyPath keeps a catalog of these prices and uses it as the base of every charge.
Multiplier
The multiplier is the share of the official list price a caller pays: 0.6 means 60%. AnyPath sets one per provider, and it never goes above 1. See Pricing and billing.
Protection floor
A supplier can set the lowest multiplier at which their route should serve. While the provider’s multiplier is below it, the route does not serve, and it resumes automatically when the multiplier is raised to it or above.
Supply pressure
The share of recent requests that supply could not serve, either because the serving account was rate limited or because no eligible route was available. It is what moves the multiplier.
Account tier
Each account has a tier that sets its requests-per-minute and tokens-per-minute limits. Tiers rise automatically with settled usage. See Rate limits and tiers.
Reserved balance
Before a request runs, AnyPath reserves part of the caller’s balance. On success, the actual metered cost is charged and the rest is returned. On failure, the whole reservation is returned. A charge never exceeds the reservation.
Settlement
The accounting after a successful request: the caller is charged, the supplier is credited, and the service fee is taken, all in USDT and all from the same usage figures.
Next
- API Access: create a key and send a first request.
- Pricing and billing: how the charge is calculated.
- Supplier guide: connect a credential.