Client compatibility
Subscription relays expose the transport needed by their native clients. They are not general proxies for the account’s website, personal chat history or every provider API.
Use the generated base URL and setup returned for your link. Model availability and feature compatibility are checked independently: inclusion in a union catalog does not guarantee another member can continue the same turn.
Codex and ChatGPT
The ChatGPT relay accepts Codex HTTP Responses with store: false and a complete inline transcript. It rejects stored previous_response_id/conversation/item references, saved prompts, uploaded file IDs and account-connected tools outside the accepted Codex shape. Send continuation history inline rather than asking Modem to retrieve a personal ChatGPT conversation.
Supported native desktop metadata reads receive minimal or empty local responses after relay-key authorization. Existing ChatGPT conversation lists, recents and unrelated personal account data are not forwarded from the account. These compatibility responses do not describe the account’s existing conversations. Native account/usage/reset-credit widgets can consequently show placeholder empty or unknown values. Use Modem’s subscription details for actual observed quota and credits; do not interpret a local compatibility response as the provider’s balance.
Grok
Grok supports inline Chat Completions and Responses. Responses are non-stored; stored response/conversation/prompt/file references and background requests are unavailable.
The relay preserves encrypted reasoning, tool context and compaction items. The provider’s reasoning documentation describes sending encrypted reasoning items back unchanged in Responses input; it does not establish that every account/model switch will accept them. Under the selected transfer policy it may replay those items unchanged to another eligible member. If the provider rejects opaque state, Modem stops instead of deleting it and inventing a different history. A rejection is not, by itself, proof that all encrypted reasoning is account-bound.
Known native metadata routes receive minimal settings, empty personal conversation/workspace lists and an empty native bundle. /user represents the primary subscription. /billing is a sanitized read of the primary, marked x-modem-subscription-view: primary; it is not summed across members. Unknown routes return an unsupported-route 404.
Claude
NOTE
This section describes the current Claude-enabled implementation. Confirm that the deployment and SDK version you use include it; hosted availability is not established by the source alone.
The Claude relay supports Messages, model discovery and messages/count_tokens. Signed and redacted thinking are preserved, as are inline tool history and results. Provider-managed containers, stored-file references and remote MCP credentials are unavailable through this relay.
The provider’s thinking documentation requires preserving thinking through tool-use turns and identifies model-specific account/link restrictions. Modem’s strict selector limits those known model families to a known account/organization. That selection rule is not a guarantee that the provider accepts every same-organization replay. An unspecified model family establishes neither portability nor account binding. The provider can still reject a replay. Modem preserves the supplied thinking and explains the incompatibility rather than stripping signatures or resubmitting altered history.
Reported thinking modes, reasoning-effort support and output budgets also affect selection. The default rejects incompatible features; a server-configurable downgrade policy may adapt supported controls without discarding opaque history. It cannot make provider-managed state transferable.
Token counting selects a compatible account and holds its shared capacity. It bypasses included-quota generation admission and does not debit a generated-request allowance. It therefore must not be treated as proof that an actual generation request will pass the link’s usage/rate rules or provider quota. Unsupported Claude metadata routes return 404; no personal-account API proxy is provided.
Cancellation and continuation
Cancelling closes the active request; it does not move its stream to another account. Usage already produced may still count. Preserve the native client’s saved inline transcript for continuation/resume. If required state cannot transfer, stop and resolve the compatibility error rather than removing tool results or reasoning blocks.
Prompt caches are provider-managed. Account affinity may preserve cache locality, but switching accounts does not guarantee a cache hit or transfer cached resources. Claude’s cache isolation rules distinguish workspaces/organizations and require matching prompt prefixes; these API rules do not establish a shared cache across subscription accounts. Do not assume an equal model name implies identical features, account state or cache behavior.