Terms of Service
API passes, metering, upstream compatibility and refund entitlement handling.
Last updated: 2026-10-18
Service and compatibility
Relay Station issues customer keys and forwards requests for a chosen model group to configured upstreams. You or your client choose the group; this service does not automatically split tasks. The current API supports OpenAI Chat Completions JSON, SSE and tool-call forwarding. Native Claude Messages and Codex Responses endpoints are not available. Verify each client before relying on it.
Availability and response quality depend on upstreams. Published model names are operator-checked snapshots, not a guarantee that every call uses a particular model. Keep alternatives for workloads that cannot tolerate interruption.
Passes and usage
A pass is a one-time purchase of validity time, without automatic renewal. Prices and limits are those shown at purchase and recorded with the order. Limits are shared per account, count input plus output tokens, with daily tokens resetting at 00:00 UTC (07:00 in Vietnam) and hourly/request limits remaining rolling. Requests spanning midnight count toward the UTC date they started. Missing usage or interrupted responses may be conservatively estimated. Explicit authentication, parameter and rate-limit rejections before generation consume a request but no tokens.
Pausing a key does not pause pass time. Rotating a key preserves expiry and account usage. The old key stops accepting new requests; running requests may finish. Protect your email and keys and rotate a leaked key in the user center.
Payments, refunds and disputes
Live checkout is available only after provider and deployment acceptance has been completed and the channel enabled. Demo orders do not charge money. Request a refund through a support ticket; an administrator will review the order and usage and respond with a proposed resolution. There is no automatic refund button and approval is not guaranteed.
After Stripe confirms a refund, the cumulative refunded proportion of that order's purchased days is subtracted from the pass's current remaining time, stopping at zero. The calculation uses all days purchased in that order; elapsed time is not separately restored. Duplicate notifications do not repeat the deduction. Renewal refunds use that renewal's days. Orders refunded before delivery are held for administrator reconciliation.
An open or lost payment dispute suspends new requests on the associated pass. Winning the dispute restores access if no other restriction applies and the pass is still valid. Expiry continues during suspension. An administrator can reconcile interrupted notifications. Applicable legal requirements take precedence.
Accounts and acceptable use
Do not attack the service, bypass limits, send spam or infringe others' rights. Serious abuse may result in suspension. For account closure, data or billing questions, submit a support ticket from the user center. Self-service account closure is not available.
The date above changes when these terms are updated. Service or upstream changes may affect availability. Retain important outputs and verify practical compatibility.