Install Jentic One Beta

Connect the HTML to Image API to your agent

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

Render your own HTML and CSS to a PNG or PDF at a chosen width, height, and dpi

Capture a public URL as an image or PDF, optionally clipped to one element with selector

Fill a named template such as open-graph-image, invoice, or certificate-of-completion from a JSON payload

Wait for a selector or a ms_delay before rendering so late-loading content appears

GET STARTED

Start building with HTML to Image API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use HTML to Image API for, with concrete tasks.

★ Agent-generated share images

An AI agent publishing content needs a social card for each post without a designer. Through Jentic it finds the html2img template operation by intent, posts the post title and author to the open-graph-image template, and attaches the returned CDN URL to the post metadata, with the htim_ key held by your own instance.

Call POST /v1/templates/{slug} with slug set to open-graph-image and the post's title fields, then save the returned URL as the og:image

Documents as images or PDFs

Apps that send receipts, tickets, or certificates as attachments can describe them in HTML. POST /html takes html and css with width, height, dpi, and format set to png or pdf, and scale_to_fit keeps fixed-size artwork whole on a PDF page.

Call POST /html with html set to the receipt markup, css set to the receipt styles, and format set to pdf, then email the returned URL

Screenshots of external pages

Monitoring, archiving, or QA work needs pictures of pages you do not control. POST /screenshot takes a url with optional selector, fullpage, wait_for_selector, and ms_delay, and returns a CDN URL to the PNG or PDF.

Call POST /screenshot with url set to the competitor pricing page and fullpage true, then store the returned image URL

Key Endpoints

5 endpoints — the html2img html to image api converts html and css, or any public url, into a png image or a vector pdf rendered in headless chrome, and returns a cdn url for the result.

METHOD

PATH

DESCRIPTION

POST

/html

Render HTML to a PNG or PDF

POST

/screenshot

Capture a public URL

POST

/v1/templates/{slug}

Render a named template

GET

/me

Account behind the key

POST

/html

Render HTML to a PNG or PDF

POST

/screenshot

Capture a public URL

POST

/v1/templates/{slug}

Render a named template

GET

/me

Account behind the key

Why Jentic?

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

Setup

Wiring html2img by hand means sending the htim_ key in the X-API-Key header, keeping it server-side because it spends credits, and choosing between synchronous renders and webhook_url delivery. Through Jentic you install once, import html2img from the API Directory, store the key once, and your agent calls it.

Permission scoping

html2img puts the template slug in the URL path (/v1/templates/{slug}), so a rule can pin your agent to one template such as open-graph-image. You choose the operations it may call, so free-form HTML rendering or URL screenshots are not included unless you add them.

Credential isolation

Your html2img 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 'generate an og image' or 'html to pdf', and Jentic returns the matching html2img operation with its input schema so the agent sends valid html, url, or template fields without reading the reference docs.

FAQs

Specific to using HTML to Image API through Jentic.

What authentication does the HTML to Image API use?

Per its OpenAPI spec, html2img authenticates with an API key in the `X-API-Key` header, with keys prefixed htim_ and created in the html2img dashboard. GET /ping is declared without a security requirement, and GET /me lets you verify a key without spending a credit. Through Jentic the key is stored by your own instance and attached at call time.

Which templates can I render with the HTML to Image API?

POST /v1/templates/{slug} takes a template slug such as open-graph-image, invoice, event-ticket, code-screenshot, github-repo-card, or certificate-of-completion, with the full list and each template's fields documented by html2img. Fields a template does not recognise are rejected with a 422, and an unknown slug returns 404 template_not_found.

What are the rate limits for the HTML to Image API?

The spec states there is no rate-limit response: usage is metered in credits, one per successful render whether PNG or PDF, and running out returns 402 with your balance. Synchronous requests have a time budget, so pass webhook_url for slower renders.

Is there an html2img MCP server?

The spec notes that html2img offers its render capabilities over MCP on paid plans, using the same key. You do not need it to give your agent html2img: Jentic connects the REST API directly from the API Directory, so your agent discovers the render, screenshot, and template operations on demand without loading another server's tool definitions into its context.

How do I render HTML to an image through Jentic?

Search Jentic for 'convert html to an image', load POST /html, and send html with optional css, width, height, and format set to png. Your instance attaches the X-API-Key at call time and the response carries the CDN 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 HTML to Image API?

Yes. Write a rule that allows only POST /v1/templates/{slug} and GET /me, and the agent can fill templates and check its credit balance but cannot render arbitrary HTML or screenshot URLs, and every call it makes is logged.

Html2img HTML to Image API

AI ReadinessAI-Aware (B)67/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaImage ProcessingapiKey5 EndpointsREST

For Agents

Render HTML and CSS or a public URL to a PNG or PDF, or fill a named template like an Open Graph card or invoice, and get back a CDN URL.

Use for: Turn this HTML snippet into a PNG, Generate an Open Graph image for a new blog post, Take a full-page screenshot of a public URL, Create an invoice PDF from a template

Not supported: Does not edit existing images, host arbitrary uploads, or scrape page data. Use for rendering HTML, URLs, and templates to PNG or PDF only.

The html2img HTML to Image API converts HTML and CSS, or any public URL, into a PNG image or a vector PDF rendered in headless Chrome, and returns a CDN URL for the result. You post your own markup to the html endpoint, capture a page you do not control through the screenshot endpoint, or fill a named template such as open-graph-image, invoice, event-ticket, or github-repo-card with a JSON payload. Each successful render costs one credit, requests return the finished URL synchronously or deliver it to a webhook_url for slower jobs, and paid-plan renders are hosted permanently.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B+Signals: 4

95%

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

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

49%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

60%

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

54%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

80%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

71%

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

50%

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

95%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the HTML to Image API to your agent

Capabilities

Start building with HTML to Image API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Html2img HTML to Image API

Jentic AI Readiness Score

HTML to Image 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