Models · Verification
Verify Tikway model IDs and billing: request records and evidence limits
Last updated：
When using an AI API gateway, developers need clear model selection, request paths and charges. Tikway’s catalog and request records help check model IDs, protocols, token usage and bills. This guide explains those checks and which details cannot independently prove the upstream model’s identity.
1. Distinguish three kinds of name
A display name helps readers, a request model ID selects a model, and an alias or mapping may connect provider routes. Copy the complete ID from the catalog, then check protocol, endpoint and parameters. Do not construct IDs from display names.
Distinguish changing a provider route from changing a model. If a feature includes automatic switching or fallback, check its applicable rules before relying on it. This guide does not replace unpublished routing or fallback policies.
2. Record the details of one request
Save time and timezone, model ID, protocol, final URL and available response request ID. You do not need to publish your key or private input. After a short request, find the matching console record.
Compare recorded model, status, input/output tokens, cache usage and charges. For asynchronous work, also track the task ID and final state. Client estimates may differ from actual settlement; reconcile using the applicable billing rules.
3. Recalculate ordinary text costs
Check input/output prices in the same billing unit on the model page. Use response usage or record counts, estimate base text costs with the calculator, then check caches, extras and account rules using the billing guide.
Prices can change. Historical bills require prices applicable at that time; a current catalog price alone does not demonstrate an error in an old bill.
4. Understand what each piece of evidence shows
| Information | Useful for checking | Does not independently prove |
|---|---|---|
Request model |
What the client requested | The upstream model actually executed. |
| Response model field | The server’s returned ID | All routing behavior behind that field. |
| Tikway request records | Recorded model, usage and costs | Independent third-party upstream auditing. |
| Repeatable task tests | Capability and compatibility on those tasks | Every task’s behavior or complete provider provenance. |
| Model says “I am model X” | Generated text | Reliable model identity authentication. |
More complete identity checks depend on provider provenance, routing rules and verifiable upstream evidence. Generated self-identification or one test answer is insufficient, and unsupported guesses do not justify claims about another platform.
5. Report a discrepancy with useful records
Collect model ID, protocol, time, request ID, redacted response and billing differences. Omit API keys, full authentication headers and private prompts. Keep original records and compare one setting at a time to preserve a reproducible case.
For data handling and service responsibilities, read the privacy policy and terms. Continue with coding model selection and 401 troubleshooting.