Install Jentic One Beta

Connect the snaplab API to your agent

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

Screenshot a URL or raw HTML as PNG, JPEG, WebP, or AVIF at a chosen viewport, deviceScaleFactor, or full page

Render a page to PDF with options such as pdf.format, pdf.landscape, and header and footer templates

Clip a capture to one element with selector and hide others with hideSelectors

Generate a fixed-size Open Graph image from an HTML template and a data object

GET STARTED

Start building with snaplab API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use snaplab API for, with concrete tasks.

★ Agent visual checks of web pages

An AI agent reviewing a deploy needs to see the page, not just its HTML. Through Jentic it finds the snaplab render operation by intent, requests a full-page PNG of the URL with dismissBanners and blockAds on, and passes the image to a vision model, with the sk_ key held by your own instance.

Call POST /api/render with url set to the staging homepage, fullPage true, format png, and dismissBanners true, then attach the image to the deploy review

HTML to PDF documents

Apps that generate invoices or reports in HTML need print-ready PDFs. The render endpoint takes html or a url with format set to pdf and PDF options for paper format, landscape, background printing, margins, and header and footer templates, and returns the file bytes.

Call POST /api/render with html set to the invoice markup and format set to pdf, then save the returned file

Open Graph image generation

Every blog post or product page needs a social card. The image endpoint renders HTML, or a template with a data object, into an image of a fixed width and height, with Google Fonts support, so a publishing pipeline can create a card per post from one template.

Call POST /api/render/image with a template containing a title placeholder, data set to the post title, width 1200 and height 630, and save the PNG

Stored captures with webhooks

Batch jobs that capture many pages should not hold a connection open for each. POST /api/captures renders and stores a capture and calls a webhookUrl signed with webhookSecret when it is done, and the captures list filters by status and q so the job can collect results later.

Call POST /api/captures with webhookUrl set to your callback endpoint, then GET /api/captures/{id} once the webhook arrives

Key Endpoints

21 endpoints — the snaplab api renders web pages and raw html in a headless chromium and returns the result as png, jpeg, webp, avif, or pdf.

METHOD

PATH

DESCRIPTION

POST

/api/render

Render a URL or HTML to an image or PDF

GET

/api/render

Render by query string or signed URL

POST

/api/render/image

HTML to a fixed-size image

POST

/api/captures

Render and store a capture

GET

/api/captures

List stored captures

GET

/api/me

Account plan and usage

POST

/api/render

Render a URL or HTML to an image or PDF

GET

/api/render

Render by query string or signed URL

POST

/api/render/image

HTML to a fixed-size image

POST

/api/captures

Render and store a capture

GET

/api/captures

List stored captures

GET

/api/me

Account plan and usage

Why Jentic?

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

Setup

Wiring snaplab by hand means sending the sk_ bearer key, or building signed URLs with keyId and an HMAC_SHA256 sig for GET renders, and handling quota and capacity responses. Through Jentic you install once, import snaplab from the API Directory, store the key once, and your agent calls it.

Permission scoping

snaplab takes the target url or html in the request body or query string, so rules bound which operations your agent may call, not which site it renders. You choose the operations it may call, so account ones like key creation, key revocation, or capture deletion are not included unless you add them.

Credential isolation

Your snaplab 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 'screenshot a website' or 'generate an og image', and Jentic returns the matching snaplab operation with its input schema so the agent sets format, fullPage, and selector correctly without reading the reference docs.

FAQs

Specific to using snaplab API through Jentic.

What authentication does the snaplab API use?

Per its OpenAPI spec, the snaplab API uses HTTP bearer authentication with an sk_ key as the default. The GET render and GET image operations also accept signed-URL auth, where keyId and sig query parameters carry the key id and an HMAC_SHA256 signature instead of the secret. The health check, the demo preview, the free tools, and the Stripe webhook receiver are declared without a security requirement.

Can I screenshot just one element of a page with the snaplab API?

Yes. Pass a CSS selector in the selector option on POST /api/render and the capture is clipped to that element; if nothing matches, the API returns 422 selector_not_found. waitForSelector delays the shot until an element appears, and hideSelectors removes elements such as chat widgets before capture.

What are the rate limits for the snaplab API?

The spec lists per-plan limits: free allows 100 renders a month at 30 a minute, starter 2,000 at 120 a minute, pro 10,000 at 300 a minute, and business 40,000 at 600 a minute. The key-less tools allow 20 renders a day per IP. Cache hits and failed renders do not count against quota.

Is there a snaplab MCP server?

The spec describes a stateless MCP server at /mcp with screenshot, pdf, html_to_image, and usage tools. You do not need it to give your agent snaplab: Jentic connects the REST API directly from the API Directory, so your agent gets the full render, capture, and key surface on demand without loading another server's tool definitions into its context.

How do I render a page to PDF through Jentic?

Search Jentic for 'convert a web page to pdf', load POST /api/render, and send url or html with format set to pdf and any PDF options you need. Your instance attaches the bearer key at call time. 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 snaplab API?

Yes. Write a rule that allows only POST /api/render and POST /api/render/image, and the agent can take screenshots and make images but cannot create or revoke keys, delete captures, or start a billing checkout, and every call it makes is logged.

Hsingh App snaplab API

AI ReadinessFoundational (C+)57/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaImage Processingbearer, apiKey21 EndpointsREST

For Agents

Screenshot a URL or HTML, render it to PDF, or turn an HTML template into a fixed-size Open Graph image, with full-page, element clipping, and dark mode options.

Use for: Take a full-page screenshot of a landing page, Convert this HTML invoice to a PDF, Generate an Open Graph image for a blog post title, Get the screenshot of just the pricing table on a page

Not supported: Does not crawl sites, extract structured data, or host images on a CDN beyond stored captures. Use for rendering URLs and HTML to images and PDFs only.

The snaplab API renders web pages and raw HTML in a headless Chromium and returns the result as PNG, JPEG, WebP, AVIF, or PDF. A render can capture the viewport or the full page, clip to one element with selector, switch on dark mode, hide selectors, dismiss cookie banners, block ads, and wait for a selector before shooting. A separate image endpoint turns HTML or a template with data into a fixed-size image for Open Graph cards, stored captures can notify a webhook when they finish, and repeat renders with identical options are served from a shared cache that does not count against quota.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

88%

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

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

62%

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

41%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

86%

OperationId Quality

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

63%

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

30%

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

77%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the snaplab API to your agent

Capabilities

Start building with snaplab API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Hsingh App snaplab API

Jentic AI Readiness Score

snaplab 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