API key and access recovery
Lost keys, revoked keys, dashboard sign-in, user role changes, and production access requests.
Include the account email, key name if known, and the route or model you were trying to use.Send the right details once and TVP support can trace API keys, usage, model routes, endpoint behavior, and account status without back-and-forth.

TVP support is built around the same operating signals buyers use: live catalog state, endpoint metadata, key status, billing records, and gateway usage. That keeps support requests tied to the exact model, provider, key, or checkout event involved.
Lost keys, revoked keys, dashboard sign-in, user role changes, and production access requests.
Include the account email, key name if known, and the route or model you were trying to use.Credit balance questions, failed checkout, invoice review, usage spikes, and spend-cap planning.
Send the account email, approximate timestamp, and any request ID or checkout reference you have.Model availability, endpoint failures, unsupported parameters, latency changes, and routing questions.
Include model ID, provider, endpoint route, request body shape, and the error response if available.The best support tickets include the account, affected route, timing, and visible error signal. Use the checklist below before sending production issues.
Tell us whether this blocks production traffic, testing, billing, or account access.
Include request IDs, model IDs, timestamps, dashboard screenshots, or provider response text.
TVP triages account, billing, gateway, and provider issues separately so the fix path is clear.
Email TVP support with account context, model or endpoint details, timestamps, and screenshots for the fastest review.