Install Jentic One Beta

Connect the LaunchList API to your agent

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

Add and update contacts through the same submit pipeline that dedupes and credits referrals

Track a contact's referrals and live leaderboard position

Mint, redeem, and revoke invitations that grant waitlist access

Draft, test, schedule, and send email broadcasts to segments of contacts

Build segments from filters and tag contacts for targeting

GET STARTED

Start building with LaunchList API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use LaunchList API for, with concrete tasks.

★ Agent-run waitlist signup and referral

An AI agent handling a new signup can call the LaunchList API through Jentic to add the contact, which triggers dedupe and referral credit automatically, then read back the contact's leaderboard position to show their standing. Jentic returns the create-contact operation from a natural-language query, so the agent runs the waitlist loop without reading the LaunchList reference first.

Create the contact from the signup details, then retrieve the contact's leaderboard position and return their current standing and referral count.

Launch-day email broadcast

Draft a broadcast, send a test to the team, and then schedule or send it to a segment of waitlist contacts when a product launches. LaunchList keeps the broadcast lifecycle, prepare, send, pause, and resume, as separate operations so a workflow can stage the send safely before it goes out.

Create a broadcast draft, send a test to the team, then send the broadcast to the chosen segment and confirm it moved to the sent state.

Invitation-gated early access

Mint invitation codes for early access, let contacts redeem them, and revoke codes that should no longer work. Combined with segments, a growth team can open access in controlled waves rather than all at once.

Mint an invitation for the contact, return the code, and confirm the invitation appears in the invitations list as active.

Key Endpoints

53 endpoints — the launchlist api runs waitlist signups, referral programs, and email broadcasts for a product launch.

METHOD

PATH

DESCRIPTION

GET

/contacts

List contacts

POST

/contacts

Create a contact

GET

/contacts/{contact}

Retrieve a contact

GET

/contacts/{contact}/position

Retrieve a contact's leaderboard standing

POST

/invitations

Mint an invitation

GET

/broadcasts

List broadcasts

POST

/broadcasts/{broadcast}/send

Send or schedule a broadcast

POST

/segments

Create a segment

GET

/contacts

List contacts

POST

/contacts

Create a contact

GET

/contacts/{contact}

Retrieve a contact

GET

/contacts/{contact}/position

Retrieve a contact's leaderboard standing

POST

/invitations

Mint an invitation

GET

/broadcasts

List broadcasts

POST

/broadcasts/{broadcast}/send

Send or schedule a broadcast

POST

/segments

Create a segment

Why Jentic?

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

Setup

Wiring the LaunchList API by hand means handling its workspace bearer key, learning its handle-style ids and cursor pagination, and coding the contact and broadcast calls yourself. Through Jentic you install once, import the API from the API Directory, store the key once, and your agent calls it.

Permission scoping

LaunchList puts contact and broadcast ids in the URL path, so a rule can bound your agent to the operations it needs, such as adding contacts and reading positions. You choose which operations it may call, so sending a broadcast is not included unless you add it.

Credential isolation

Your LaunchList 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 'add a contact to a waitlist' or 'send a broadcast', and Jentic returns the matching LaunchList operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using LaunchList API through Jentic.

Is there a LaunchList API MCP server?

You do not need an MCP server to give your agent the LaunchList API. Jentic connects it directly from the API Directory: import the API, store your key once, and your agent calls the contact, invitation, broadcast, and segment operations. Operations are discovered on demand, so no extra server definitions load into the agent's context.

What authentication does the LaunchList API use?

The API authenticates with a bearer key per its OpenAPI spec, sent in the Authorization header, and the key belongs to the workspace rather than to the person who created it. Through Jentic the key is stored encrypted in your own Jentic One instance and supplied only when an allowed call runs, so it never reaches the agent's context.

Can I send an email broadcast with the LaunchList API?

Yes. The broadcast operations let you create a draft, send a test to your team, prepare it, and then send or schedule it to a segment, with pause and resume available while it is going out. Each step is a separate operation so a workflow can stage the send before it reaches contacts.

What are the rate limits for the LaunchList API?

The OpenAPI spec does not specify rate limits. Lists are cursor-paginated to keep large reads efficient, and you can confirm the current request limits in the LaunchList documentation at https://getlaunchlist.com/docs.

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

Yes. Write a rule that permits only the contact read and create operations when the agent should capture signups, and add the broadcast send operations only for workflows that actually email contacts, so a draft can never go out without your explicit choice, with every call logged.

How do I add a contact to a waitlist with the LaunchList API through Jentic?

Search Jentic for 'add a contact to a waitlist' to surface the create-contact operation, load its input schema, pass the email and any referral code, and execute, then read the contact's position to show their standing. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Getlaunchlist LaunchList API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingEmail Marketingbearer53 EndpointsREST

For Agents

Run a waitlist and referral program through LaunchList: add and update contacts, track referrals and leaderboard position, mint invitations, and draft and send email broadcasts to segments.

Use for: Add a contact to the launch waitlist, Retrieve a contact's live leaderboard standing, List the people a contact has referred, Mint an invitation code for early access

Not supported: Does not handle SMS, transactional receipts, or payment collection. Use for waitlist signups, referral tracking, and email broadcasts only.

The LaunchList API runs waitlist signups, referral programs, and email broadcasts for a product launch. It creates and updates contacts through the same submit pipeline the hosted signup page uses, so canonicalization, dedupe, referral credit, and automation enrollment all fire on an API call just as they do on a typed signup. It tracks each contact's referrals and live leaderboard position, mints and redeems invitations, and drafts, tests, and sends email broadcasts to segments of contacts. It is aimed at founders and growth teams automating a pre-launch waitlist and referral loop.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

97%

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

42%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

49%

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

64%

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.

58%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

93%

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 LaunchList API to your agent

Capabilities

Start building with LaunchList API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Getlaunchlist LaunchList API

Jentic AI Readiness Score

LaunchList 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