Install Jentic One Beta

Connect the Loops OpenAPI Spec to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Loops OpenAPI Spec, 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%2Floops.so%2Floops" | 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%2Floops.so%2Floops" | 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 Loops OpenAPI Spec API.

Send a transactional email to a contact

Trigger event-based email automations by sending an event

Create, find, and update contacts in the audience

Define and list custom contact properties

List transactional emails and mailing lists

GET STARTED

Start building with Loops OpenAPI Spec API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Loops OpenAPI Spec API for, with concrete tasks.

★ Send product emails from an AI agent

An AI agent integration created through Jentic needs to email users as part of a flow. The Loops API sends a transactional email to a contact and can trigger an event-based automation, so the agent delivers a receipt, reset link, or onboarding step without the product wiring an email service directly.

Send a transactional email to a contact and confirm it was accepted for delivery

Keep the audience in sync

Contacts in Loops must reflect the product's users. The Loops API creates, finds, and updates contacts and manages their custom properties, so an automation can add a new signup, enrich an existing contact, and keep attributes current for later segmentation.

Find a contact by email, create it if missing, then update its custom properties

Event-driven onboarding

Onboarding emails fire off product events rather than manual sends. The Loops API sends an event for a contact to start the matching automation, so an agent can advance a user through an onboarding sequence by emitting the right event at each step.

Send an onboarding event for a contact to start its automation

Key Endpoints

12 endpoints — the loops api sends transactional emails, triggers event-based email flows, and manages the contacts, contact properties, and mailing lists behind a product's email program.

METHOD

PATH

DESCRIPTION

POST

/contacts/create

Create a contact

PUT

/contacts/update

Update a contact

GET

/contacts/find

Find a contact

POST

/events/send

Send an event

POST

/transactional

Send a transactional email

GET

/lists

Get mailing lists

POST

/contacts/create

Create a contact

PUT

/contacts/update

Update a contact

GET

/contacts/find

Find a contact

POST

/events/send

Send an event

POST

/transactional

Send a transactional email

GET

/lists

Get mailing lists

Why Jentic?

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

Setup

Wiring Loops by hand means handling its bearer API key and shaping the contact, event, and transactional email payloads yourself. Through Jentic you install once, import Loops from the API Directory, store the key once, and your agent calls it.

Permission scoping

The contact and email details travel in the request body, so rules bound which operations your agent may call, not which contact or list. You can allow the transactional-send and contact operations while leaving contact deletion out unless you add it.

Credential isolation

Your Loops 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 contact', and Jentic returns the matching Loops operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Loops OpenAPI Spec API through Jentic.

What authentication does the Loops API use?

The Loops API authenticates with a bearer API key in the Authorization header, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt or logs.

Can I send a transactional email with the Loops API?

Yes. The transactional operation sends an email to a contact using a template, and you can also send an event to trigger an automation, so an agent can deliver receipts, reset links, and lifecycle messages.

Can I manage contacts with the Loops API?

Yes. The API creates, finds, and updates contacts and manages their custom properties, so an agent can add a signup, enrich an existing contact, and keep attributes current for segmentation.

How do I send a transactional email through Jentic?

Install Jentic One on your own infrastructure with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then import the Loops API from the API Directory and search for 'send a transactional email'. Store the API key once and your agent can send email and manage contacts. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Loops MCP server?

You don't need an MCP server to give your agent the Loops API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls it, with operations discovered on demand instead of loaded into the agent's context.

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

Yes. The contact and email details travel in the request body, so a rule bounds which operations the agent may call rather than which contact. Allow the transactional-send and contact-find operations and the agent can email and look up contacts while contact deletion stays out of reach, and every action is recorded in an audit log.

Loops So Loops OpenAPI Spec

AI ReadinessFoundational (D)44/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsEmail Deliverybearer12 EndpointsREST

For Agents

Send transactional emails, trigger event-based flows, and manage contacts, contact properties, and mailing lists through the Loops API.

Use for: Send a transactional email to a user, Trigger a welcome flow by sending an event, Create a contact in Loops, Find a contact by email

Not supported: Does not handle SMS, push notifications, or voice calls. Use for transactional and event-based email and contact management only.

The Loops API sends transactional emails, triggers event-based email flows, and manages the contacts, contact properties, and mailing lists behind a product's email program. It lets you create, find, and update contacts, define custom contact properties, send an event to start an automation, send and list transactional emails, and read dedicated sending IP addresses. Requests are authenticated with a bearer API key.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: CSignals: 4

96%

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

25%

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

13%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

52%

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

30%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

52%

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: A-Signals: 1

78%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Loops OpenAPI Spec to your agent

Capabilities

Start building with Loops OpenAPI Spec API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Loops So Loops OpenAPI Spec

Jentic AI Readiness Score

Loops OpenAPI Spec

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