Install Jentic One Beta

Connect the CurlShot API to your agent

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

Capture a full-page screenshot of a URL as an image or PDF

Queue many URLs at once as a bulk screenshot batch

Poll a background job for a capture's completion state

Retrieve every job that belongs to one bulk batch

Download a stored screenshot or PDF result file

GET STARTED

Start building with CurlShot API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use CurlShot API for, with concrete tasks.

★ Agent-driven page capture

An AI agent captures how a webpage looks right now, requesting a full-page image or PDF of a URL and attaching it to a report or ticket. Because a capture can run synchronously or return a job to poll, the agent handles both quick single shots and slower full-page renders without blocking on a long request.

Capture a full-page PDF of a given URL and download the resulting file once the job completes

Bulk visual monitoring

Teams that watch many pages for visual regressions need captures at scale. The bulk endpoint queues many URLs in one call and groups the resulting jobs into a batch, so an agent can submit a list of pages, retrieve the batch, and download each image for a before-and-after comparison.

Queue a bulk batch of ten URLs, retrieve the batch, and download every completed screenshot

On-demand previews with device presets

Previewing a page across devices needs consistent viewport settings. CurlShot exposes device presets and reports quota usage, so an agent can render a page against a chosen preset for a thumbnail or preview and track how much of the billing period's quota each run consumes.

List device presets, capture a page using a mobile preset, and read the remaining quota usage

Key Endpoints

10 endpoints — the curlshot api turns a website address into a screenshot of the whole page, returned as an image or a pdf.

METHOD

PATH

DESCRIPTION

GET

/api/v1/screenshot

Take a screenshot

POST

/api/v1/screenshot

Take a screenshot from a JSON body

POST

/api/v1/bulk

Queue many screenshots at once

GET

/api/v1/jobs/{id}

Get a background job's state

GET

/api/v1/batches/{id}

Get every job in one bulk batch

GET

/api/v1/files/{file}

Download a stored result

GET

/api/v1/devices

List device presets

GET

/api/v1/usage

Get quota and limits for the billing period

GET

/api/v1/screenshot

Take a screenshot

POST

/api/v1/screenshot

Take a screenshot from a JSON body

POST

/api/v1/bulk

Queue many screenshots at once

GET

/api/v1/jobs/{id}

Get a background job's state

GET

/api/v1/batches/{id}

Get every job in one bulk batch

GET

/api/v1/files/{file}

Download a stored result

GET

/api/v1/devices

List device presets

GET

/api/v1/usage

Get quota and limits for the billing period

Why Jentic?

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

Setup

Wiring the CurlShot API by hand means choosing where to put the access key, deciding between synchronous capture and the bulk-plus-polling flow, and computing an HMAC signature when a key requires it. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.

Permission scoping

CurlShot carries the target URL in the request parameters, so a rule bounds which operations your agent may call, such as the screenshot and job reads. You choose the operations it may call, so bulk queueing is not included unless you add it.

Credential isolation

Your CurlShot access 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 'take a webpage screenshot' or 'capture a URL as PDF', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using CurlShot API through Jentic.

What authentication does the CurlShot API use?

The CurlShot API accepts an access key three ways, as declared in its OpenAPI spec: the access_key query parameter, the X-Access-Key header, or an Authorization bearer token. A key can also require signed requests with an HMAC signature. Through Jentic the key is stored encrypted by your own Jentic One instance and injected when a call runs, so it never reaches the agent's prompt or logs.

Can I capture many URLs in one request with this API?

Yes. The bulk endpoint queues many URLs at once and groups the resulting jobs into a batch, and you retrieve the batch by its id to collect every completed capture.

What are the rate limits for the CurlShot API?

The OpenAPI spec does not publish fixed numeric limits, but it exposes a usage endpoint that returns your quota and limits for the current billing period, and it signals a quota_exceeded error when you run over. Read the usage endpoint to pace requests.

Is there a CurlShot MCP server?

You do not need an MCP server to give your agent the CurlShot API. Jentic connects it directly from the API Directory: import it, store your access key once, and your agent captures screenshots on demand.

Can I limit what my agent is allowed to do with the CurlShot API?

Yes. CurlShot carries the target URL in the request parameters, so a rule bounds which operations your agent may call, such as taking a screenshot and reading jobs, rather than naming a URL, and every call it makes is logged.

How do I capture a screenshot with this API through Jentic?

Search Jentic for an intent like 'take a webpage screenshot' and it returns the matching operation with its input schema, then your agent calls it with the access key Jentic injects at runtime. To run it on your own infrastructure, install Jentic One from its GitHub repo.

CurlShot API

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaImage ProcessingapiKey, bearer10 EndpointsREST

For Agents

Capture a full-page screenshot of a URL as an image or PDF, queue bulk captures, poll jobs and batches, and download stored result files.

Use for: Take a screenshot of a webpage as an image, Capture a full page as a PDF, Queue a batch of URLs for bulk screenshots, Check whether my screenshot job has finished

Not supported: Does not handle image editing, OCR, or structured web scraping. Use for capturing full-page website screenshots and PDFs only.

The CurlShot API turns a website address into a screenshot of the whole page, returned as an image or a PDF. It takes a capture synchronously or queues many URLs at once as a bulk batch, then exposes background jobs, batches, and stored result files so a caller can poll for completion and download the output. Device presets and a usage endpoint round it out, giving a small, focused rendering surface.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

97%

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

50%

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

24%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

68%

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

48%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

90%

OperationId Quality

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

60%

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

42%

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 CurlShot API to your agent

Capabilities

Start building with CurlShot API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

CurlShot API

Jentic AI Readiness Score

CurlShot 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