Install Jentic One Beta

Connect the IndiePitcher OpenAPI Spec to your agent

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

Send a one-off transactional email to any address with a markdown or HTML body via /email/transactional

Email one or more registered contacts in the context of a mailing list, with optional delaySeconds or delayUntilDate scheduling

Broadcast an email to every contact subscribed to a mailing list via /email/list

Add a single contact or import many in one call, with name, userId, languageCode, and customProperties

GET STARTED

Start building with IndiePitcher OpenAPI Spec API

Explore with Jentic One

View OpenAPI Document

Use Cases

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

★ Agent-driven product emails through Jentic

An AI agent connected through Jentic sends the emails a small product needs: a welcome message on signup, a receipt, or a one-off notice to a single user. It calls the transactional send operation with a subject, a markdown body, and a bodyFormat of markdown, and can turn on trackEmailOpens and trackEmailLinkClicks when you want engagement data. The API key stays in your own Jentic One instance, so the agent never handles it.

Call POST /email/transactional with to 'jane@example.com', subject 'Welcome to Acme', body '**Thanks for signing up.**', and bodyFormat 'markdown', then confirm the response reports success

Signup-to-mailing-list sync

Keep IndiePitcher contacts aligned with your own user table. When someone signs up, create the contact with their email, name, and userId, and subscribe them to lists through subscribedToLists. Setting updateIfExists lets the same call refresh an existing record instead of failing, and the batch import operation moves a backlog of users in one request.

Call POST /contacts/create with email 'sam@example.com', name 'Sam Lee', userId 'u_1842', subscribedToLists ['changelog'], and updateIfExists true

Newsletter and changelog broadcasts

Send a release note or newsletter to every contact on a mailing list with one call to the list send operation, passing the list name, subject, body, and bodyFormat. Use delayUntilDate to schedule the send for a specific time rather than sending it immediately.

Call GET /lists to confirm the 'changelog' list exists, then POST /email/list with list 'changelog', subject 'What shipped in March', a markdown body, and bodyFormat 'markdown'

Self-serve subscription management

Give each contact a hosted page to manage their own mailing list subscriptions instead of building preference screens yourself. The portal session operation takes the contactEmail and a returnURL and returns a URL you can link from your settings page or an email footer.

Call POST /lists/portal_session with contactEmail 'sam@example.com' and returnURL 'https://acme.example/settings', then return the generated portal URL to the user

Key Endpoints

11 endpoints — the indiepitcher api sends transactional emails and mailing-list campaigns, and keeps the contact records behind them in sync with your product.

METHOD

PATH

DESCRIPTION

POST

/email/transactional

Send an email to a specified address

POST

/email/list

Send an email to contacts in a mailing list

POST

/email/contact

Send an email to one or more registered contacts

POST

/contacts/create

Add a new contact

POST

/contacts/create_many

Add multiple contacts in one call

GET

/contacts/find

Find a contact by email

PATCH

/contacts/update

Update an existing contact

POST

/lists/portal_session

Create a subscription portal session URL

POST

/email/transactional

Send an email to a specified address

POST

/email/list

Send an email to contacts in a mailing list

POST

/email/contact

Send an email to one or more registered contacts

POST

/contacts/create

Add a new contact

POST

/contacts/create_many

Add multiple contacts in one call

GET

/contacts/find

Find a contact by email

PATCH

/contacts/update

Update an existing contact

POST

/lists/portal_session

Create a subscription portal session URL

Why Jentic?

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

Setup

Wiring IndiePitcher by hand means managing a project-scoped bearer key, staying under its 10 requests per second limit, and shaping markdown or HTML send payloads yourself. Through Jentic you install once, import IndiePitcher from the API Directory, store the key once, and your agent calls it.

Permission scoping

IndiePitcher identifies contacts and lists by email and list name inside the request body or query string, not the URL path, so rules bound which operations your agent may call, not which contact or list. You choose the operations it may call, so ones like contact deletion or list-wide sends are not included unless you add them.

Credential isolation

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

FAQs

Specific to using IndiePitcher OpenAPI Spec API through Jentic.

Is there an IndiePitcher MCP server?

You don't need an MCP server to give your agent IndiePitcher. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it. The agent discovers the IndiePitcher operations it needs on demand, so no extra server's tool definitions sit in its context.

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

Yes. For a welcome-email agent, write a rule that allows only POST /email/transactional and GET /contacts/find. The agent can look up a contact and send it a message, but it cannot remove contacts, import batches, or broadcast to a whole mailing list, and every call it makes is logged.

What authentication does the IndiePitcher API use?

Per its OpenAPI spec, the IndiePitcher API uses HTTP bearer authentication: send your project API key in the `Authorization` header as `Bearer <key>`. API keys are tied to a single IndiePitcher project. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected when the call runs.

Can I schedule an email for later with the IndiePitcher API?

Yes, for contact and mailing-list sends. POST /email/contact and POST /email/list accept delaySeconds to postpone the send or delayUntilDate to send at a specific time. The transactional send operation does not take these scheduling fields in the spec.

What are the rate limits for the IndiePitcher API?

The IndiePitcher OpenAPI spec states a limit of 10 requests per second across all API keys tied to a project, after which the API returns 429 Too Many Requests and the limit resets after one second. The spec recommends batch operations such as POST /contacts/create_many to reduce request volume.

How do I send a mailing-list email with the IndiePitcher API through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import IndiePitcher from the API Directory, and store your API key. Your agent searches for 'send an email to a mailing list', gets POST /email/list with its input schema, and calls it with list, subject, body, and bodyFormat. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Does the IndiePitcher API support HTML emails?

Yes. Every send operation requires a bodyFormat field set to markdown or html, so you can write the body in markdown and let IndiePitcher render it, or pass your own HTML.

IndiePitcher OpenAPI Spec

AI ReadinessFoundational (C-)52/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsEmail Deliverybearer11 EndpointsREST

For Agents

Send transactional or mailing-list emails in markdown or HTML, and add, find, update, or remove IndiePitcher contacts and their list subscriptions.

Use for: I need to send a password reset email to a user, Send a product update to everyone on the newsletter list, Find the contact record for jane@example.com, Add a new signup to IndiePitcher with their user id

Not supported: Does not handle SMS, inbound email parsing, domain DNS setup, or visual campaign design. Use for sending emails and managing IndiePitcher contacts and mailing list subscriptions only.

The IndiePitcher API sends transactional emails and mailing-list campaigns, and keeps the contact records behind them in sync with your product. It adds, finds, updates, and removes contacts by email address, accepts batch contact imports in a single call, and lets you attach custom properties and list subscriptions to each contact. Email bodies can be written in markdown or HTML, with optional open and link-click tracking, and a portal session endpoint gives each contact a hosted page to manage their own list subscriptions.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

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

42%

Example Density

How richly the API is illustrated with examples.

84%

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

56%

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.

50%

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

66%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the IndiePitcher OpenAPI Spec to your agent

Capabilities

Start building with IndiePitcher OpenAPI Spec API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

IndiePitcher OpenAPI Spec

Jentic AI Readiness Score

IndiePitcher 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