Install Jentic One Beta

Connect the HTML/CSS to Image API to your agent

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

Render HTML and CSS, or a live url, to an image with selector clipping, viewport size, device_scale, and google_fonts

Fetch a rendered image in a specific format and resize or crop it with width, height, and crop query options

Create a batch of image variations, or a batch of templated images filled from template_values, in one request

Version reusable HTML templates and list a template's versions

GET STARTED

Start building with HTML/CSS to Image API

Explore with Jentic One

View OpenAPI Document

Use Cases

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

★ Agent-made graphics from HTML

An AI agent producing a weekly report needs a chart card or quote graphic it can drop into email or chat. Through Jentic it finds the HTML/CSS to Image create operation by intent, posts the html and css it wrote, and returns the hosted image URL, with the API ID and key held by your own instance.

Call POST /v1/image with html set to the report card markup, css set to its styles, and google_fonts set to Inter, then return the image URL

Templated images in bulk

Marketing teams need one design rendered many times, such as a card per product or speaker. A versioned template holds the HTML, and the templated batch endpoint takes a list of variations, each with its own template_values, plus shared default_options, so a single call produces the full set.

Call POST /v1/image/batch/templated with variations listing template_values for each speaker's name and talk title, then collect the returned image ids

Website screenshots

QA, archiving, or link previews need pictures of live pages. Sending a url to the create endpoint renders the page with options like full_screen, viewport_mobile, block_consent_banners, and custom headers, and the image can then be fetched in any format with resize and crop parameters.

Call POST /v1/image with url set to the release notes page and full_screen true, then fetch GET /v1/image/{id}.{format} with format png and width 1200

Renders delivered to your own storage

Teams that keep assets in their own bucket can register a storage destination with its connection_info, then render and store an image there with the store endpoint instead of downloading and re-uploading it.

Call POST /v1/storage-destinations with name and connection_info for your bucket, then PUT /v1/store/{id}.{format} for a rendered image id with format png

Key Endpoints

40 endpoints — the html/css to image api renders html and css, or a live website url, into an image and returns a hosted image id that can be fetched in a chosen format, size, or crop.

METHOD

PATH

DESCRIPTION

POST

/v1/image

Create an image from HTML or a URL

GET

/v1/image/{id}.{format}

Render an image in a specific format

POST

/v1/image/batch

Create a batch of images

POST

/v1/image/batch/templated

Create a batch of templated images

POST

/v1/template

Create a template

PUT

/v1/store/{id}.{format}

Render and store in a storage destination

GET

/v1/usage

Organization usage

POST

/v1/image

Create an image from HTML or a URL

GET

/v1/image/{id}.{format}

Render an image in a specific format

POST

/v1/image/batch

Create a batch of images

POST

/v1/image/batch/templated

Create a batch of templated images

POST

/v1/template

Create a template

PUT

/v1/store/{id}.{format}

Render and store in a storage destination

GET

/v1/usage

Organization usage

Why Jentic?

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

Setup

Wiring HTML/CSS to Image by hand means base64-encoding the API ID and key into basic auth, picking between JSON, form, and multipart bodies, and handling per-group rate limits. Through Jentic you install once, import HTML/CSS to Image from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

HTML/CSS to Image puts template, image, and storage ids in the URL path (/v1/template/{id}, /v1/image/{id}), so a rule can pin your agent to one template's versions and the operations you pick. You choose the operations it may call, so destructive ones like API key deletion or template removal are not included unless you add them.

Credential isolation

Your HTML/CSS to Image API ID and key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'turn html into an image' or 'batch generate social images', and Jentic returns the matching HTML/CSS to Image operation with its input schema so the agent sends valid html, url, or template_values without reading the reference docs.

FAQs

Specific to using HTML/CSS to Image API through Jentic.

What authentication does the HTML/CSS to Image API use?

Per its OpenAPI spec, the HTML/CSS to Image API uses HTTP basic auth with your API ID as the username and your API key as the password. Fetching a rendered image by id is declared public, and the create-and-render URL carries the api_id and a token in its path instead of a header. Through Jentic the API ID and key are stored by your own instance and attached at call time.

Can I generate many images from one template with the HTML/CSS to Image API?

Yes. POST /v1/image/batch/templated takes a required variations list, each with its own template_values, plus default_options shared across the batch. POST /v1/image/batch does the same for plain html or url variations, and DELETE /v1/image/batch removes a set of images by ids.

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

The spec sets limits per operation group per organization, shared across all your API keys: for example, 20 requests per minute for proxy:write and og-config:write operations and 100 requests per minute for api-key:read. Over a limit the API returns 429 Too Many Requests with RateLimit-Policy headers.

Is there an HTML/CSS to Image MCP server?

You don't need an MCP server to give your agent HTML/CSS to Image. Jentic connects it directly from the API Directory: import it, store your API ID and key once, and your agent discovers the image, template, and storage operations on demand without loading another server's tool definitions into its context.

How do I screenshot a website through Jentic?

Search Jentic for 'screenshot a website', load POST /v1/image, and send a url with options such as full_screen or block_consent_banners. Your instance attaches the basic auth credentials at call time and the response returns the image id and 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/CSS to Image API?

Yes. Write a rule that allows only POST /v1/image and GET /v1/images, and the agent can render and list images but cannot create API keys, delete templates, or change storage destinations, and every call it makes is logged.

HTML/CSS to Image API

AI ReadinessNon-Ready (F)37/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaImage Processingbasic40 EndpointsREST

For Agents

Render HTML and CSS or a website URL to an image, batch-generate templated images, store renders in your own storage, and manage templates, proxies, and scoped API keys.

Use for: Turn this HTML and CSS into a PNG, Take a screenshot of a website with consent banners blocked, Create 20 social images from one template with different titles, Get the image I rendered earlier as a JPG at 600 pixels wide

Not supported: Does not edit uploaded photos, run multi-step browser automation, or extract page data. Use for rendering HTML, CSS, URLs, and templates to images only.

The HTML/CSS to Image API renders HTML and CSS, or a live website URL, into an image and returns a hosted image id that can be fetched in a chosen format, size, or crop. Renders accept options such as selector, viewport_width, device_scale, google_fonts, color_scheme, ms_delay, and block_consent_banners, and batch endpoints create many variations, including templated ones filled from template_values, in one call. Account tooling covers versioned templates, Open Graph configurations, outbound proxies, external storage destinations that receive rendered files, scoped API keys, and organization usage.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4

91%

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

Example Density

How richly the API is illustrated with examples.

75%

Example Validity

Percentage of examples that conform to their schemas.

52%

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

62%

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.

19%

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

10%

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

75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the HTML/CSS to Image API to your agent

Capabilities

Start building with HTML/CSS to Image API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

HTML/CSS to Image API

Jentic AI Readiness Score

HTML/CSS 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