Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Rendex Rendering 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%2Frendex.dev%2Frendex" | shStep 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%2Frendex.dev%2Frendex" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Rendex Rendering API.
Capture a full-page screenshot of any URL as PNG, JPEG, WebP, or PDF
Render raw HTML or Markdown into an image or a PDF with page size and margins
Batch-capture up to 500 URLs asynchronously and poll the batch status
Extract a page's main content as Markdown, JSON, HTML, or text
Mint a signed hosted-render URL for an OG image that renders on first hit
GET STARTED
Watch a page on an interval and get a webhook or email when it visibly changes
Render a branded PDF and PNG artifact from Markdown or HTML content
Patterns agents use Rendex Rendering API for, with concrete tasks.
★ Agent eyes on the web
An agent that needs to see a page, not just its HTML, asks Rendex for a screenshot and gets back an image it can inspect or attach. The JSON variant returns the capture as base64 so the agent can pass it straight to a vision model, with waitUntil and waitForSelector controlling when the capture fires.
Call POST /v1/screenshot/json with url set to https://example.com, fullPage set to true, and format set to png
HTML and Markdown to PDF
Invoices, reports, and certificates generated as HTML or Markdown are rendered to PDF by setting format to pdf, with pdfFormat, pdfLandscape, pdfMargin, and pdfPrintBackground controlling the layout. The artifact operation goes further and renders a branded PDF and PNG pair from the same content.
Call POST /v1/screenshot with html set to the invoice markup, format set to pdf, and pdfFormat set to A4
Bulk capture for audits and archives
A batch request takes up to 500 URLs, each able to override shared defaults, and returns a batch id to poll or a webhookUrl to call on completion. This suits visual regression sweeps, competitor archives, and SEO audits across a whole sitemap.
Call POST /v1/screenshot/batch with urls listing the sitemap pages, then GET /v1/batches/{batchId} until the batch completes
Page change monitoring
A watch re-renders a URL every intervalMinutes and compares the result using a diffMode and threshold, optionally adding an aiSummary of what changed and notifying a webhookUrl or notifyEmail. Watches can be dry-run first, triggered on demand, paused, and their run history read back.
Call POST /v1/watches/test with url set to the pricing page to check the config, then POST /v1/watches with the same url, intervalMinutes set to 1440, and notifyEmail set to the team inbox
21 endpoints — the rendex rendering api turns a webpage url, raw html, or markdown into a png, jpeg, webp, or pdf, with options such as fullpage capture, darkmode, blockads, custom css and js injection, device presets, and geo-targeted rendering.
METHOD
PATH
DESCRIPTION
/v1/screenshot
Capture a screenshot, returns image binary
/v1/screenshot/json
Capture a screenshot, returns base64 JSON
/v1/screenshot/batch
Batch capture multiple URLs
/v1/batches/{batchId}
Poll batch status
/v1/extract
Extract clean content from a URL
/v1/render/link
Mint a signed hosted-render URL
/v1/watches
Create a page watch
/v1/artifact
Render a branded PDF and PNG artifact
/v1/screenshot
Capture a screenshot, returns image binary
/v1/screenshot/json
Capture a screenshot, returns base64 JSON
/v1/screenshot/batch
Batch capture multiple URLs
/v1/batches/{batchId}
Poll batch status
/v1/extract
Extract clean content from a URL
/v1/render/link
Mint a signed hosted-render URL
/v1/watches
Create a page watch
/v1/artifact
Render a branded PDF and PNG artifact
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Rendex by hand means choosing between its bearer, x-api-key, and key query auth, picking binary or base64 responses, and polling job and batch ids for async captures. Through Jentic you install once, import Rendex from the API Directory, store the key once, and your agent calls it.
Permission scoping
Rendex carries the page to render in the request body, so rules bound which operations your agent may call, not which sites it captures. Watches, jobs, and batches do sit in the URL path (/v1/watches/{id}), so a rule can tie the agent to one watch, and you choose whether destructive ones like watch deletion are included.
Credential isolation
Your Rendex 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 'screenshot a webpage' or 'convert a page to Markdown', and Jentic returns the matching Rendex operation with its input schema so the agent sets the right render options.
Alternatives and complements available in the Jentic catalogue.
Specific to using Rendex Rendering API through Jentic.
What authentication does the Rendex Rendering API use?
Per its OpenAPI spec, Rendex authenticates with your API key sent as a bearer token (Authorization: Bearer rdx_...). The GET screenshot operation also accepts the key in an x-api-key header or a key query parameter. The health checks and the signed GET /v1/render link need no API key; for render links the HMAC signature in the URL is the auth boundary. Through Jentic, your key is stored encrypted by your own Jentic One instance and injected at execution time.
Can I turn a webpage into Markdown with Rendex?
Yes. POST /v1/extract takes a url and returns the page's clean content, with extractFormat set to markdown by default or to json, html, or text. Options such as device, waitUntil, and blockCookieBanners control how the page loads first.
How many URLs can a Rendex batch capture?
A batch request accepts between 1 and 500 URLs in its urls array, each able to override the shared defaults. Poll GET /v1/batches/{batchId} for progress or pass a webhookUrl to be notified.
What are the rate limits for the Rendex Rendering API?
The OpenAPI spec does not publish a fixed number. GET /v1/account returns your plan, usage, and per-minute rate limit, and calls over the limit get a RATE_LIMITED error. See https://rendex.dev for plan details.
How do I take a screenshot through Jentic?
Search Jentic for 'screenshot a webpage'. It returns the Rendex screenshot operations with their input schema; your agent sets url and options such as fullPage or format, and Jentic sends the call with your stored key. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a Rendex MCP server?
You don't need an MCP server to give your agent Rendex. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it, discovering the capture, extract, and watch operations on demand instead of loading every tool definition into its context.
Can I limit what my agent is allowed to do with the Rendex Rendering API?
Yes. A research agent could be allowed POST /v1/screenshot/json and POST /v1/extract only, so it can see and read pages but cannot create, change, or delete watches or start batch captures. Which URLs it renders is set in the request body, so the rule bounds the operations, not the target sites.
For Agents
Screenshot webpages, render HTML or Markdown to image or PDF, batch-capture up to 500 URLs, extract page content as Markdown, and watch pages for visual changes with Rendex.
Use for: Take a full-page screenshot of https://example.com, Convert this HTML invoice to a PDF, Get the content of this article as Markdown, Capture screenshots of these 200 product pages
Not supported: Does not handle multi-page site crawling, image editing of existing files, or video capture. Use for rendering webpages, HTML, or Markdown to images and PDFs, extracting page content, and watching pages for changes only.
The Rendex Rendering API turns a webpage URL, raw HTML, or Markdown into a PNG, JPEG, WebP, or PDF, with options such as fullPage capture, darkMode, blockAds, custom css and js injection, device presets, and geo-targeted rendering. Batches of up to 500 URLs run asynchronously with job and batch status polling and optional webhook delivery. It also mints signed hosted-render links for OG images, extracts a page's content as Markdown, JSON, HTML, or text, renders branded PDF and PNG artifacts, and runs scheduled visual watches that diff a page over time.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>