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

> ## Agent Instructions
> Use the documentation index to find relevant pages, then read the linked Markdown before answering and cite the source URL.
> Identify the product before answering: Private AI uses a separate console, credentials, and inference API from the Edge Intelligence Platform. Do not apply instructions from one product to the other.
> Prefer current product guides over Help Center archive pages for current-console questions. Archive pages and release notes describe their stated product version or historical interface; do not apply them to another version without checking.
> Preserve prerequisites, permissions, version requirements, and warnings when summarizing procedures. Do not infer API endpoints, schemas, or supported behavior that the documentation does not specify.

# API destination and availability

> Understand the default API reference, session-based destinations, and deployment compatibility.

## One API Reference

Everyone uses the same service pages and operation URLs. The documented contract comes from the APIs published at [zedcontrol.zededa.net](https://zedcontrol.zededa.net/api/v1/docs/).

After you connect your console session, the native Mintlify playground uses that session's verified management API origin and Authorization value. The destination is shown in the playground header and in the full URL under **Request code**; there is no cluster selector. Changing a token manually does not change the destination. Without a verified session, no live destination is selected.

## API versions and availability

This shared reference contains all 11 services in the main deployment's published contract snapshot. Signing in changes the request destination, not the documented schema. Other deployments may run different releases or omit operations and fields. Your API permissions still determine which requests succeed.

API path versions such as `/v1`, `/v2`, and `/beta` belong to individual operations. The source specifications' “1.0” metadata does not identify a deployed software release. Contact your administrator if an operation or field is unavailable on your deployment.

## Request URLs

The playground combines the session's management API origin with `/api` and the documented path:

```text theme={"dark"}
https://zedcontrol.zededa.net + /api + /v1/devices
= https://zedcontrol.zededa.net/api/v1/devices
```

Console paths such as `/login` are not part of the API base URL. Custom console domains and edge-device API domains are not interchangeable; the console connection uses the administrator-approved management origin.

## Use the contract in your tools

Each service overview links to its OpenAPI 3.0 document. Downloads use `zedcontrol.zededa.net` as the default server variable and contain no user credentials or cluster inventory. When using your own HTTP client, use the management origin and credentials assigned to your enterprise.

[Connect your console session](https://zededa.mintlify.site/api-reference/authentication.md)