Install Jentic One Beta

Connect the Faivelo API to your agent

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

Send transactional email via POST /emails and send mail from a specific mailbox via POST /mailboxes/{address}/send

Create mailboxes on your domains via POST /mailboxes and reset their passwords

List, read, search, flag, move, and mark messages as spam within a mailbox via /mailboxes/{address}/messages and its actions

Manage mail domains and their DNS records via /domains and /domains/{domain}/dns/records

GET STARTED

Start building with Faivelo API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Faivelo API for, with concrete tasks.

★ AI agent with its own mailbox

An AI agent provisions a mailbox on your domain, sends from it, and polls the inbox to read what comes back, for example a verification code during a sign-up it is driving. Through Jentic it creates the mailbox, sends mail, and searches messages without a person wiring SMTP or IMAP. Jentic injects the Faivelo key at call time, so the agent never holds the raw secret.

Search Jentic for 'create a mailbox and send mail', create one with POST /mailboxes, send from it with POST /mailboxes/{address}/send, then poll GET /mailboxes/{address}/messages for the reply

Transactional email sending

Applications need to send receipts, password resets, and notifications and know they left the building. Faivelo sends transactional email through POST /emails and lets a caller fetch a sent email's record by id, so a workflow can send and then confirm. It sends from mail domains you control rather than a shared pool.

Call POST /emails with the recipient, subject, and body, then read GET /emails/{id} to confirm the send was recorded

Domain and mailbox provisioning

Standing up email for a new domain means adding the domain, publishing the right DNS records, and creating mailboxes on it. Faivelo exposes the domain, DNS record, and mailbox operations to script that whole setup, so an onboarding flow can take a bare domain to a working mailbox. Aliases can then forward addresses to the right mailbox.

Add DNS with POST /domains/{domain}/dns/records, create the mailbox with POST /mailboxes, then create an alias with POST /aliases to forward a public address to it

Inbox search and triage

A support or automation workflow needs to find specific messages and act on them. Faivelo searches a mailbox, lists folders and messages, and lets a caller flag, move, or mark messages as spam, so an agent can triage an inbox programmatically. Attachments can be downloaded for processing downstream.

Call GET /mailboxes/{address}/search to find the message, then POST /mailboxes/{address}/messages/{uid}/move to file it in the right folder

Key Endpoints

54 endpoints — the faivelo api runs a full email service over rest: it manages mail domains and their dns records, creates mailboxes and aliases, and sends, reads, searches, and organises mail.

METHOD

PATH

DESCRIPTION

POST

/emails

Send a transactional email

POST

/mailboxes

Create a mailbox

POST

/mailboxes/{address}/send

Send mail from a mailbox

GET

/mailboxes/{address}/messages

List messages in a mailbox

GET

/mailboxes/{address}/search

Search messages in a mailbox

POST

/domains/{domain}/dns/records

Create a DNS record

POST

/aliases

Create an alias

GET

/domains

List domains

POST

/emails

Send a transactional email

POST

/mailboxes

Create a mailbox

POST

/mailboxes/{address}/send

Send mail from a mailbox

GET

/mailboxes/{address}/messages

List messages in a mailbox

GET

/mailboxes/{address}/search

Search messages in a mailbox

POST

/domains/{domain}/dns/records

Create a DNS record

POST

/aliases

Create an alias

GET

/domains

List domains

Why Jentic?

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

Setup

Wiring the Faivelo API by hand means managing its bearer key and per-key scopes, publishing DNS for each mail domain, and building the send-then-poll inbox loop yourself. Through Jentic you install once, import Faivelo from the API Directory, store the key once, and your agent calls it.

Permission scoping

Faivelo puts the mailbox address and domain in the URL path, such as /mailboxes/{address} and /domains/{domain}, so a rule can pin your agent to the mailbox and domain operations it needs. You choose the operations it may call, so destructive ones like deleting a mailbox or a DNS record are not included unless you add them.

Credential isolation

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

FAQs

Specific to using Faivelo API through Jentic.

What authentication does the Faivelo API use?

The Faivelo API authenticates with a bearer API key, per its OpenAPI spec, and each key carries scopes that decide which operations it may perform. When you call it 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 prompt, logs, or context.

Can I send email from my own domain with the Faivelo API?

Yes. Send transactional email with POST /emails, or send from a specific mailbox with POST /mailboxes/{address}/send, both from mail domains you control rather than a shared pool. You can then fetch a sent email's record with GET /emails/{id} to confirm it went out.

Can the Faivelo API read and search a mailbox?

Yes. List messages with GET /mailboxes/{address}/messages, search with GET /mailboxes/{address}/search, read one with GET /mailboxes/{address}/messages/{uid}, and act on it with flag, move, and spam operations. Attachments come down through GET /mailboxes/{address}/messages/{uid}/attachment.

What are the rate limits for the Faivelo API?

The OpenAPI spec does not pin rate limits in a machine-readable field. Check the Faivelo documentation for current per-key request and send limits, and have your agent back off when the API signals that it is being throttled.

How do I give an agent its own mailbox through Jentic?

Search Jentic for 'create a mailbox and send mail' to load the Faivelo operations with their input schemas, create a mailbox with POST /mailboxes, send with POST /mailboxes/{address}/send, and poll GET /mailboxes/{address}/messages for replies. 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 Faivelo API?

Yes. Faivelo puts the mailbox address and domain in the URL path, such as /mailboxes/{address} and /domains/{domain}, so a rule can pin your agent to the mailbox and sending operations it needs. Destructive operations, such as deleting a mailbox or a DNS record, stay out unless you add them, and every call the agent makes is logged.

Faivelo API

AI ReadinessAI-Aware (B-)62/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsEmail Deliverybearer54 EndpointsREST

For Agents

Run a full email service through Faivelo: send transactional mail, create mailboxes and aliases on your domains, manage DNS records, and list, read, search, flag, and move messages in a mailbox.

Use for: Send a transactional email from my domain, Create a new mailbox on my domain, Search a mailbox for a verification code, List the messages in an inbox

Not supported: Does not handle SMS, voice, push notifications, or chat. Use for email: hosting mailboxes and domains, sending transactional mail, and reading and organising messages only.

The Faivelo API runs a full email service over REST: it manages mail domains and their DNS records, creates mailboxes and aliases, and sends, reads, searches, and organises mail. Transactional email goes out through a send endpoint, while per-mailbox operations list folders and messages, flag or move them, mark spam, and download attachments. Partner endpoints let approved resellers provision and manage customer accounts under their own brand, and a Drive surface lists files with download URLs. Authentication uses a bearer API key, scoped per key to the operations it may perform.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: DSignals: 4

79%

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

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

16%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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

59%

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.

55%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

93%

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: ASignals: 1

82%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Faivelo API to your agent

Capabilities

Start building with Faivelo API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Faivelo API

Jentic AI Readiness Score

Faivelo 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