Skip to main content

Separate three configuration layers

Changing a Base URL does not configure a proxy. Successful inference does not establish network access for an Agent’s tools.

Test from the actual runtime

Set APIONE_API_KEY in the same terminal as the client and request the model list:
A valid list confirms basic connectivity and authentication for that process. Next, test inference with a model supporting the required protocol. Avoid logging complete authorization headers.

Configure a proxy when needed

Replace the example port with your running proxy’s port:
Proxy-variable support depends on the client and HTTP library. Start CLI tools in a new terminal. Use a desktop app’s supported network settings or launch method. For Node.js clients, check proxy behavior for the actual runtime and client version.

Containers and remote services

  • Inside Docker, 127.0.0.1 refers to the container, not a host proxy.
  • Diagnose cloud-hosted OpenClaw, Dify, and Open WebUI from the server.
  • SSH shell variables do not automatically reach systemd or background services. Configure their environment and restart them.
  • Install a trusted CA for corporate certificates. Keep TLS verification enabled.

Diagnose by error

For DNS failures, check resolution. For timeouts, check outbound routing and firewalls. For TLS errors, check certificates and system time. For 401, check credentials; 403, permissions; 404, protocol and path; 429, budget and concurrency. Include the client version, timestamp, redacted error, and X-Maxx-Request-ID when requesting help. Remove keys and authorization headers.
Integration directory · Choose a model · Troubleshooting