Agent Setup
Agent Setup Troubleshooting
Diagnose API key, model, base URL, configuration precedence, streaming, and client compatibility problems.
Use this page after following the setup guide for your agent tool.
Check the connection in order
- Confirm the API key can list models.
- Confirm the configured model ID appears for the same key.
- Confirm the base URL matches the protocol required by the client.
- Check whether shell environment variables override the config file.
- Run a minimal non-tool prompt before testing streaming, tools, or media.
Key and model preflight
export ANYINT_API_KEY="your-anyint-api-key"
curl https://api.anyint.ai/openai/v1/models \
-H "Authorization: Bearer $ANYINT_API_KEY"For an Anthropic-compatible client:
curl https://api.anyint.ai/anthropic/v1/models \
-H "x-api-key: $ANYINT_API_KEY" \
-H "anthropic-version: 2023-06-01"If model discovery fails, fix the key or account access before changing the agent configuration.
Base URL reference
| Client protocol | Base URL |
|---|---|
| OpenAI Chat Completions | https://api.anyint.ai/openai/v1 |
| OpenAI Responses | https://api.anyint.ai/openai/v1 |
| Anthropic-compatible | https://api.anyint.ai/anthropic |
| Gemini-compatible | https://api.anyint.ai/gemini/v1beta |
Do not append a specific endpoint unless the client explicitly asks for a full request URL.
Symptoms and fixes
| Symptom | Likely cause | Next step |
|---|---|---|
401 or authentication error | Missing, invalid, or incorrectly prefixed key | Re-enter the key without extra spaces. Use the auth field required by the selected API family. |
404 or route not found | Base URL includes the wrong prefix or endpoint | Copy the base URL from the table above. |
| Model not found | Marketing name used instead of an account-visible model ID | Fetch the Models API with the same key and copy data[].id. |
| The old provider is still used | Environment variables override the config file | Reopen the terminal and inspect relevant OPENAI_*, ANTHROPIC_*, GEMINI_*, and ANYINT_API_KEY variables. |
| A response starts but never completes | Client and streaming protocol are not compatible for that route/model | Try a minimal non-streaming API request and review the API family's status and limitations. |
| Tool calls fail | Client schema differs from the selected API family | Confirm the client uses the matching tool-calling format. |
| Gemini file input fails | A local path was used as fileData.fileUri | Use a public HTTPS URL or inline data. |
Protect the API key
- Do not paste a real key into public issue reports, screenshots, chat transcripts, or documentation.
- Do not commit local agent settings that contain the key.
- Rotate the key if it has been exposed.
- Use separate keys for different people, projects, or automation environments when possible.
Collect useful support information
When contacting AnyInt support, include:
- the agent tool and version
- the selected API family
- the base URL without the key
- the model ID
- the HTTP status or client error message with secrets removed
- whether model discovery succeeds with the same key
Never include the API key itself.