Allocate
HarnessRecursiveDBModelsPricingDocs
Sign inTry for free
Try for free
Allocate
HarnessRecursiveDBModelsPricingDocsSign in
Try for freeBook a call
Allocate documentation
QuickstartsYour first inference callUse Allocate from your coding agent
OnboardingGetting accessPush your dataImport mappingData residency
PlatformGatewayRoutesModelsKeysMeter
API referenceCreate a chat completionList models
PlanesPrivate Inference CloudCloudlightCloudheavyLearningAgentsRecursiveDBTraining
Allocate
Try for freeBook a call
Product
Cloud agentsModelsRecursiveDBTrainingMeterPricing
Solutions
HealthcareInsuranceFinancial servicesOperationsAgenciesStartupsSouth Africa
Resources
DocumentationAPI referenceChangelogFree toolsGlossarySecurity
Popular models
Gemini 3.5 FlashDeepSeek V4GPT-5.5Qwen 3.5Best open-weight modelsExplore all
Company
EnterpriseContactBook a demo
© 2026 Allocate. All rights reserved.POPIA ready · security overview
Allocate

Models

The full catalog behind one key, frontier and open weight.

One key reaches every model in the catalog: frontier models and open-weight models, listed with live pricing at allocate.network/models and served through the Gateway.

Listing models

curl https://api.allocate.network/v1/models \
  -H "Authorization: Bearer $ALLOCATE_API_KEY"

Each entry carries the model id, context window, and billed prices in USD per million tokens. See the API reference for the shape.

Pricing

The prices returned by /v1/models are the billed prices, so what you see is what the Meter records. Provider-reported usage is the billing truth; requests are never re-tokenized to compute your bill.

Pinned by you

Models are pinned per Route and per agent. The platform never silently changes which model serves a surface: the customer or an explicit Route change switches them, and the served model is always reported in the x-allocate-model header.

PreviousRoutesNextKeys
On this pageListing modelsPricingPinned by you