Evidence boundary: The AI SDK documentation describes provider packages and model calls. It demonstrates a developer integration contract, not the infrastructure of a separate production product.
Documented integration pattern
- Install the provider package named in the documentation.
- Load the API key from server-side secrets.
- Select an explicit model identifier.
- Record token, tool, streaming, and error behavior for the chosen route.
Relevant provider records
- OpenAI API · official channel
- Anthropic API · official channel
First-party evidence
- Vercel AI SDK providersFirst-party provider documentation.
What this page does not claim
It does not claim that the project's hosted service uses these providers in production, that the integration handles every feature, or that any private cost or revenue figure is known.
Questions developers ask
Does this page prove Vercel AI SDK's private production stack?
No. It documents only the linked public repository or first-party documentation evidence and makes no private deployment claim.
Does APIDir know this project's provider spend or revenue?
No. APIDir does not infer private usage, cost, customer, or revenue information from a public integration.
How should I reuse this integration pattern?
Open the cited source, confirm its current license and configuration, then test the relevant provider record against your own workload.