Install Jentic One Beta

Connect the autoMessage REST API to your agent

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

Queue an outbound iMessage to a contact and track its delivery status

List conversations and retrieve individual messages by their guid

Draft a message, update it before it sends, and cancel it while still queued

Create and update the contacts the connector is allowed to message

Check connector liveness and the health of the macOS bridge

GET STARTED

Start building with autoMessage REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use autoMessage REST API for, with concrete tasks.

★ AI Agent iMessage Outreach

An AI agent reaches customers over iMessage without a developer wiring the connector by hand. Through Jentic the agent imports the autoMessage API, queues an outbound message to a contact, and reads back the delivery status the macOS connector reports, all while the Apple ID and key stay on the developer's own machine.

Queue an outbound iMessage to the contact +15551234567 saying 'Your order shipped', then poll the message by its guid until the delivery status is confirmed

Delivery Tracking

Teams that message customers over iMessage need to know which messages actually landed. autoMessage returns each queued message with a guid and a status the connector updates as Apple reports back, so a workflow can list recent messages and flag any that failed to deliver.

List messages from the last day and return the guid of any whose delivery status is not confirmed

Draft Review Before Send

Some outbound messages should be reviewed before they leave the device. autoMessage lets an agent create a draft, update its text, and cancel it while it is still queued, so a human or a second check can approve the wording before the connector sends it.

Create a draft to a contact, update its body after review, and cancel it if the reviewer rejects the wording

Key Endpoints

15 endpoints — the automessage api sends and receives imessages over standard https, relaying each message through a customer's own macos connector and apple id.

METHOD

PATH

DESCRIPTION

POST

/messages

Queue an outbound iMessage

GET

/messages

List messages

GET

/messages/{guid}

Retrieve a single message

GET

/conversations

List conversations

POST

/drafts

Create a draft

PATCH

/drafts/{id}

Update a draft before it sends

GET

/contacts

List contacts

GET

/status

Report connector liveness

POST

/messages

Queue an outbound iMessage

GET

/messages

List messages

GET

/messages/{guid}

Retrieve a single message

GET

/conversations

List conversations

POST

/drafts

Create a draft

PATCH

/drafts/{id}

Update a draft before it sends

GET

/contacts

List contacts

GET

/status

Report connector liveness

Why Jentic?

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

Setup

Wiring autoMessage by hand means provisioning its API key, pairing a macOS connector to an Apple ID, and handling message status polling yourself. Through Jentic you install once, import autoMessage from the API Directory, store the key once, and your agent calls it.

Permission scoping

A single account key reaches every autoMessage operation, so a rule bounds the agent to the operations it needs, such as queuing and reading messages. You choose which operations it may call, so destructive ones like contact deletion are not included unless you add them.

Credential isolation

Your autoMessage 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 an iMessage' or 'check delivery status', and Jentic returns the matching autoMessage operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using autoMessage REST API through Jentic.

Is there an autoMessage MCP server?

You don't need an MCP server to give your agent the autoMessage API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Because operations are discovered on demand, you avoid loading another server's tool definitions into the agent's context.

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

Yes. Write a rule that allows only the message-send and draft operations, so the agent can queue and review iMessages but cannot delete contacts, and every call it makes is logged for you to review.

What authentication does the autoMessage REST API use?

The autoMessage REST API authenticates with an API key sent in the `X-API-KEY` header, as declared in its OpenAPI spec. Through Jentic that 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 an iMessage and confirm it was delivered with the autoMessage API?

Yes. Queue the message with a post to the messages collection, then poll the message by its guid to read the delivery status the connector reports back as Apple confirms it.

How do I send an iMessage through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then import the autoMessage API from the Jentic API Directory and store your key. Your agent searches for 'send an iMessage' and Jentic returns the queue-message operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo.

What are the rate limits for the autoMessage API?

The autoMessage OpenAPI spec does not define rate limits. Because every message is relayed through your own Apple device, throughput is bounded by that device rather than a published API quota, so plan high-volume sends accordingly.

Automessage App autoMessage REST API

AI ReadinessFoundational (D+)48/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsChat MessagingapiKey15 EndpointsREST

For Agents

Send and track iMessages from a connected Apple device: queue outbound messages, read conversations, edit drafts before they send, and update the contacts the connector can reach.

Use for: Send an iMessage to a customer from my Apple device, I want to track whether an iMessage was delivered, List the most recent conversations, Retrieve a single message by its guid

Not supported: Does not handle SMS gateways, email, or push notifications. Use for sending and tracking iMessages through your own connected Apple device only.

The autoMessage API sends and receives iMessages over standard HTTPS, relaying each message through a customer's own macOS connector and Apple ID. It queues outbound messages, exposes conversations and individual messages by their guid, and keeps editable drafts that can be updated or cancelled before they send. A contacts collection and a status endpoint let an agent confirm who it can reach and whether the connector is online.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

89%

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

100%

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.

37%

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

35%

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.

62%

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

50%

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

70%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the autoMessage REST API to your agent

Capabilities

Start building with autoMessage REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Automessage App autoMessage REST API

Jentic AI Readiness Score

autoMessage REST 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