Install Jentic One Beta

Connect the MadeThis API to your agent

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

Create a product with priceAmountCents and pricingModel, sync it to Stripe, and issue a shareable checkout link

Refund an order fully or partially, or mark a physical order shipped with carrier and trackingNumber

Send email from the business inbox and read email threads with their messages

Import or search leads by jobTitles, industries, and locations, then enrol them in a cold-email sequence

GET STARTED

Start building with MadeThis API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MadeThis API for, with concrete tasks.

★ Coding agent launching a product through Jentic

A builder asks their coding agent to put a new template up for sale. Through Jentic the agent searches for 'create a product', loads the MadeThis product operation with its input schema, and posts the name and priceAmountCents, then requests a checkout link for the new productId. The business-scoped API key is injected at call time, so the agent never holds it.

Call POST /products with name 'Notion Budget Template' and priceAmountCents 1900, then POST /checkout-links with the returned productId and return the checkout URL

Order fulfilment and refunds

Once sales arrive, someone has to ship physical goods and handle refund requests. MadeThis lists orders newest first, marks a physical order shipped with an optional carrier and trackingNumber, and refunds an order fully or partially with amountCents and a reason; the refund call requires an Idempotency-Key so a retry cannot refund twice.

Call GET /orders, then POST /orders/{id}/ship with carrier and trackingNumber for each unshipped physical order

Cold-email outreach to a defined audience

A founder wants outbound without wiring a separate lead tool and mail sender. MadeThis searches leads matching an ideal customer profile by jobTitles, industries, locations, and company size, billed per Apollo enrichment, or imports a list the founder already has. A sequence is created as a draft with steps and an icpDescription and sends nothing until leads are enrolled, and enrolment is held for confirmation.

Call POST /leads/search with jobTitles ['Head of Marketing'] and industries ['Software'], then POST /sequences with name, icpDescription, and steps, then POST /sequences/{id}/leads with the leadIds

Meta ads under a spend policy

Paid acquisition is where an agent mistake costs real money. MadeThis creates and launches a Meta campaign asynchronously under the business spend policy, reports campaign insights that lag Meta by roughly thirty minutes, and changes the daily budget only when the expected current budget matches; budget increases are spend-gated while pausing a campaign is always available.

Call GET /ads/{id}/insights for a campaign and, if cost per result is above target, call POST /ads/{id}/pause

Key Endpoints

80 endpoints — the madethis api runs the business side of a small online product for builders who bring their own coding agent: products, checkout links, orders, customers, and stripe-backed subscriptions and payouts.

METHOD

PATH

DESCRIPTION

POST

/products

Create a product

POST

/checkout-links

Get a checkout URL for a product

GET

/orders

List orders

POST

/orders/{id}/refund

Refund an order

POST

/email/send

Send an email from the business inbox

POST

/sequences

Create a cold-email sequence

POST

/ads/publish

Create and launch a Meta campaign

POST

/confirmations/{id}/confirm

Confirm a parked action

POST

/products

Create a product

POST

/checkout-links

Get a checkout URL for a product

GET

/orders

List orders

POST

/orders/{id}/refund

Refund an order

POST

/email/send

Send an email from the business inbox

POST

/sequences

Create a cold-email sequence

POST

/ads/publish

Create and launch a Meta campaign

POST

/confirmations/{id}/confirm

Confirm a parked action

Why Jentic?

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

Setup

Wiring MadeThis by hand means minting a business-scoped bearer key, sending Idempotency-Key headers on writes, and handling parked confirmations and async ad publishing. Through Jentic you install once, import MadeThis from the API Directory, store the key once, and your agent calls it.

Permission scoping

MadeThis puts resource ids in the URL path, such as /orders/{id}/refund and /ads/{id}/budget, so a rule can pin your agent to one order or one campaign and the operations you pick. You choose the operations it may call, so money-moving ones like refunds, ad publishing, or budget changes are not included unless you add them.

Credential isolation

Your MadeThis 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 'refund an order' or 'pause an ad campaign', and Jentic returns the matching MadeThis operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using MadeThis API through Jentic.

What authentication does the MadeThis API use?

The MadeThis API authenticates with a business-scoped API key in the mt_live_ format, sent as an HTTP bearer token, per its OpenAPI spec. You mint it with the madethis login CLI command or in dashboard settings. The two CLI pairing operations, POST /cli-auth/start and POST /cli-auth/poll, need no key. Through Jentic the key is stored by your own instance and attached at call time.

Can I refund an order with the MadeThis API?

Yes. POST /orders/{id}/refund refunds an order fully, or partially when you pass amountCents, with an optional reason and note. The operation requires an Idempotency-Key header, so a retried call does not issue a second refund.

What are the rate limits for the MadeThis API?

The OpenAPI spec does not specify request rate limits, though it notes a per-inbox daily cap on email sends and gates spending by credit balance, which GET /usage reports. Check the MadeThis site at https://www.madethis.com for current limits.

Is there a MadeThis MCP server?

You don't need an MCP server to give your agent MadeThis. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the products, orders, email, and ads operations it needs, discovered on demand rather than loaded into its context up front.

How do I create a checkout link through Jentic?

Search Jentic for 'get a checkout link for a product', load the POST /checkout-links operation, and run it with the productId of an active product to get a shareable URL. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. For example, a rule that allows GET /orders, GET /ads/{id}/insights, and POST /ads/{id}/pause lets the agent review sales and stop a costly campaign while it cannot refund orders, publish ads, or raise a budget. Jentic logs each call the agent makes.

What are MadeThis confirmations?

Some actions, such as enrolling leads in a sequence or resuming one, are held as confirmations instead of running immediately. GET /confirmations lists them, POST /confirmations/{id}/confirm executes one exactly once, and POST /confirmations/{id}/reject ensures it never runs.

MadeThis API

AI ReadinessNon-Ready (C-)52/100

See full scorecard

Official vendor OpenAPI document · agent-readyE CommerceStorefronthttp (bearer)80 EndpointsREST

For Agents

Run a small online business with MadeThis: create products and checkout links, refund and ship orders, email customers, run outreach sequences, post to social, and launch Meta ads under a spend policy.

Use for: I need to create a digital product and get a checkout link for it, Refund the last order from a customer by email, List all orders from this week, Send a follow-up email to a customer from the business inbox

Not supported: Does not host a full multi-store storefront, file taxes, or run payroll. Use for running a small product business's sales, email, outreach, social, and ads only.

The MadeThis API runs the business side of a small online product for builders who bring their own coding agent: products, checkout links, orders, customers, and Stripe-backed subscriptions and payouts. Products created through it sync to Stripe when active, orders can be refunded fully or partially or marked shipped with tracking, and shareable checkout URLs are issued for any active product. The same business account also sends email from a provisioned inbox, runs cold-email sequences against imported or searched leads, publishes social posts, launches and pauses Meta ad campaigns, and registers custom domains. Risky actions can be parked as confirmations that the owner confirms or rejects, and a usage endpoint reports the credit balance and whether writes are currently allowed.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: FSignals: 4

42%

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

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

17%

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.

53%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

89%

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

53%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the MadeThis API to your agent

Capabilities

Start building with MadeThis API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

MadeThis API

Jentic AI Readiness Score

MadeThis 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