Install Jentic One Beta

Connect the Tuemilio API to your agent

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

Create an email

Get all emails

Update an email

Delete an email

Add points to an email

Use Cases

Patterns agents use Tuemilio API for, with concrete tasks.

GET STARTED

Start building with Tuemilio API

Explore with Jentic One

View OpenAPI Document

Automated Emails Management

Automate emails operations by combining multiple Tuemilio API endpoints. Agents can get all emails and then get an email by id in a single workflow.

Call GET /lists/{list_id}/emails to get all emails, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Tuemilio API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'create an email', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

8 endpoints — tuemilio provides a waitlist management api for managing email subscribers, waitlists, referral tracking, and points-based engagement.

METHOD

PATH

DESCRIPTION

POST

/lists/{list_id}/emails

Create an email

GET

/lists/{list_id}/emails

Get all emails

GET

/lists/{list_id}/emails/{email_id}

Get an email by ID

PUT

/lists/{list_id}/emails/{email_id}

Update an email

DELETE

/lists/{list_id}/emails/{email_id}

Delete an email

PUT

/lists/{list_id}/emails/{email_id}/add-points

Add points to an email

GET

/lists

Get all waitlists

GET

/lists/{list_id}

Get a waitlist

POST

/lists/{list_id}/emails

Create an email

GET

/lists/{list_id}/emails

Get all emails

GET

/lists/{list_id}/emails/{email_id}

Get an email by ID

PUT

/lists/{list_id}/emails/{email_id}

Update an email

DELETE

/lists/{list_id}/emails/{email_id}

Delete an email

PUT

/lists/{list_id}/emails/{email_id}/add-points

Add points to an email

GET

/lists

Get all waitlists

GET

/lists/{list_id}

Get a waitlist

Why Jentic?

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

Setup

Wiring Tuemilio API by hand means passing its api_token as a query parameter on every call, tracking list and email ids across calls, and handling errors and retries yourself. Through Jentic you install once, import Tuemilio API from the API Directory, store the API token once, and your agent calls it.

Permission scoping

Tuemilio API puts the list id in the URL path (/lists/{list_id}/emails/...), so a rule can pin your agent to one list: it can add and read that list's emails and nothing else. You choose the operations it may call, so deleting an email is not included unless you add it.

Credential isolation

Your Tuemilio API 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 'add an email to a list' or 'add points to a subscriber', and Jentic returns the matching Tuemilio API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Tuemilio API through Jentic.

What authentication does the Tuemilio API use?

The Tuemilio API uses an API key passed in the `api_token` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I create an email with the Tuemilio API?

Yes. Use the POST /lists/{list_id}/emails endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Tuemilio API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I create an email through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create an email'. Jentic returns the matching Tuemilio API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Tuemilio API have?

The Tuemilio API exposes 8 endpoints covering emails, waitlists operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Tuemilio operations and credentials the agent may use. Since Tuemilio puts the list id in the URL path (/lists/{list_id}/emails/...), you can pin the agent to a single waitlist so it only adds and reads that list's emails. You also choose the operations it may call, so deleting an email stays off unless you explicitly include it.

Tuemilio API

AI ReadinessFoundational (D+)49/100

See full scorecard

Official vendor OpenAPI document · agent-readyAnalyticsWeb AnalyticsapiKey8 EndpointsREST

For Agents

Programmatically create an email, get all emails. Covers 8 operations with apiKey authentication.

Use for: I need to an email, I want to all emails, Search for an email by id, Find all an email

Not supported: Does not handle payments, communications, or crm - use for analytics only.

Tuemilio provides a waitlist management API for managing email subscribers, waitlists, referral tracking, and points-based engagement. The API exposes 8 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 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).

50%

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.

50%

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

43%

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

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

15%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Tuemilio API to your agent

Capabilities

Use Cases

Start building with Tuemilio API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Tuemilio API

Jentic AI Readiness Score

Tuemilio 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