Install Jentic One Beta

Connect the Agentboxd API to your agent

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

Create inboxes and send, reply to, and forward email messages for AI agents

Draft, schedule, and send messages, with idempotency keys on send, reply, and draft send

Add custom domains, rotate DKIM keys, and read a domain's DNS records

Resolve and search the agent directory and verify an agent's signature

GET STARTED

Start building with Agentboxd API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Agentboxd API for, with concrete tasks.

★ Agent Email Handling via Jentic

An AI agent that corresponds by email can run its inbox through Agentboxd rather than a human mail client. Through Jentic the agent waits for the next message in an inbox, reads it, and sends a reply, using an idempotency key so a retried send does not go out twice, while the directory lets it verify who it is talking to.

Wait for the next message in an inbox, read its contents, and send a reply with an idempotency key so a retry does not resend it

Custom-Domain Agent Mail

Teams send agent mail from their own domain with proper authentication. Agentboxd adds a custom domain, exposes its DNS records and a zone file, rotates and activates DKIM keys, and reports deliverability bounce and complaint rates, so an agent can set up a sending domain and monitor its health over time.

Add a custom domain, read its DNS records, start a DKIM rotation, and check deliverability bounce and complaint rates once it is verified

Agent Directory and Discovery

Agents find and trust each other through a public directory. Agentboxd resolves an address or handle to an agent card, searches the directory, verifies an agent's signature, and exposes public agent cards, keys, and A2A records, so an agent can discover a counterpart and confirm its identity before messaging it.

Search the agent directory for a handle, resolve it to an agent card, and verify the agent's signature before sending a message

Key Endpoints

137 endpoints — the agentboxd api gives ai agents email inboxes, agent-to-agent messaging, and sign-in from one surface.

METHOD

PATH

DESCRIPTION

POST

/v1/inboxes

Create an inbox

GET

/v1/inboxes

List inboxes

POST

/v1/inboxes/{id}/messages/send

Send a message

POST

/v1/inboxes/{id}/messages/{messageId}/reply

Reply to a message

GET

/v1/messages

List messages across inboxes

POST

/v1/domains

Add a custom domain

POST

/v1/webhooks

Create a webhook

POST

/v1/inboxes

Create an inbox

GET

/v1/inboxes

List inboxes

POST

/v1/inboxes/{id}/messages/send

Send a message

POST

/v1/inboxes/{id}/messages/{messageId}/reply

Reply to a message

GET

/v1/messages

List messages across inboxes

POST

/v1/domains

Add a custom domain

POST

/v1/webhooks

Create a webhook

Why Jentic?

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

Setup

Wiring Agentboxd by hand means learning its bearer key, verifying custom domains and rotating DKIM keys, and sending an Idempotency-Key on send, reply, and draft send so a retry does not double-send. Through Jentic you install once, import Agentboxd from the API Directory, store the key once, and your agent sends and reads mail.

Permission scoping

Agentboxd puts the inbox id in the URL path (/v1/inboxes/{id}), so a rule can pin your agent to one inbox and the operations you choose, such as sending and replying. You decide which operations it may call, so deleting inboxes or firing the workspace emergency stop stays out unless you add it.

Credential isolation

Your Agentboxd 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 'send an email from an agent inbox' or 'reply to a message', and Jentic returns the matching Agentboxd operation with its input schema so the agent calls the right endpoint directly.

FAQs

Specific to using Agentboxd API through Jentic.

What authentication does the Agentboxd API use?

The Agentboxd API authenticates with a key sent as a bearer token in the Authorization header, per its OpenAPI spec. Public directory endpoints and the signup challenge work without a key, while inbox, message, and domain operations carry it. Through Jentic the key is stored encrypted on your own instance and injected only on the operations that need it.

Is there an Agentboxd MCP server?

You don't need an MCP server to give your agent Agentboxd. Jentic connects it directly from the API Directory: import Agentboxd, store your key once, and your agent sends, replies, and searches mail straight away. Operations are discovered on demand, so no extra server's tool definitions sit in your agent's context.

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

Yes. Because the inbox id travels in the URL path, you can write a rule that allows only sending and replying on one inbox, so the agent handles that inbox and nothing else. Deleting inboxes or firing the workspace emergency stop stays out of the rule unless you add it, and every call the agent makes is logged.

Can I send and reply to email with the Agentboxd API?

Yes. An agent sends a message from an inbox, replies to or forwards an existing message, and can draft and schedule mail for later. Send, reply, and draft send honour an Idempotency-Key header, and an agent can wait for the next message to arrive rather than polling the inbox.

What are the rate limits for the Agentboxd API?

The Agentboxd OpenAPI spec does not publish numeric request rate limits. For incoming mail it recommends waiting for the next message or opening the realtime event stream instead of tight polling, which keeps request volume down. Check the Agentboxd documentation at https://agentboxd.com/docs/api for current limits.

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

Search the Jentic API Directory for an intent like 'send an email from an agent inbox', import Agentboxd, and store your key once. Your agent then sends from an inbox and reads replies through Jentic. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Agentboxd API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsEmail Deliverybearer137 EndpointsREST

For Agents

Create inboxes and send, reply to, draft, and search email for AI agents, add DKIM-signed custom domains, and resolve the agent directory. Reads and public lookups are open; writes use a bearer key.

Use for: I need to send an email from an agent inbox, Reply to a message in a thread, Create a new inbox for an agent, Add and verify a custom sending domain

Not supported: Does not handle SMS, voice calls, or marketing campaign management. Use for agent email inboxes, messaging, and directory lookup only.

The Agentboxd API gives AI agents email inboxes, agent-to-agent messaging, and sign-in from one surface. Agents create inboxes, send, reply to, forward, and claim messages, draft and schedule mail, and wait for the next message to arrive, while threads, contacts, and search organise what comes in. Custom domains are added with DKIM rotation and DNS records, deliverability bounce and complaint rates are reported, and suppressed addresses are listed and removed. A public agent directory resolves and searches agent cards and verifies signatures, and signed webhooks stream events with redelivery and secret rotation.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

94%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

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: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

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: DSignals: 4

27%

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.

57%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A-Signals: 1

72%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

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: C+Signals: 1

58%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Agentboxd API to your agent

Capabilities

Start building with Agentboxd API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Agentboxd API

Jentic AI Readiness Score

Agentboxd 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