Install Jentic One Beta

Connect the htmlpub API to your agent

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

Publish a complete HTML document at a chosen slug, or replace a page you already own, with one PUT call

Change a page's HTML or title, or move it into a site, without resending everything

Upload images, CSS, JavaScript, and font files to a page and remove them individually or all at once

Group pages into sites with a name, slug, and default page

GET STARTED

Start building with htmlpub API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use htmlpub API for, with concrete tasks.

★ Agent-published pages through Jentic

An AI agent that writes HTML, such as a landing page, a report, or a prototype, can put it online with one call to the htmlpub create-or-update operation and share the resulting URL. Through Jentic the agent finds the operation by intent and the bearer key is injected at execution time, and because the page slug sits in the URL path a rule can limit the agent to the one page it is allowed to publish.

Call PUT /api/pages/{slug} with slug 'q3-report' and html set to the generated report document, then return the page URL to the user

Campaign landing pages

Marketing teams spin up short-lived pages for launches, events, and promotions. With htmlpub a page goes live from a single HTML document, its images and stylesheets upload as page assets, and related pages can be grouped into a site, so a campaign can be assembled and taken down programmatically.

Call POST /api/sites with slug 'spring-launch' and name 'Spring Launch', then PUT /api/pages/{slug} with slug 'spring-launch-home', the page html, and the new siteId

Custom domains for published pages

A page on a branded domain looks more credible than one on a shared host. The htmlpub custom domain operations attach a domain to a page by pageId, let you repoint it later, and verify the DNS records after you add the CNAME, returning an error until the configuration is correct.

Call POST /api/custom-domains with domain 'launch.example.com' and the page's pageId, then call POST /api/custom-domains/{domain}/verify after the CNAME record has been added

Page asset management

Pages often need their own images, stylesheets, scripts, and fonts. htmlpub accepts png, jpg, gif, svg, webp, css, js, woff, woff2, and ttf uploads per page, lists what a page holds, and deletes a single asset by assetId or clears every asset on the page.

Call POST /api/pages/{slug}/assets for slug 'spring-sale' with the file 'hero.webp', then reference the returned asset URL in the page HTML

Key Endpoints

20 endpoints — the htmlpub api publishes complete html documents as live web pages under a slug you choose, and updates or deletes them by that slug.

METHOD

PATH

DESCRIPTION

PUT

/api/pages/{slug}

Create or update a page

PATCH

/api/pages/{slug}

Update a page

GET

/api/pages

List all pages

POST

/api/pages/{slug}/assets

Upload an asset

POST

/api/sites

Create a site

POST

/api/custom-domains

Add a custom domain

POST

/api/custom-domains/{domain}/verify

Verify a custom domain

PUT

/api/pages/{slug}

Create or update a page

PATCH

/api/pages/{slug}

Update a page

GET

/api/pages

List all pages

POST

/api/pages/{slug}/assets

Upload an asset

POST

/api/sites

Create a site

POST

/api/custom-domains

Add a custom domain

POST

/api/custom-domains/{domain}/verify

Verify a custom domain

Why Jentic?

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

Setup

Wiring htmlpub by hand means managing an hp_live_ bearer key, knowing which read operations are open, and handling 409 conflicts when a slug belongs to someone else. Through Jentic you install once, import htmlpub from the API Directory, store the key once, and your agent calls it.

Permission scoping

htmlpub puts the page slug, site id, and custom domain in the URL path (/api/pages/{slug}, /api/sites/{siteId}), so a rule can pin your agent to one page or site and the operations you pick. You choose the operations it may call, so destructive ones like deleting a site or removing a custom domain are not included unless you add them.

Credential isolation

Your htmlpub 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 'publish an HTML page' or 'attach a custom domain', and Jentic returns the matching htmlpub operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using htmlpub API through Jentic.

Is there an htmlpub MCP server?

You don't need an MCP server to give your agent the htmlpub API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it. Operations are discovered on demand, so your agent's context carries no tool definitions it will not use.

What authentication does the htmlpub API use?

Per its OpenAPI spec, the htmlpub API uses HTTP bearer authentication with an API key that starts with hp_live_, created in the htmlpub dashboard. Reading a page's raw HTML and serving an asset are declared open and need no key. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at execution time.

Can I update an existing page with the htmlpub API?

Yes. PUT /api/pages/{slug} replaces a page you own with new html, returning 200 for an update and 201 for a new page, and 409 if another user holds the slug. PATCH /api/pages/{slug} changes only the fields you send, such as html, title, or siteId.

What are the rate limits for the htmlpub API?

The OpenAPI spec does not specify rate limits. It notes that page HTML can be up to 5MB and that asset size limits depend on your plan; check https://htmlpub.com for current limits.

Is the htmlpub API free?

No. Per the spec, API access requires a Pro plan, listed at $15 a month. Raw page HTML and page assets can be read without a key, but creating and managing pages needs a Pro API key.

How do I publish a page with htmlpub through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import the htmlpub API from the directory, and store your API key. Your agent then searches for 'publish an HTML page' and Jentic returns PUT /api/pages/{slug}, which takes the slug in the path and the html in the body. 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 htmlpub API?

Yes. Write a rule that allows only PUT /api/pages/{slug} and POST /api/pages/{slug}/assets for the slug 'agent-drafts': the agent can publish and add assets to that one page, while your other pages, sites, and custom domains stay out of reach, and every call it makes is logged.

Leadpages htmlpub API

AI ReadinessAI-Aware (B+)70/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingContent Managementbearer20 EndpointsREST

For Agents

Publish generated HTML as a live page at a chosen slug, update or delete it, upload page assets, group pages into sites, and attach and verify custom domains.

Use for: I need to publish this generated landing page HTML at the slug spring-sale, Update the title of my pricing page, List all pages on my htmlpub account, Upload a logo image to the launch page

Not supported: Does not handle drag-and-drop page building, form submissions, lead capture, or site analytics. Use for publishing and hosting HTML pages, their assets, and custom domains only.

The htmlpub API publishes complete HTML documents as live web pages under a slug you choose, and updates or deletes them by that slug. Each page can carry uploaded assets such as images, CSS, JavaScript, and fonts, pages can be grouped into sites with a default page, and a custom domain can be pointed at a page and verified once its CNAME record is in place. A single PUT creates a page or replaces one you own, returning 201 for new pages and 200 for updates, which makes it a direct way to put generated HTML online.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

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

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.

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

51%

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.

65%

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

79%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the htmlpub API to your agent

Capabilities

Start building with htmlpub API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Leadpages htmlpub API

Jentic AI Readiness Score

htmlpub 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