Enjoy waived service fees on top-ups, plus exclusive referral gifts

Service-specific Terms

Effective date: 2026-06-22 ยท Version: 1.1.0

These Service-specific Terms apply to particular OneRouter features. They supplement the Terms of Service and apply whenever you use the relevant feature.

A. API routing and keys

  • API keys are credentials. You must store them securely, rotate them when exposed, and restrict them to the minimum necessary scope.
  • Routing may depend on model availability, provider health, region, pricing, safety filters, rate limits, context length, modality, and account configuration.
  • OneRouter may retry, fail over, queue, throttle, cache metadata, or reject requests to protect reliability, cost controls, security, and policy compliance.
  • Compatibility with any provider API, SDK, endpoint, parameter, or output format may change as upstream services change.

B. Workbench and conversations

The workbench is a paid usage environment for testing and using supported models. It may store conversation history, uploaded assets, model selections, parameters, generated outputs, and usage records so you can resume work and understand cost. You should not enter secrets, production credentials, regulated data, or unnecessary sensitive personal data unless your organization has approved that use.

C. Multimodal generation and uploads

  • Image, video, audio, and file features may require uploads such as reference images, start or end frames, audio clips, documents, or parameter settings.
  • You must have the rights and permissions needed for uploaded materials, including likeness, voice, trademark, copyright, and privacy rights.
  • Generated media may be filtered, watermarked, delayed, failed, degraded, removed, or restricted by safety systems, provider rules, or regional law.
  • Large files and generated assets may have storage limits, expiration times, format limits, download limits, and additional costs.

D. Web search, tools, and agents

Search, browsing, retrieval, function calling, tools, and agentic workflows may send queries, context, files, URLs, tool outputs, and action results to third-party services or customer-configured systems. You are responsible for tool permissions, data minimization, user disclosure, monitoring, and preventing unsafe autonomous actions.

E. Billing, credits, compensation, and refunds

Usage is measured from OneRouter and upstream provider records, including tokens, images, seconds, files, tool calls, retries, storage, and other unit types. Pricing may differ by model, provider, region, feature, priority, or quality tier. Failed-call compensation may be provided when OneRouter can confirm that a charge was incurred for a failed or unusable request, but compensation is not guaranteed for user error, unsupported parameters, policy blocks, provider-side limitations, network conditions, or subjective output quality unless stated in the console.

F. Rate limits, quotas, logs, and monitoring

OneRouter may enforce limits on requests, concurrency, tokens, media jobs, uploads, storage, spend, geographic access, or suspicious behavior. Operational logs may be used for billing reconciliation, abuse detection, debugging, support, security, audit, and legal compliance. You are responsible for monitoring your own usage and setting appropriate limits for your users.

G. Provider changes and availability

Upstream providers may change models, pricing, parameters, safety filters, supported regions, training or retention commitments, and availability without notice. OneRouter may update listings, aliases, logos, descriptions, compatibility notes, or routing behavior to reflect those changes, but does not guarantee that a specific model will remain available.