Install Jentic One Beta

Connect the MailRambo Verification API to your agent

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

Get a strict yes/no deliverable answer with a reason for one address through GET or POST /v1/verify

Run a free sub-second check for sign-up forms with mode=fast, covering syntax, typos, MX, disposable, and role addresses

Request the full detail block with detail=full to see a grade, score, inbox_provider, flags such as catch_all and mailbox_exists, and DNS records like SPF and DMARC

Start a batch verification of a named email list of up to 200 addresses with POST /v1/verify/batch, using an Idempotency-Key header so retries do not charge twice

GET STARTED

Start building with MailRambo Verification API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MailRambo Verification API for, with concrete tasks.

★ Agent-run deliverability checks through Jentic

An agent that adds contacts to a mailing tool first asks MailRambo whether each address is deliverable and keeps only the ones that come back true, logging the reason for the rest. Through Jentic the agent finds the verify operation by intent, the mr_live_ key stays in the developer's own Jentic One instance, and a rule can hold the agent to verification and account reads.

Call GET /v1/verify with email 'jane@example.com' and add the contact only if deliverable is true, otherwise record the reason

Batch list verification

To clean a whole list, POST /v1/verify/batch with the emails array and an optional name starts a job charged at one credit per address up front, and sending an Idempotency-Key makes a retried request replay the first response rather than charge again. GET /v1/verify/batch/{batch_id} then reports status and progress and returns one yes/no result per address when the job completes.

POST /v1/verify/batch with emails from the leads list and name 'November leads' and an Idempotency-Key header, then poll GET /v1/verify/batch/{batch_id} until the results appear

Free sign-up form checks with mode=fast

Sign-up forms need a quick answer. Calling the verify endpoint with mode=fast runs a free sub-second check for syntax, typos, MX, disposable, and role addresses, so the form can reject throwaway or mistyped addresses and offer the suggestion field, then run a full check later when a mailbox answer matters.

Call GET /v1/verify with email 'user@gmial.com' and mode 'fast', then show the suggestion value to the user if one is returned

Key Endpoints

5 endpoints — the mailrambo verification api answers a strict yes or no on whether an email address is deliverable, setting deliverable to true only for confirmed mailboxes and explaining every answer in a reason field.

METHOD

PATH

DESCRIPTION

GET

/v1/verify

Verify one email address

POST

/v1/verify

Verify one email address with a JSON body

POST

/v1/verify/batch

Start a batch verification

GET

/v1/verify/batch/{batch_id}

Poll a batch for results

GET

/v1/account

Read plan and remaining credits

GET

/v1/verify

Verify one email address

POST

/v1/verify

Verify one email address with a JSON body

POST

/v1/verify/batch

Start a batch verification

GET

/v1/verify/batch/{batch_id}

Poll a batch for results

GET

/v1/account

Read plan and remaining credits

Why Jentic?

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

Setup

Wiring MailRambo by hand means passing its bearer key, choosing between mr_live_ and mr_test_ keys, and handling batch polling and idempotent retries yourself. Through Jentic you install once, import MailRambo from the API Directory, store the key once, and your agent calls it.

Permission scoping

MailRambo puts the batch_id in the URL path when polling, so a rule can pin your agent to one batch's results, while single verifications carry the address in the query or body and are bounded by operation. You choose the operations it may call, so credit-spending batch creation is not included unless you add it.

Credential isolation

Your MailRambo 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 'check if an email is deliverable' or 'verify a list of emails', and Jentic returns the matching MailRambo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using MailRambo Verification API through Jentic.

Is there a MailRambo MCP server?

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

What authentication does the MailRambo Verification API use?

Per its OpenAPI spec, the MailRambo Verification API uses bearer authentication: send your API key in the Authorization header. Keys come in two forms, mr_live_ for real verifications and mr_test_ for integrating without spending credits. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.

Can I limit what my agent is allowed to do with MailRambo?

Yes. For example, write a rule that allows GET /v1/verify and GET /v1/account but not POST /v1/verify/batch, so the agent can check single addresses and read the balance without starting credit-spending batch jobs. Every call it makes is logged on your own machine.

How much does a MailRambo verification cost?

Per the spec, a full verification costs one credit per address. It is free when the address is syntactically invalid, when it repeats a check from the last 24 hours, or when you use mode=fast. Batch jobs charge one credit per address up front, and reading GET /v1/account is free.

How do I verify a list of emails through Jentic?

Install Jentic One, import the MailRambo Verification API from the directory, and search for 'verify a batch of email addresses'. Jentic returns the batch create operation with its input schema; your agent sends the emails array, stores the returned batch_id, and polls the batch status operation until results appear. To run it on your own infrastructure, install Jentic One from its GitHub repo.

What are the rate limits for the MailRambo Verification API?

The OpenAPI spec does not specify rate limits. Check the MailRambo documentation at https://www.mailrambo.com for current limits.

MailRambo Verification API

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentContact Enrichmentbearer5 EndpointsREST

For Agents

Check whether an email address is deliverable with a yes/no answer and reason, run batch verifications and poll their results, and read the remaining credit balance.

Use for: Check whether jane@example.com is a real mailbox, Run a fast free check on an email typed into a sign-up form, Verify a list of 200 leads in one batch, Get the status of my MailRambo batch job

Not supported: Does not handle sending email, inbox placement testing, or contact enrichment with phone or company data. Use for verifying email address deliverability only.

The MailRambo Verification API answers a strict yes or no on whether an email address is deliverable, setting deliverable to true only for confirmed mailboxes and explaining every answer in a reason field. Single addresses are checked over GET or POST on the verify endpoint, either in full mode with a mailbox check or in a free fast mode for forms that covers syntax, typos, MX, disposable, and role checks. Larger lists go through batch jobs that you start and then poll by batch_id, and an account endpoint reports the plan and remaining credits.

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.

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

23%

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.

50%

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

57%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the MailRambo Verification API to your agent

Capabilities

Start building with MailRambo Verification API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

MailRambo Verification API

Jentic AI Readiness Score

MailRambo Verification 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