FAQ

Is CanalAPI really OpenAI-compatible?

Yes. The base path is /v1 and the request / response shape matches OpenAI's HTTP API for the supported endpoints (Chat Completions, Responses, Embeddings, Images, Audio, Moderations, etc.). Most OpenAI client libraries work as drop-in clients once the baseURL and apiKey are overridden.

If your codebase is already on the Anthropic SDK or the Google Gemini SDK, you can switch to CanalAPI's native-protocol endpoints — see Endpoints.

How do I find the current model list?

Authoritative sources:

• Public page /models (filter by provider / category, with prices)
• Public page /pricing (price table and FAQ)
• Console → Models (signed-in; shows the models actually available to your account)
• The REST endpoint GET /v1/models

Model names, capabilities, and prices change as upstream providers release new versions and the platform onboards them.

How is usage billed?

CanalAPI supports two billing models, which can be combined:

• Pay-as-you-go (default) — top up the balance, deducted by token cost on each request.
• Subscriptions — pay once per period for a fixed quota; see Subscriptions.

When both are active, subscription quota is consumed first; overage follows the subscription's policy.

What payment methods are supported?

• International cards / Apple Pay / Google Pay — via Stripe
• Alipay — Mainland China QR / app
• WeChat Pay — Mainland China QR / app

The actually-available methods depend on your account region (shown on the Top up page). Subscription orders are processed via Stripe only.

Can I get a company invoice?

Yes. Invoices are issued by the Japanese operating entity under Japanese tax law (Qualified Invoice / 適格請求書). Configure your invoice header (company name, registration / tax ID, address) in Billing → Profile before topping up. Past invoices are downloadable as PDF from Console → Invoices.

Can I use CanalAPI directly from a browser or mobile app?

No — don't embed an API key in client-side JavaScript or a mobile app. That exposes the key to anyone who can read the bundle. Use a server-side proxy (Next.js Route Handler, Express, Cloudflare Workers, …) and call CanalAPI from your own backend.

Issuing short-lived, low-quota, IP-restricted keys per client is possible as a mitigation but still not recommended.

Does CanalAPI store my prompts?

User-facing usage logs record metadata only (token counts, model, timestamps, status, request ID). Full prompt and completion bodies, and tool-call arguments, are not retained. Refer to the Privacy Policy in the console for the authoritative statement.

What about rate limits and 429s?

See Rate Limits:

1. Self-throttle from X-RateLimit-Remaining.
2. On 429, honor Retry-After if present.
3. Otherwise exponential backoff + jitter, capped at ~5 retries.

What happens if I lose my authenticator after enabling 2FA?

The backup codes generated when you enable 2FA each grant a one-time login (and are invalidated on use). If you've lost the backup codes too, contact support via the console for manual identity verification. See Security.

How do I invite friends / earn referrals?

The Referrals page provides your personal referral code, a share link, and a poster. New users that sign up via your link and spend generate commission that can be withdrawn into your account balance. See Referrals.

Where can I report a bug or request a refund?

Use the Support form in the console. Include:

• The request ID (returned in response headers and visible in Usage Logs)
• An approximate timestamp
• A short description and the outcome you expect

Payment disputes / refunds go through the same channel; approved refunds return to the original payment method (or, where appropriate, as a balance credit).