Tutorial · Task guide

Configure BYOK and Fix 401, 404, 429, or No-Model Errors

Updated · 2026-08-10Public document

Direct answer: Open Me → AI Models & Services, pick the provider that issued your key, paste it, and run Test connection. For a custom provider, enter the full versioned API base (for example, https://api.example.com/v1) and let the client append relative endpoints. Then import models from upstream /v1/models or add the exact model ID manually, verify its modality, and select it under Default model configuration. Diagnose 401 as credentials, 404 as host/path/model, and 429 as quota or throttling.

Before you start

A key copied from the provider's official console, with required billing/project permissions enabled.
The provider's documented API base URL and model ID; a chat-web subscription is not automatically an API entitlement.
Network access to that host from the phone.

Where to find it

Me > AI Models & Services
Provider > Test connection
Provider > Import from upstream /v1/models
Default model configuration
Me > Request records

Step-by-step

Choose the matching provider
Open Me → AI Models & Services and search for the company that issued the key. Use a built-in preset when available; use Add custom provider only for a compatible gateway or self-hosted endpoint.
Enter credentials without exposing them
Paste the key into the protected field. Do not include labels, shell syntax, quotes, or spaces copied around the key. Never place it in screenshots, logs, or support messages.
Set the API host once
For custom providers, set the full base including its required version prefix. Do not add /chat/completions at the end: Foreverse appends the relative endpoint for the selected protocol.
Test, then add models
Run Test connection and review the exact status/provider message. In the provider's model section, choose Import from upstream /v1/models or Add custom model, select the exact ID, and verify its text/vision/image/speech/video modality instead of assuming every returned ID supports everything.
Assign defaults and make one small call
Open Default model configuration, set the relevant modality, then run a short test from the actual Reader/chat/media surface. Check Me → Request records for status, latency, tokens, and channel.

How to know it worked

Test connection reports success and the expected host/provider.
At least one enabled model appears in the correct modality picker.
The actual feature completes a small request.
API request records show BYOK, the expected provider/model, and no secret value.

Cost, data, and irreversible-risk notes

A connectivity test may be a real API request. Your provider may bill it even when the output is tiny.
BYOK usage is billed by the provider, not deducted from Foreverse credits. Foreverse cannot refund a charge made directly by a third party.
Keys are encrypted on-device and should never be copied into reports. Requests go to the host you configured, so verify custom gateways before sending private text.
A failed client display does not always prove the upstream accepted nothing. Use provider usage plus API request records before repeating expensive media calls.

Troubleshooting

401 / 403 unauthorized or forbidden

Likely cause: Wrong/expired key, missing project permission, incompatible auth header, or key and API host belong to different services.

What to do: Generate or copy an API key from the correct provider project, confirm API billing/access, remove surrounding spaces, and retest against that provider's documented host.

404 not found

Likely cause: The base host lacks the version prefix, includes an endpoint twice, uses the wrong protocol, or the model ID does not exist there.

What to do: Use the provider base exactly once (commonly ending /v1), remove /chat/completions from the host, confirm protocol and model ID, then test again.

429 / quota exceeded / rate limit

Likely cause: Account balance, requests-per-minute, tokens-per-minute, or concurrency limit was reached.

What to do: Check the provider console for the precise quota, wait for reset, reduce concurrency/output, add billing if intended, or switch to another configured provider.

Test succeeds but the model is missing

Likely cause: The model was not enabled, was classified under another modality, or the provider's list endpoint did not return it.

What to do: Open the provider page, enable or manually add the exact documented model ID, set its supported modality, then reopen the feature picker.

TLS / network / timeout

Likely cause: The host is unreachable from this network, certificate is invalid, proxy/VPN policy interferes, or the upstream is slow.

What to do: Verify the URL in the provider docs, try a normal reachable network, remove untrusted interception, and check provider status. Do not disable certificate validation.

Frequently asked questions

Should the API host include /v1?

Include the provider's complete documented version prefix. Do not append an operation path such as /chat/completions; Foreverse adds relative endpoints.

Why does my ChatGPT/Claude/Gemini subscription key not work?

Consumer chat subscriptions and developer API billing are usually separate products. Create an API project/key and enable its billing or quota in the provider console.

Can I mix official models and BYOK?

Yes. Defaults are per modality and features can choose a model. For example, text can use BYOK while image generation uses the official channel.

Sources and verification

Models and Usage guide · Foreverse · Verified 2026-08-10

Coverage and verification

Platform	Android model settings
App version	v76+
Path verified	2026-08-10

Third-party names and logos mentioned on this page belong to their respective owners. 文中提及的第三方名称与标识归各自所有者所有。

← Tutorials & Help

Before you start

Where to find it

Step-by-step

Choose the matching provider

Enter credentials without exposing them

Set the API host once

Test, then add models

Assign defaults and make one small call