Unkey API

Name: Unkey API
Brand: Unkey API
Availability: InStock

✓ Official Vendor SpecIdentity AuthAuthorizationbearer42 EndpointsREST

For Agents

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

Use for: I need to query key verification data, I want to api namespace, Search for api namespace, Find all api namespace

Install Jentic One Beta

Connect the Unkey API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Unkey API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Unkey API.

Query key verification data

Create API namespace

Delete API namespace

Get API namespace

GET STARTED

Start building with Unkey API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Unkey API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

42 endpoints — unkey's api provides programmatic access for all resources within our platform.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Unkey API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'query key verification data') and Jentic returns the matching Unkey API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Unkey API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Unkey API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.

Unkey API

Connect the Unkey API to your agent

Capabilities

Start building with Unkey API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs