ZEIT API

Name: ZEIT API
Brand: ZEIT API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlbearer, oauth25 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the ZEIT API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ZEIT 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fzeit.co%2Fzeit" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fzeit.co%2Fzeit" | 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 ZEIT API.

Create a new webhook

Get a list of existent webhooks

Remove a webhook by id

Query and filter ZEIT API records by parameters

GET STARTED

Start building with ZEIT API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use ZEIT API for, with concrete tasks.

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

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.

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.

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

Key Endpoints

5 endpoints — zeit.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using ZEIT API through Jentic.

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.