Install Jentic One Beta

Connect the Twin API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Twin 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%2Ftwin.so%2Ftwin-so" | 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%2Ftwin.so%2Ftwin-so" | 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 Twin API.

Create API key

List API keys

Revoke API key

Get authenticated user

Monitor Twin API operational status and events

Use Cases

GET STARTED

Start building with Twin API

Explore with Jentic One

View OpenAPI Document

Automated API Keys Management

Automate API keys operations by combining multiple Twin API endpoints. Agents can list API keys and then revoke API key in a single workflow.

Call GET /api/public/v1/access-api-keys to list API keys, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Twin 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 apiKey tokens manually.

Search Jentic for 'create API key', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

33 endpoints — rest api for managing twin ai web agents, runs, schedules, instructions, and webhooks.

METHOD

PATH

DESCRIPTION

POST

/api/public/v1/access-api-keys

Create API key

GET

/api/public/v1/access-api-keys

List API keys

DELETE

/api/public/v1/access-api-keys/{key_id}

Revoke API key

GET

/v1/me

Get authenticated user

POST

/v1/agents

Create agent

GET

/v1/agents

List agents

GET

/v1/agents/{agent_id}

Get agent

DELETE

/v1/agents/{agent_id}

Delete agent

POST

/api/public/v1/access-api-keys

Create API key

GET

/api/public/v1/access-api-keys

List API keys

DELETE

/api/public/v1/access-api-keys/{key_id}

Revoke API key

GET

/v1/me

Get authenticated user

POST

/v1/agents

Create agent

GET

/v1/agents

List agents

GET

/v1/agents/{agent_id}

Get agent

DELETE

/v1/agents/{agent_id}

Delete agent

Why Jentic?

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

Setup

Wiring the Twin API by hand means managing an x-api-key header against the builder.twin.so host, minting and rotating access API keys, and handling retries yourself. Through Jentic you install once, import the Twin API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

The Twin API puts the agent and key ids in the URL path (/v1/agents/{agent_id}, /api/public/v1/access-api-keys/{key_id}), so a rule can pin your agent to one Twin agent. You choose the operations it may call, so destructive ones like deleting an agent or revoking an access API key are not included unless you add them.

Credential isolation

Your Twin API 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.

Intent-based discovery

Agents search Jentic by intent such as 'create an agent' or 'list access API keys', and Jentic returns the matching Twin API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Twin API through Jentic.

What authentication does the Twin API use?

The Twin API uses an API key passed in the `x-api-key` 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 create API key with the Twin API?

Yes. Use the POST /api/public/v1/access-api-keys endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Twin 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 API key through Jentic?

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

How many endpoints does the Twin API have?

The Twin API exposes 33 endpoints covering API keys, agents, identity operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Twin API operations and credentials the agent may use. You pick the operations it can call, so destructive ones like DELETE /v1/agents/{agent_id} or revoking an access key at DELETE /api/public/v1/access-api-keys/{key_id} are excluded unless you add them. Because Twin puts the agent and key ids in the URL path, a rule can pin the agent to a single Twin agent rather than your whole account.

Twin So Twin API

Name: Twin API
Brand: Twin API
Availability: InStock

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey33 EndpointsREST

For Agents

Programmatically create API key, list API keys. Covers 33 operations with apiKey authentication.

Use for: I need to API key, I want to API keys, Search for revoke API key, Find all authenticated user

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

REST API for managing Twin AI web agents, runs, schedules, instructions, and webhooks. The API exposes 33 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Twin API to your agent

Capabilities

Use Cases

Start building with Twin API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Twin So Twin API