Pricing / Routes / api-usage

API Usage Pricing Route

A route type describes the purchase or access path. Pricing model, direct plan rows, purchase track, and pricing owner remain separate fields.

4 route facts · 3 tools
01

Route definition

Route taxonomy is about access path, not price level, ranking, buyer fit, or editorial guidance.
Definition

Developer or system access purchased through metered API usage.

Use when

The official pricing source defines API meters such as requests, tokens, jobs, minutes, or compute.

Do not use when

API is only a delivery mode and has no separate pricing or access route.

02

Model coverage

Current formal records can combine this route with multiple commercial models. The model describes charging logic; the route describes the access path.
Models in current records

Observed commercial models

Canonical model patterns

Expected model contexts

03

Route facts

Route rows carry source URL, checked date, primary marker, and optional pricing owner boundary.
toolroute labelprimarypricing modelstarting priceunitpricing ownersourcechecked
Hugging Face Inference Endpoints
hugging-face-inference-endpoints
Dedicated endpoint computeprimaryUsage BasedNo numeric price assertedcompute timeCurrent entityhuggingface.co/docs/inference-endpoints/en/pricing2026-05-06
Pinecone
pinecone
Standard usageprimaryUsage Based$50/month minimum usageusageCurrent entitywww.pinecone.io/pricing/2026-05-06
Unstructured
unstructured
Pay-As-You-GoprimaryUsage Based$0.03 / pagepageCurrent entityunstructured.io/pricing2026-05-06
Unstructured
unstructured
Free pagesNoFree$0pageCurrent entityunstructured.io/pricing2026-05-06
04

Evidence and ownership

Route facts should be source-backed. Missing source or owner fields stay visible rather than being inferred.
Route facts
4

Current records with this canonical route type.

Primary routes
3

Tool records where this route is the primary pricing route.

Source URLs
4

Route facts with a route-level source URL.

Owner boundaries
0

Route facts where exact prices belong to another canonical entity.

05

Evidence requirements

These requirements prevent route pages from becoming unsupported pricing claims.
Required evidence

Official API pricing source

Required evidence

Meter or usage unit where visible

Required evidence

Pricing checked date