Marlie AI API

Name: Marlie AI API
Brand: Marlie AI API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsVoice Telephonybearer4 EndpointsREST

For Agents

Pull AI voice call records, fetch individual call transcripts, and retrieve call-volume analytics for a Marlie-connected business.

Install Jentic One Beta

Connect the Marlie AI API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Marlie AI 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Marlie AI API.

List all AI voice calls handled by Marlie for the connected business

Fetch the transcript and metadata for a specific call by ID

Retrieve the business profile linked to the API token

Pull aggregated analytics on call volume and outcomes

GET STARTED

Start building with Marlie AI API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Marlie AI API, keeping it validated and agent-ready. Marlie AI provides a small, focused interface to retrieve AI voice-call records and call analytics for a connected business. Customers use it to pull historical call lists, fetch a single call's transcript and metadata, look up business profile information, and read aggregated call analytics. The API is intended for businesses that have deployed Marlie's AI voice agent and want to feed call outcomes into reporting, CRMs, or downstream automations.

Use Cases

Patterns agents use Marlie AI API for, with concrete tasks.

★ CRM Call Logging

Service businesses using Marlie as their AI voice receptionist need every handled call logged into their CRM. The Marlie API exposes a list-calls endpoint plus per-call detail, so a sync job can pull new calls hourly and create matching CRM activity records with the full transcript attached.

Call `GET /calls` filtered to the last hour and create a CRM activity record for each new call_id with the transcript pulled from `GET /calls/{call_id}`.

Call Analytics Dashboard

Owners of small businesses want a daily view of how many calls Marlie answered, how many resulted in bookings, and trend lines over time. The `/analytics/calls` endpoint returns aggregated counts that a dashboard can render directly without computing rollups client-side.

Call `GET /analytics/calls` and render the daily total-calls and answered-calls counts for the past 30 days.

Missed Call Follow-up

When the AI agent flags a call as needing a human follow-up, the business owner wants a quick list of those calls each morning. The list endpoint returns enough metadata (timestamp, caller, outcome) to triage which calls a team member should return personally.

Call `GET /calls` filtered to outcomes that require follow-up and produce a morning summary email of caller numbers and reasons.

AI Agent Customer Support Briefing

A customer-support AI agent can use Jentic to fetch a caller's most recent Marlie call before responding to a follow-up email, so it has the right context. Jentic stores the bearer token and exposes Marlie's small operation set behind intent-based search, keeping integration trivial for downstream agents.

Search Jentic for 'fetch latest ai voice call', load the Marlie `/calls` schema, and execute it filtered by today to brief the support agent.

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for marlie ai api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/calls

List AI voice calls

GET

/calls/{call_id}

Fetch transcript and metadata for one call

GET

/business

Retrieve the business profile

GET

/analytics/calls

Aggregated call analytics

GET

/calls

List AI voice calls

GET

/calls/{call_id}

Fetch transcript and metadata for one call

GET

/business

Retrieve the business profile

GET

/analytics/calls

Aggregated call analytics

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Marlie AI bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped session references and the `Authorization: Bearer ...` header is set automatically — raw tokens never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'list ai voice calls' or 'get call transcript') and Jentic returns the matching Marlie operation with its input schema.

Time to first call

Direct Marlie AI integration: 2-3 hours for auth and pagination. Through Jentic: under 15 minutes — search, load schema, execute.

FAQs

Specific to using Marlie AI API through Jentic.

Why is there no official OpenAPI spec for Marlie AI API?

Marlie AI does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Marlie AI API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Marlie AI API use?

Marlie AI uses HTTP bearer-token authentication. Through Jentic, the token is stored encrypted in the MAXsystem vault and the `Authorization: Bearer ...` header is applied automatically when the agent executes a call.

Can I retrieve call transcripts with the Marlie AI API?

Yes. `GET /calls/{call_id}` returns the full transcript and metadata for a specific call. Use `GET /calls` first to list call IDs from the time window you care about.

What are the rate limits for the Marlie AI API?

Marlie AI does not publish hard rate limits in the spec. Given the small endpoint surface (4 endpoints), conservative client-side throttling at 1-2 requests per second per business token is sufficient for most CRM-sync workloads.

How do I sync new Marlie calls into a CRM through Jentic?

Run `pip install jentic`, then use Jentic's search with the query 'list ai voice calls'. Jentic loads the `/calls` operation schema and your agent executes it incrementally, then fetches each transcript via `/calls/{call_id}` for the CRM activity record.

Does the Marlie AI API expose call analytics?

Yes. `GET /analytics/calls` returns aggregated call metrics (volume and outcomes) so dashboards do not need to compute rollups client-side.