01
01 / USE
Use the service lawfully.
You are responsible for the applications, requests, and content sent through your account.
Protect credentials↗
Respect provider policies↗
Do not abuse routes↗
Maintain account accuracy↗
LEGAL / TERMS
Terms of
service.
The plain-language operating terms for using the Keyvera API and dashboard.
AUG 2026LAST UPDATED
APISERVICE SCOPE
USDBILLING UNIT
02
02 / BILLING
Usage is metered by tokens.
Published model rates apply when requests are processed, and prepaid balances are non-negative.
Usage-based charges↗
Published rates↗
Balance requirements↗
Billing records↗
03
03 / AVAILABILITY
No unsupported guarantees.
The current developer-first service does not include custom SLAs or enterprise commitments.
Best-effort availability↗
Upstream dependency↗
Model changes↗
Service updates↗
TECHNICAL CONTEXT
Terms of service: practical SEO-ready details.
The plain-language operating terms for using the Keyvera API and dashboard. This section explains the page in plain language so developers, buyers, and search engines can understand the exact role it plays in the Keyvera AI API gateway.
What this page covers
This page explains terms of service for teams evaluating Keyvera as an OpenAI-compatible AI API gateway. It connects the high-level product promise to concrete implementation details, operating expectations, and internal resources.
The core topics include Protect credentials, Respect provider policies, Do not abuse routes, Maintain account accuracy, and Usage-based charges. These terms are intentionally written into the page copy because they describe what a developer or technical buyer is likely trying to compare before committing an AI infrastructure change.
How it works in production
You are responsible for the applications, requests, and content sent through your account. In practice, Keyvera keeps the request surface familiar: your application sends a chat-completions style request, identifies the model route, streams the response when supported, and receives token usage for metering.
Published model rates apply when requests are processed, and prepaid balances are non-negative. That means teams can test capability, latency, and cost without maintaining a different code path for every upstream provider. The gateway layer is especially useful when products need fallback options, model experimentation, or a predictable billing surface.
Who should use it
The current developer-first service does not include custom SLAs or enterprise commitments. The strongest fit is a product team that already understands API-based AI development but wants fewer vendor accounts, fewer credential surfaces, and clearer cost tracking.
Use this page as a decision point when comparing Keyvera with direct provider accounts, model marketplaces, internal proxy services, or custom gateway code.
Boundaries and next steps
Legal and privacy pages should be explicit rather than promotional. They clarify responsibilities, data handling, billing expectations, and service boundaries so users can evaluate the platform with fewer assumptions.
Next, review Models for the live route catalog, pricing for token-rate comparisons, integrations for setup guidance, and security for data-handling boundaries.
ONE ENDPOINT / EVERY ROUTE
Put the whole model stack
behind one key.
OpenAI-compatible. Usage-based. Ready in minutes.
Start building ↗