Questions about setup, limits, and billing.

Yes. OpenLimits supports OpenClaw, Hermes, Pi, Conductor, OpenCode, Cursor, Claude Code, Codex Desktop, compatible SDKs, and direct API clients.

Every plan includes Opus 5; Claude Opus 4.8 and 4.7, Sonnet 5, Haiku 4.5; GPT-5.6 Sol, Terra, and Luna; GPT-5.5, GPT-5.4, and GPT-5.4 Mini; GLM 5.3, 5.2, 5.1, and 5 Turbo; MiniMax M3; and DeepSeek V4 Pro and Flash. Plans differ by renewal period, priority, and support—not model availability.

Yes. Set the compatible base URL and auth token, then use Claude Code normally.

Yes. Every plan includes the GPT and Codex-compatible models. The same key and dashboard apply.

You need an API key and a compatible base URL. Most clients can be configured in a few minutes.

There are no hidden fees. Plans renew until you cancel. Used access and credits are not refundable.

Day, Week, Max, and Ultimate renew on their listed schedules until you stop renewal from the billing portal.

Future renewals stop. Access remains active until the end of the paid period, and dashboard history stays available.

Provider capacity is pooled across users, so one customer does not need to fund an entire account at peak capacity.

The global guard allows 30 request starts per second. There is no pool concurrency cap for work already in flight.

OpenLimits does not store prompt or completion content. It records routing and usage metadata required for operation, billing, and dashboard analytics.

Control-plane work is designed to complete before streaming begins. End-to-end latency still depends on the selected upstream provider.

Yes, subject to the plan terms and normal upstream availability. The public APIs preserve compatible request and streaming behavior.

Yes. Send supported media and tool schemas through the corresponding provider-compatible API format.

OpenLimits can retry eligible transient account failures. A provider-wide outage still prevents models on that provider from completing requests.