> For the complete documentation index, see [llms.txt](https://docs.perceptis.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perceptis.ai/perceptis-api-v1/infra-routing-and-env.md).

# Base URLs and environment

## API base URL

Use the production API origin as your base URL:

```
https://app.perceptis.ai
```

All v1 paths are under:

```
{PERCEPTIS_API_BASE_URL}/api/v1/
```

For example:

* `POST https://app.perceptis.ai/api/v1/generate`
* `GET https://app.perceptis.ai/api/v1/status/{job_id}`

Do not include `/api` in `PERCEPTIS_API_BASE_URL`; client code and examples append `/api/v1/...`.

## Environment variables

| Variable                 | Use                                                         |
| ------------------------ | ----------------------------------------------------------- |
| `PERCEPTIS_API_BASE_URL` | API origin only, for example `https://app.perceptis.ai`.    |
| `PERCEPTIS_API_KEY`      | Your API key from Developer Settings. Store it as a secret. |

Copy [tooling-env.example](https://github.com/Whiteboard-Intelligence/perceptis/blob/main/docs/public/developer/public-api/tooling-env.example) as a starting point.

## Example

```bash
export PERCEPTIS_API_BASE_URL="https://app.perceptis.ai"
export PERCEPTIS_API_KEY="sk-live-per-..."
```

Then call:

```bash
curl -sS "${PERCEPTIS_API_BASE_URL}/api/v1/status/${JOB_ID}" \
  -H "Authorization: Bearer ${PERCEPTIS_API_KEY}"
```

## Organization-specific API hosts

If Perceptis provides a dedicated API host for your organization, use that origin in `PERCEPTIS_API_BASE_URL` and keep the same `/api/v1/...` paths.