Install Jentic One Beta

Connect the Mailfornet API to your agent

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

Create a disposable inbox on an available domain with a username and ttlMinutes lifetime

Wait up to 60 seconds for a verification code or confirmation link and get just that back

List inbox messages filtered by from, subject, and since, holding open with wait instead of polling

Read one message by id and delete an inbox with all its mail

GET STARTED

Start building with Mailfornet API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Mailfornet API for, with concrete tasks.

★ AI agent completing email verification through Jentic

A browser-testing agent signs up for an app and must enter the code that gets emailed. Through Jentic it searches for 'create a test inbox', loads the Mailfornet create operation to get an address, submits it in the sign-up form, then calls the wait-for-code operation with wait set to 60 so the request returns as soon as the code arrives. The API key is injected at call time.

Call POST /inboxes with ttlMinutes 30, use the returned address in the sign-up form, then GET /inboxes/{address}/code with wait 60 and subject 'Verify'

End-to-end sign-up tests in CI

A CI suite needs a fresh address on every run so sign-up tests never collide. Mailfornet creates an inbox per test, the wait parameter holds the request until mail arrives so there is no polling loop, and deleting the inbox removes it with its mail when the test finishes. An Idempotency-Key header lets a retried create return the original inbox.

Call POST /inboxes with an Idempotency-Key per test run, read mail with GET /inboxes/{address}/messages using wait 30, then DELETE /inboxes/{address}

Password-reset and notification checks

QA wants to confirm that a password reset, invite, or receipt email is actually sent with the right subject. Mailfornet lists messages filtered by from and subject text and since a timestamp, and returns the full message by id for content checks. A registered webhook can instead push each new message to your test harness.

Call GET /inboxes/{address}/messages with subject 'Reset your password' and wait 30, then GET /messages/{id} to check the reset link

Key Endpoints

12 endpoints — the mailfornet api creates disposable email inboxes from code and reads the mail that arrives in them, built for automated tests that sign up, wait for a verification code, and type it back in.

METHOD

PATH

DESCRIPTION

POST

/inboxes

Create an inbox

GET

/inboxes/{address}/code

Wait for a verification code or link

GET

/inboxes/{address}/messages

List messages

GET

/messages/{id}

Read one message

DELETE

/inboxes/{address}

Delete an inbox and its mail

POST

/webhooks

GET

/domains

List usable domains

POST

/inboxes

Create an inbox

GET

/inboxes/{address}/code

Wait for a verification code or link

GET

/inboxes/{address}/messages

List messages

GET

/messages/{id}

Read one message

DELETE

/inboxes/{address}

Delete an inbox and its mail

POST

/webhooks

GET

/domains

List usable domains

Why Jentic?

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

Setup

Wiring Mailfornet by hand means a bearer key, picking a domain from the account's list, and handling long-held wait requests. Through Jentic you install once, import Mailfornet from the API Directory, store the key once, and your agent calls it.

Permission scoping

Mailfornet puts the inbox address in the URL path (/inboxes/{address}/code), so a rule can pin your agent to one inbox and the operations you pick. You choose the operations it may call, so destructive ones like deleting an inbox or removing a webhook are not included unless you add them.

Credential isolation

Your Mailfornet 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 'get an email verification code' or 'create a test inbox', and Jentic returns the matching Mailfornet operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Mailfornet API through Jentic.

What authentication does the Mailfornet API use?

The Mailfornet API authenticates with an API key sent as an HTTP bearer token in the Authorization header, per its OpenAPI spec, and the spec applies it to all twelve operations. You create the key on your Mailfornet account page. Through Jentic the key is stored by your own instance and attached at call time.

How does Mailfornet return a verification code without polling?

GET /inboxes/{address}/code holds the request open for up to the wait value, at most 60 seconds, until a message carrying a verification code or confirmation link arrives, then returns just that. It skips mail with neither and answers 404 code_not_found if nothing arrives in time.

What are the rate limits for the Mailfornet API?

The OpenAPI spec does not specify rate limits. GET /usage reports this month's usage for your key; check https://mailfornet.com for plan limits.

Is there a Mailfornet MCP server?

You don't need an MCP server to give your agent Mailfornet. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the inbox and code operations on demand without loading another server's tool definitions into its context.

How do I create a test inbox through Jentic?

Search Jentic for 'create a disposable inbox', load the POST /inboxes operation, and run it with an optional username, a domain from GET /domains, and ttlMinutes. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. For example, a rule that allows POST /inboxes and GET /inboxes/{address}/code lets a test agent make an inbox and read its code while it cannot delete inboxes or register and remove webhooks. Jentic logs each call the agent makes.

Mailfornet API

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsTesting Qahttp (bearer)12 EndpointsREST

For Agents

Create disposable test inboxes with Mailfornet and wait for verification codes or confirmation links to arrive, so a sign-up test or agent can complete email verification from code.

Use for: I need a throwaway inbox to sign up for a test account, Get the verification code sent to my test inbox, Check whether the password reset email arrived, List all messages from the sign-up sender in this inbox

Not supported: Does not send outbound email, host permanent mailboxes, or verify that third-party addresses exist. Use for disposable test inboxes and reading verification mail only.

The Mailfornet API creates disposable email inboxes from code and reads the mail that arrives in them, built for automated tests that sign up, wait for a verification code, and type it back in. An inbox takes an optional username, one of your available domains, and a ttlMinutes lifetime of up to 1440 minutes. A wait-for-code call holds the connection open for up to 60 seconds until a message carrying a verification code or confirmation link arrives and returns just that, skipping welcome mails and newsletters. Messages can also be listed with sender and subject filters, read individually, or pushed to a registered webhook.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

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

75%

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.

42%

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

30%

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.

54%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

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

68%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Mailfornet API to your agent

Capabilities

Start building with Mailfornet API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Mailfornet API

Jentic AI Readiness Score

Mailfornet 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