canonical: https://jentic.com/apis/unkey.com/unkey

# Unkey API

Unkey's API provides programmatic access for all resources within our platform. Authentication This API uses HTTP Bearer authentication with root keys. Most endpoints require specific permissions associated with your root key. When making requests, include your root key in the `Authorization` header: All responses follow a consistent envelope structure that separates operational metadata from actu. The API exposes 42 endpoints secured with bearer authentication.

## For AI agents

Programmatically query key verification data, create API namespace. Covers 42 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Query key verification data
- Create API namespace
- Delete API namespace
- Get API namespace
- List API keys

## Use cases

### Identity and Authentication Operations

Use the Unkey API to perform identity auth operations programmatically. The API provides 42 endpoints covering core functionality including query key verification data, create API namespace, delete API namespace.

Example prompt: Call POST `/v2/analytics.getVerifications` to query key verification data

### Automated analytics Management

Automate analytics operations by combining multiple Unkey API endpoints. Agents can create API namespace and then delete API namespace in a single workflow.

Example prompt: Call POST `/v2/apis.createApi` to create API namespace, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Unkey API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'query key verification data', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v2/analytics.getVerifications` | Query key verification data |
| POST | `/v2/apis.createApi` | Create API namespace |
| POST | `/v2/apis.deleteApi` | Delete API namespace |
| POST | `/v2/apis.getApi` | Get API namespace |
| POST | `/v2/apis.listKeys` | List API keys |
| POST | `/v2/deploy.createDeployment` | Create deployment |
| POST | `/v2/deploy.getDeployment` | Get deployment |
| POST | `/v2/identities.createIdentity` | Create Identity |

## Key resources

- **analytics** — Analytics query operations
- **apis** — API management operations
- **deploy** — Deployment operations
- **identities** — Identity management operations
- **keys** — API key management operations

## Why Jentic

- **Setup:** Wiring the Unkey API by hand means attaching a root-key bearer token on every call, matching each RPC-style operation to its request body, and handling responses yourself. Through Jentic you install once, import the Unkey API from the API Directory, store the root key once, and your agent calls it.
- **Permission scoping:** The Unkey API is RPC-style and carries its targets in the request body, so scope your agent to the operations it needs, such as getting an API or querying key verifications. You choose the operations it may call, so a write like deleting an API or creating an identity is not included unless you add it.
- **Credential handling:** Your Unkey root key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'query key verifications' or 'list keys for an API', and Jentic returns the matching Unkey operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Unkey API use?

The Unkey API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I query key verification data with the Unkey API?

Yes. Use the POST `/v2/analytics.getVerifications` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Unkey API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I query key verification data through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'query key verification data'. Jentic returns the matching Unkey API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Unkey API have?

The Unkey API exposes 42 endpoints covering analytics, apis, deploy operations.

### Can I limit what my agent is allowed to do with the Unkey API?

Yes. Because you run Jentic One yourself, self-hosted, your own rules decide which Unkey operations and credentials the agent may use. Since the Unkey API is RPC-style and carries its targets in the request body, you scope the agent to only the operations it needs, such as querying key verifications with POST `/v2/analytics.getVerifications` or getting an API with POST `/v2/apis.getApi.` A write like deleting an API or creating an identity is not available to the agent unless you explicitly add it.