Install Jentic One Beta

Connect the Anjal API to your agent

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

Create email inboxes on a shared or custom sending domain

Send, reply to, and forward messages from an inbox

Search messages full-text across inboxes

Draft messages and organize them into threads and labels

GET STARTED

Start building with Anjal API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Anjal API for, with concrete tasks.

★ Agent-managed mailboxes

An AI agent connected through Jentic provisions an inbox and starts corresponding on a user's behalf: it creates the inbox, sends a message, and reads the reply from the thread. Because the agent discovers operations by intent, a full send-and-receive email loop runs without a developer wiring the inbox and messaging endpoints by hand.

Create an inbox, send a message to a recipient, then list the inbox threads and read the reply

Reseller-isolated email per customer

Anjal isolates resources across workspaces and tenants so a reseller can give each end-customer its own inboxes under one billing relationship. An agent can create a workspace, issue a scoped key, and register a custom domain for that tenant, keeping each customer's mail separate. This supports multi-tenant products without each tenant leaking into another's data.

Create a workspace, register and verify a custom domain for it, and create an inbox on that domain

Deliverability and event tracking

Before sending, the API checks whether a recipient address is deliverable, and after sending it pushes delivery events to a webhook. An agent can validate a list, send only to deliverable addresses, and react to bounces or opens as the events arrive, grounding send decisions in Anjal's deliverability and event data rather than guessing.

Check whether a recipient is deliverable, send a message if it is, and register a webhook to receive the delivery events

Key Endpoints

112 endpoints — the anjal api creates email inboxes and sends and receives mail for ai agents across isolated workspaces.

METHOD

PATH

DESCRIPTION

POST

/v1/inboxes

Create an inbox

POST

/v1/inboxes/{id}/send

Send a message from an inbox

GET

/v1/inboxes/{id}/threads

List threads in an inbox

GET

/v1/messages/search

Search messages across inboxes

POST

/v1/inboxes/{id}/drafts

Create a draft

POST

/v1/domains

POST

/v1/webhooks

Create a webhook

POST

/v1/verify-email

Check recipient deliverability

POST

/v1/inboxes

Create an inbox

POST

/v1/inboxes/{id}/send

Send a message from an inbox

GET

/v1/inboxes/{id}/threads

List threads in an inbox

GET

/v1/messages/search

Search messages across inboxes

POST

/v1/inboxes/{id}/drafts

Create a draft

POST

/v1/domains

POST

/v1/webhooks

Create a webhook

POST

/v1/verify-email

Check recipient deliverability

Why Jentic?

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

Setup

Wiring the Anjal API by hand means handling its X-API-Key auth, registering and verifying sending domains, and tracking webhooks and per-tenant workspace keys yourself. Through Jentic you install once, import the API from the Directory, store the key once, and your agent calls it.

Permission scoping

Anjal carries its request targets in the body rather than the URL path, so rules bound which operations your agent may call: you can allow inbox send and read operations while leaving inbox deletion and domain management out unless you add them. You choose the operations it may use.

Credential isolation

Your Anjal 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 inbox' or 'send an email', and Jentic returns the matching Anjal operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Anjal API through Jentic.

What authentication does the Anjal API use?

The Anjal API authenticates with an API key sent in the X-API-Key header, as declared in its OpenAPI spec, and workspace keys scope access per tenant. Through Jentic the key is stored once by your own self-hosted instance and injected at call time, so it never appears in the agent's prompt or logs.

Can I send and receive email with the Anjal API?

Yes. You create an inbox, send messages, reply, forward, and draft, and read threads and attachments back. Full-text search spans inboxes, and a webhook pushes delivery events so an agent can react to replies and bounces.

Is there an Anjal API MCP server?

You do not need an MCP server to give your agent the Anjal API. Jentic connects it directly from the API Directory: import the API, store your API key once, and your agent sends and reads mail on demand without loading another server's tool definitions into its context.

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

Yes. Write a rule that allows only the inbox send and read operations for one workspace, so the agent can correspond from that workspace but cannot delete inboxes or manage domains unless you add those, and every call it makes is logged for review. Anjal carries its targets in the request body, so rules bound which operations the agent may call.

What are the rate limits for the Anjal API?

The OpenAPI spec does not specify rate limits for the Anjal API. Check the vendor documentation at https://anjal.app for current limits before sending at high volume.

How do I send an email with the Anjal API through Jentic?

Search Jentic for an intent such as 'send an email from an inbox', and it returns the matching operation with its input schema so your agent passes the recipient and body correctly. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Anjal App Anjal API

AI ReadinessFoundational (C)56/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsEmail DeliveryapiKey112 EndpointsREST

For Agents

Create email inboxes on shared or custom domains, send and receive mail, manage drafts and threads, search messages, verify sending domains, and receive delivery events over webhooks.

Use for: I need to create a new email inbox for a customer, Send an email from one of my inboxes, Search all inboxes for messages from a sender, Reply to the latest message in a thread

Not supported: Does not handle SMS, voice calls, or push notifications. Use for email inboxes, delivery, and connected LinkedIn outreach only.

The Anjal API creates email inboxes and sends and receives mail for AI agents across isolated workspaces. Inboxes live on a shared sending domain or a custom domain you register and verify, and each one can send, reply, forward, draft, thread, label, and search messages, with attachments handled through one-time upload and download links. It also isolates resources per tenant for reseller setups, pushes delivery events over webhooks, and drives LinkedIn outreach through connected sessions.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: DSignals: 4

51%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

30%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: C+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

36%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

32%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

59%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

81%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

79%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Anjal API to your agent

Capabilities

Start building with Anjal API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Anjal App Anjal API

Jentic AI Readiness Score

Anjal API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness