Noemad Docs
Models, streams, and capabilities
A qualified model route keeps its request contract while adding explicit payment terms.
Choose a qualified route
The product plan preserves familiar Chat Completions, Responses and Messages payloads and streams. Media, files, jobs, realtime, embeddings, rerank and structured evaluation retain their own contracts when enabled.
{
"model": "<qualified-model-id>",
"messages": [
{
"role": "user",
"content": "Turn this product brief into a clear summary."
}
],
"max_completion_tokens": 512,
"stream": true
}Bind the quote
The quote binds the owner, method, path, canonical body, provider, model, rate snapshot, limits, maximum, asset, chain, recipient and expiry. Changing the model or cost-relevant inputs requires a new quote.
Stream without losing payment state
Output can begin after authorization verification. The gateway forwards the qualified protocol’s JSON/SSE and records usage and outcome. Final settlement is retrieved separately; the initial stream headers cannot be updated after delivery begins.
Validate usage and outcome
A successful HTTP status alone does not prove a usable response or billable usage. Missing final usage, a partial stream, a timeout after dispatch, or a crashed worker enters the applicable recovery or reconciliation state.
Provider modularity
Each adapter implements capability discovery, pricing, invocation, usage mapping and health. A different provider/model/rate cannot silently replace approved terms. See provider architecture.