Good questions.
Straight answers.

Clydex is an AI API gateway with Google sign-in, keys assigned to a selected pool, separate paid and promotional balances, and request-level usage and billing history. The text API supports Responses and Chat Completions. Availability depends on the active models and published prices shown in Models & Pricing.

No. The current profile handles text JSON and SSE. Tools, agent tool loops, structured output, reasoning controls, media, stored conversations, WebSockets, and Anthropic calls are unavailable. Check your application guidebefore configuring a client; it explains the settings and current compatibility limits.

Usage displays actual input and output tokens. Cached input is a subset of input; reasoning, when reported, is a subset of output. Neither is added twice, and usage has no hidden multiplier. A settled request’s detail shows public rates, its comparable official charge, and the final Clydex charge. Prices are published only after approval and verification; no universal discount is promised.

Promotional rewards: earn $5 in Promo credits for each of your first 20 qualified friends, up to $100. Each eligible invited friend can receive a separate $5 welcome credit after Google sign-in, Telegram linking, and subscription verification, before their first request. Both participants must complete the required verification. The friend’s first completed successful request with positive confirmed usage qualifies after settlement; a Promo request counts.

5% of referred top-ups: when a direct referral redeems a paid code, their referrer receives 5% of its funded portion in the paid API balance. This program continues beyond the first 20 friends and is separate from the promotional campaign. It has no cash or crypto withdrawal and no additional referral levels.

Promo credits are for API use in the Promo pool at standard model rates. They do not receive a paid-pool discount and cannot be exchanged for cash or crypto. The $100 figure is the maximum reward from 20 qualified friends; it is not an instant signup credit. Your own eligible welcome credit is separate.

The free-request campaign has a limited operating budget. When the server pauses the campaign, new Promo requests and new $5 grants stop. Previously issued credits are not automatically removed. Referrals shows the server’s current state; requests and grants can resume only when the campaign is active and all eligibility requirements are met. There is no announced end date or restart date. Credit expiry and the consequences of unsubscribing have not yet been finalized.

The flow is purchase → confirmed payment → delivered code → separate redemption. Buying a code does not immediately increase your API balance. Purchases start at $10 through the configured GM Wallet / GM Pay checkout. Only verified token/network pairs are offered; follow the exact asset, network, amount, fees, and confirmation instructions on that checkout. The MVP has no fiat checkout.

Your purchase history retains access to the same delivered code. If an order is paid but delivery is pending, follow that order’s status. Do not pay again to fix delivery. Redeem the code in Top Up to receive one credit and a receipt.

Yes. A code can be redeemed once by an authenticated account holding the code. Until then, it is a bearer secret: anyone with a copy may try to redeem it, including its original buyer. Share it privately. The buyer sees their purchase and redeemed status, but does not receive the redeemer’s profile or balance.

The referrer of the person who redeems it. The buyer’s referrer does not replace the redeemer’s referrer. Commission is issued once on the funded portion of the redeemed credit, excluding network fees, bonus portions, manual grants, and commission itself. Buying an unredeemed code creates no commission. The referrer sees a pseudonymous referral ID and cumulative paid top-ups and commission, not full email, transactions, or credit codes.

Keep the pending operation in the same browser session and use the recovery action in Top Up. The server recovers the original receipt without another credit. An already redeemed code cannot create a second top-up, even if the first confirmation was lost. Never put a code in a URL or an error report.

Requests reserve funds before generation. Available balance is posted balance minus active reservations. After confirmed usage settles, the final charge is recorded and the unused reservation is released. An uncertain outcome remains pending reconciliation; elapsed time alone does not make it a free request. The final policy for failed or disconnected requests and maximum review time is still being finalized before live launch.

Routine refunds are not offered in the current MVP product policy. Anomalous payments and technical corrections require review and do not trigger automatic reassignment or reversal. Final purchase terms and a verified support contact must be published before checkout opens. Do not send funds outside an enabled checkout. See payment terms.

Clydex’s gateway is designed to keep request metadata, usage, amounts, and status rather than prompt and completion bodies. Generating a response requires processing request content. Identity, Telegram verification, payment, and referral features need their own operational records. Data-processing arrangements, retention, seller identity, and the privacy contact still require final disclosure. The privacy notice is a draft.

A verified Clydex support contact has not yet been published. It is a launch requirement; no response-time guarantee is offered. For a future support request, keep your order or request ID and error correlation ID. Do not include an API key, a credit code, or your prompt by default.