canonical: https://jentic.com/apis/zeit.co/zeit

# ZEIT API

zeit.co/main version v2019-01-07. The API exposes 5 endpoints secured with bearer, oauth2 authentication.

## For AI agents

Programmatically create a new webhook, get a list of existent webhooks. Covers 5 operations with bearer, oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Create a new webhook
- Get a list of existent webhooks
- Remove a webhook by id
- Query and filter ZEIT API records by parameters
- Monitor ZEIT API operational status and events

## Use cases

### Developer Tools Operations

Use the ZEIT API to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including create a new webhook, get a list of existent webhooks, remove a webhook by id.

Example prompt: Call POST `/v1/integrations/webhooks` to create a new webhook

### Automated domains Management

Automate domains operations by combining multiple ZEIT API endpoints. Agents can get a list of existent webhooks and then remove a webhook by id in a single workflow.

Example prompt: Call GET `/v1/integrations/webhooks` to get a list of existent webhooks, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call ZEIT 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, oauth2 tokens manually.

Example prompt: Search Jentic for 'create a new webhook', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/integrations/webhooks` | Create a new webhook |
| GET | `/v1/integrations/webhooks` | Get a list of existent webhooks |
| DELETE | `/v1/integrations/webhooks/:id` | Remove a webhook by id |
| GET | `/v4/domains` | Gets a list of domains registered for the authenticating user. |
| GET | `/v4/domains/{name}` | Get a domain for the authenticated user by name |

## Key resources

- **domains** — Manage custom domains to use with ZEIT
- **webhooks** — Manage webhooks where you can receive ZEIT events

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 57 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 38 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 40 / 100
- **View full report:** https://jentic.com/apis/zeit.co/zeit/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the ZEIT API by hand means choosing between its bearer token and OAuth flow, tracking the mix of v1 and v4 paths on api.zeit.co, and coding webhook and domain request handling yourself. Through Jentic you install once, import ZEIT from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** ZEIT puts the webhook id and domain name in the URL path (`/integrations/webhooks`/:id and `/domains/{name}`), so a rule can pin your agent to one webhook or domain. You choose the operations it may call, so deleting a webhook is not included unless you add it.
- **Credential handling:** Your ZEIT token 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 'create a webhook' or 'look up a domain', and Jentic returns the matching ZEIT operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the ZEIT API use?

The ZEIT API uses bearer, oauth2 authentication. 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 create a new webhook with the ZEIT API?

Yes. Use the POST `/v1/integrations/webhooks` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the ZEIT 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 create a new webhook through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new webhook'. Jentic returns the matching ZEIT API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The ZEIT API exposes 5 endpoints covering domains, webhooks operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which ZEIT operations the agent may call, so you can grant listing webhooks or looking up a domain while withholding create or delete. ZEIT puts the webhook id and domain name in the URL path (`/v1/integrations/webhooks`/:id and `/v4/domains/{name}`), so a rule can pin the agent to a single webhook or domain rather than the whole account. Your ZEIT token is held by your instance and injected only for the operations you have allowed.