Problem
OmniRoute xAI connections today authenticate by API key (metered pay-per-token) or web cookie. xAI has just shipped a native subscription integration for OpenClaw (https://x.ai/news/grok-openclaw) that lets a consumer SuperGrok / X Premium+ subscription back model access directly via a login/OAuth-style connection, rather than per-token API credits — the same pattern OmniRoute already supports for Claude session windows and for antigravity cookie auth.
Users who hold a SuperGrok subscription (currently a $25/mo-billed-annually promo bundled with X Premium+) cannot route that subscription through OmniRoute. The only xAI path OmniRoute exposes is the metered API key, which is separate billing and separate quota from the subscription the user is already paying for.
What we'd like
An xAI subscription/OAuth connection type so a SuperGrok / X Premium+ subscription can back the xai provider, analogous to:
- the existing Claude session-window connections (subscription-backed, not API-key), and
- the antigravity/gemini cookie-auth connections.
Concretely: a connection auth mode where the user completes the xAI subscription login/authorization (matching whatever OpenClaw's new grok-openclaw integration uses), and OmniRoute then routes Grok requests against that subscription's entitlement instead of metered API credits.
Why it matters
Subscription-backed provider auth is already a core OmniRoute strength for Claude and gemini. Grok is the notable gap: the models are in the catalog (grok-4.3, grok-4.20) but only reachable on the metered API path. Letting a SuperGrok subscription back the connection means users route the access they already pay for, at flat subscription cost, with the subscription's own rate limits — consistent with how OmniRoute treats other subscription providers.
Notes
- We have not reverse-engineered the OpenClaw grok-openclaw auth flow; pointing this at whatever mechanism that integration already uses is the intent.
- Happy to test against a real SuperGrok subscription once a connection mode exists.
Problem
OmniRoute xAI connections today authenticate by API key (metered pay-per-token) or web cookie. xAI has just shipped a native subscription integration for OpenClaw (https://x.ai/news/grok-openclaw) that lets a consumer SuperGrok / X Premium+ subscription back model access directly via a login/OAuth-style connection, rather than per-token API credits — the same pattern OmniRoute already supports for Claude session windows and for antigravity cookie auth.
Users who hold a SuperGrok subscription (currently a $25/mo-billed-annually promo bundled with X Premium+) cannot route that subscription through OmniRoute. The only xAI path OmniRoute exposes is the metered API key, which is separate billing and separate quota from the subscription the user is already paying for.
What we'd like
An xAI subscription/OAuth connection type so a SuperGrok / X Premium+ subscription can back the
xaiprovider, analogous to:Concretely: a connection auth mode where the user completes the xAI subscription login/authorization (matching whatever OpenClaw's new grok-openclaw integration uses), and OmniRoute then routes Grok requests against that subscription's entitlement instead of metered API credits.
Why it matters
Subscription-backed provider auth is already a core OmniRoute strength for Claude and gemini. Grok is the notable gap: the models are in the catalog (grok-4.3, grok-4.20) but only reachable on the metered API path. Letting a SuperGrok subscription back the connection means users route the access they already pay for, at flat subscription cost, with the subscription's own rate limits — consistent with how OmniRoute treats other subscription providers.
Notes