> ## Documentation Index
> Fetch the complete documentation index at: https://apione.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect to APIONE across network environments

> Diagnose local, proxy, container, and remote-service connectivity.

## Separate three configuration layers

| Layer | Purpose | Example |
| - | - | - |
| Model endpoint | Request destination | [https://api.apione.ai/v1](https://api.apione.ai/v1) |
| Network proxy | Network route | A local or corporate proxy |
| Tool and sandbox permissions | Agent resource and command access | Project directories and network permissions |

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:

```bash theme={null}
curl --fail-with-body https://api.apione.ai/v1/models \
  -H "Authorization: Bearer $APIONE_API_KEY"
```

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:

```bash theme={null}
export HTTP_PROXY="http://127.0.0.1:7890"
export HTTPS_PROXY="http://127.0.0.1:7890"
export NO_PROXY="localhost,127.0.0.1,::1"
```

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](https://apione.ai/docs/en/guides/clients.md) · [Choose a model](https://apione.ai/docs/en/models/catalog.md) · [Troubleshooting](https://apione.ai/docs/en/support/errors.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.