Candidate integration checklist

Use this checklist for any tool page with status Candidate setup. A candidate setup is not the same as a production-ready integration.

Required values

Provider type: OpenAI-compatible or Custom OpenAI
Base URL: https://api.nexorouter.com/v1
API key: YOUR_NEXOROUTER_API_KEY
Model: one exact model ID copied from Models

Verification path

1. Create a low-budget key for the tool.
2. Configure one model only.
3. Send one short non-streaming text prompt.
4. Confirm the request appears in Usage Logs.
5. Confirm model ID, key name, tokens, cost, latency, status, and request ID.
6. Test the tool's main workflow with a small disposable task.
7. Keep production traffic off the tool until the workflow is repeatable.

Stop and use another tool if

• There is no custom base URL field.
• The tool only supports native Claude, native Gemini, image, video, audio, or Responses API.
• The tool stores the API key in browser-visible or public config.
• The request does not appear in Usage Logs after a short text prompt.
• The tool silently routes through its own provider.

Support handoff

When reporting a candidate integration issue, include:

Tool name and version:
Provider type selected:
Base URL configured:
Model ID:
Request ID:
Usage Logs status:
Whether a short non-streaming prompt works:

Never include the full API key.