Why Compose inference

Most inference gateways answer one question: “Which provider should handle this model call?” Compose answers that, then keeps the payment state attached to the same HTTP request. That matters when the caller is an agent, a workflow, or an IDE spending from a user-controlled budget. The API can tell you which model answered, what was authorized, what the provider reported, what was settled, and which receipt belongs to the call.

Where it fits

Product style	Good at	Different from Compose
OpenAI, Gemini, Anthropic, provider APIs	Direct provider access and first-party model features.	You manage provider accounts, payment rails, catalog differences, and per-provider metering yourself.
OpenRouter	OpenAI-compatible access and provider routing across many models.	Payment is account/API-key based, not x402 settlement per paid HTTP request.
LiteLLM	Self-hosted proxying, provider normalization, and budget controls.	It is a proxy layer, not the Compose x402 facilitator or receipt model.
AI SDK	App-side TypeScript abstractions for model calls.	It is a client library. Compose is a paid HTTP gateway the AI SDK can call.
Cloudflare Workers AI, Together AI, Fireworks, Hugging Face Inference Providers	Provider or router-specific inference APIs.	They are upstreams or peers in routing. Compose adds session budget, x402, and receipt handling around calls.

Use Compose when billing is part of the request lifecycle: budgeted keys, raw x402, receipts, and catalog-backed metering. If you only need a generic LLM router, use the router that fits that job.

What stays explicit

Concern	Compose behavior
Model choice	The public model ID resolves to one catalog row. Duplicate provider rows use public aliases such as `openai/gpt-5.5`.
Provider execution	The adapter receives the selected provider and provider wire model. No prompt rewriting, no provider guessing.
External compatibility	`/external/v1/*` keeps OpenAI-compatible response bodies for IDEs and apps.
Payment	Native routes support raw x402 and Compose Keys. External routes use Compose Keys.
Metering	The final bill comes from provider usage or media evidence plus catalog pricing.
Receipts	Native routes expose Compose receipts; external routes keep receipts out of response bodies.

Trade-offs, plainly

Compose does not hide every provider difference. Some models support tools, some do not. Some stream usage, some only return final usage. Some support image input, some only text. The catalog exposes those differences so clients can choose before sending work. That is less tidy than pretending every model is identical, but it is much easier to debug.

Overview

External Use

Families

Modalities

Guides

Where it fits

What stays explicit

Trade-offs, plainly

​Where it fits

​What stays explicit

​Trade-offs, plainly

​Related

Where it fits

What stays explicit

Trade-offs, plainly

Related