Identity and call name
Confirm the formal model identity and current user-facing call ID instead of inferring it from a similar name, display label, or retired variant.
Model verification
AI Model Verification From Model ID and Protocol to Actual Output
Model verification helps you check the model ID, endpoint, required features, actual output, usage, and charges. Repeat the checks when the model or endpoint changes.
A verification result applies only to the reviewed date, exact model, endpoint, and tested parameters. It does not prove that a provider will never change, nor does it automatically cover untested tools, multimodal inputs, context limits, or media specifications. Current availability still comes from the live catalog, real requests, and recent notices.
Minimum checks for a model
Protocol and endpoint
Send real requests through the endpoint declared for OpenAI, Anthropic, Gemini, images, video, embeddings, or reranking, then inspect the request and response format.
Capability and specification
Record only text, tools, images, audio, video, duration, resolution, and input modes that were actually tested rather than applying family-wide claims to every variant.
Pricing and settlement
Check the model’s price and billing unit, then compare the charge with usage in your account records.
Model updates
Retest the features your application needs after a model, price, or endpoint changes. See platform announcements for updates and retirements.
A reproducible verification workflow
- Choose a model from Models and Pricing. Record its model ID, endpoint, and test date.
- Use a few requests to test the features you need. Save the request parameters, response, and usage.
- Check complete responses, streaming output, and errors. For image and video tasks, wait for completion and inspect the generated files.
- Calculate the cost from the model’s price and actual usage, then compare it with the charge in your account records.
- Record the features and limits you tested. Repeat the relevant checks when changing models, endpoints, or parameters.
What verification does not prove
- One successful request cannot prove that every parameter, date, region, or client will always succeed.
- An identical model name does not prove that a third-party route has adopted the provider’s latest service version; that exact endpoint still requires validation.
- See the integration guide for supported parameters. Experimental or provider-exclusive features may be unavailable.
- Verification is not provider endorsement, a partnership claim, a performance ranking, or an absolute availability promise.
Choose a model by task
Test results apply to the model, endpoint, and parameters used at the time of testing.