Install Jentic One Beta

Connect the Front Core API to your agent

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

List, search, and update conversations and set their assignee

Send message replies and create drafts within a conversation

Add internal comments and mentions to a conversation

Tag conversations and list the inboxes and channels they belong to

Manage contacts along with contact groups and contact lists

GET STARTED

Start building with Front Core API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Front Core API for, with concrete tasks.

★ Agent-Driven Conversation Triage

An AI agent connected through Jentic can triage the Front shared inbox without a developer wiring the bearer token and conversation paths. The agent lists an inbox's conversations, tags and assigns each one to the right teammate, and drafts a reply for review. Jentic injects the token at call time so the credential never reaches the agent.

List the conversations in an inbox, tag each by topic, assign it to a teammate, and draft a reply

Automated Reply Drafting

Support teams can have an agent draft responses that a human approves before sending. The agent reads a conversation's messages, creates a draft reply in the conversation, and leaves an internal comment explaining its reasoning. This keeps a human in the loop while removing the blank-page step.

Read a conversation's messages, create a draft reply, and add an internal comment summarising the suggested answer

Knowledge Base Maintenance

Teams keeping self-service content current can update articles across locales programmatically. The agent fetches an article's content, updates it in the default locale, and syncs the change into other locales. This keeps the knowledge base aligned with the latest answers.

Fetch a knowledge base article's content, update it in the default locale, then update the same article in another locale

Key Endpoints

238 endpoints — the front core api drives the front shared inbox, where teams handle customer conversations across email and other channels from one place.

METHOD

PATH

DESCRIPTION

GET

/conversations

List conversations

GET

/conversations/{conversation_id}

Get a conversation

POST

/conversations/{conversation_id}/messages

Send a message reply

POST

/conversations/{conversation_id}/comments

Add an internal comment

POST

/conversations/{conversation_id}/tags

Add a tag to a conversation

PUT

/conversations/{conversation_id}/assignee

Set a conversation's assignee

GET

/contacts

List contacts

GET

/conversations

List conversations

GET

/conversations/{conversation_id}

Get a conversation

POST

/conversations/{conversation_id}/messages

Send a message reply

POST

/conversations/{conversation_id}/comments

Add an internal comment

POST

/conversations/{conversation_id}/tags

Add a tag to a conversation

PUT

/conversations/{conversation_id}/assignee

Set a conversation's assignee

GET

/contacts

List contacts

Why Jentic?

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

Setup

Wiring Front by hand means managing a bearer token, threading conversation, inbox, and contact ids through nested paths, and handling pagination across a large surface yourself. Through Jentic you install once, import Front from the API Directory, store the token once, and your agent calls it.

Permission scoping

Front puts the inbox and conversation ids in the URL path, for example /inboxes/{inbox_id} and /conversations/{conversation_id}, so a rule can pin your agent to one inbox or conversation. You choose which operations it may call, so destructive ones like deleting a conversation or an account are not included unless you add them.

Credential isolation

Your Front bearer token 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 'reply to a conversation' or 'assign a conversation', and Jentic returns the matching Front operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Front Core API through Jentic.

What authentication does the Front Core API use?

Per its OpenAPI spec, the Front Core API uses a bearer token sent on each request. Through Jentic the token is stored encrypted by your own instance and injected at call time, so it never reaches the agent.

Is there a Front MCP server?

You don't need an MCP server to give your agent Front. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls operations like replying to a conversation or assigning it on demand, without loading another server's tool definitions into its context.

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

Yes. Front puts the inbox and conversation ids in the URL path, so a rule can pin your agent to one inbox and allow only reply, tag, and assign operations, so it cannot delete a conversation or an account unless you add those operations, and every call it makes is logged. This matches a triage bot that routes and drafts without destructive power.

Can I draft and send replies with the Front Core API?

Yes. Read a conversation's messages, then create a draft reply for a human to approve or send a message reply directly in the conversation. You can also add an internal comment that stays private to the team.

What are the rate limits for the Front Core API?

The OpenAPI spec does not specify rate limits. Check the Front developer documentation at https://dev.frontapp.com for current rate limits and tier-based ceilings before running bulk conversation jobs.

How do I triage conversations with the Front Core API through Jentic?

Search Jentic for 'triage a shared inbox', which returns the conversation list, tag, and assignee operations with their input schemas. The agent lists an inbox's conversations, tags and assigns each, and drafts a reply, with your stored token injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Frontapp Front Core API

AI ReadinessFoundational (C)54/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMCustomer Supportbearer238 EndpointsREST

For Agents

Triage and reply to customer conversations in the Front shared inbox, assign and tag them, manage contacts and inboxes, and author knowledge base content. Authenticated with a bearer token.

Use for: I need to reply to a customer conversation, Assign a conversation to a teammate, Search conversations for a keyword, Add an internal comment to a conversation

Not supported: Does not handle billing, telephony dialing, or marketing campaign sending. Use for the Front shared inbox: conversations, contacts, inboxes, and knowledge base only.

The Front Core API drives the Front shared inbox, where teams handle customer conversations across email and other channels from one place. It lists, searches, and updates conversations, assigns them, sends message replies and drafts, and adds internal comments and mentions. It also manages contacts, contact groups and lists, inboxes, channels, tags, knowledge base articles and categories, and analytics reports. Requests authenticate with a bearer token.

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

23%

Example Density

How richly the API is illustrated with examples.

95%

Example Validity

Percentage of examples that conform to their schemas.

25%

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

63%

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.

62%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: D-Signals: 1

43%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A-Signals: 1

75%

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

66%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Front Core API to your agent

Capabilities

Start building with Front Core API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Frontapp Front Core API

Jentic AI Readiness Score

Core 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