Install Jentic One Beta

Connect the CaptureKit API Reference to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CaptureKit API Reference, 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%2Fcapturekit.dev%2Fcapturekit" | 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%2Fcapturekit.dev%2Fcapturekit" | 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 CaptureKit API Reference API.

Capture a webpage as a PNG, JPEG, WebP, or PDF screenshot, full page or a single CSS selector

Emulate a device such as iphone_14_pro or galaxy_s23 and set viewport_width, viewport_height, and scale_factor

Extract a page's metadata, links, and optionally its HTML, Markdown, and sitemap in one request

Analyze a webpage with AI to get a summary, value proposition, features, categories, and use cases, guided by a custom_prompt

GET STARTED

Start building with CaptureKit API Reference API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use CaptureKit API Reference API for, with concrete tasks.

★ Agent web reading through Jentic

An AI agent asked about a webpage needs the page's text in a form it can reason over. Through Jentic the agent searches for 'get the markdown of a webpage', receives the CaptureKit Content operation with its input schema, and calls GET /v1/content with the url and include_markdown set to true. With remove_cookie_banners and remove_ads enabled, the agent reads clean Markdown and the page's links and metadata.

Call GET /v1/content with url 'https://example.com/blog/post', include_markdown true, and remove_cookie_banners true, then summarise the Markdown returned

Visual QA and monitoring screenshots

A team checking releases wants screenshots of key pages on desktop and mobile. GET /v1/capture takes a url, format, device such as iphone_14_pro, and full_page with full_page_scroll to load lazy content, and can wait_for_selector before capturing. Setting s3_url with s3_bucket and the S3 keys uploads the image straight to storage for later comparison.

Call GET /v1/capture with url 'https://example.com/pricing', format 'png', device 'iphone_14_pro', and full_page true, then return the image

Company page analysis for research

A sales or research agent needs a quick read of what a company's website says. GET /v1/analyze returns an AI summary of the page with its value proposition, features, categories, and use cases, and accepts a custom_prompt to steer the analysis and custom_response to add fields to the output. Caching with cache and cache_ttl avoids paying twice for the same page.

Call GET /v1/analyze with url 'https://example.com' and custom_prompt 'List the pricing tiers mentioned', then report the summary and features

Lightweight HTML fetch for audits

An SEO audit script needs raw HTML quickly, without a browser render. GET /v1/website/crawler fetches a URL in request mode, follows or ignores redirects with allow_redirects, and returns the HTML source when return_page_source is true. It suits link and metadata extraction across many URLs where screenshots are not needed.

Call GET /v1/website/crawler with query 'https://example.com', allow_redirects false, and return_page_source true, then list the canonical and meta description tags found

Key Endpoints

11 endpoints — the capturekit api captures webpages as png, jpeg, webp, or pdf screenshots and extracts their content for agents and automation.

METHOD

PATH

DESCRIPTION

GET

/v1/capture

Capture a screenshot or PDF

GET

/v1/content

Extract page content, metadata, and links

GET

/v1/analyze

AI analysis of a webpage

GET

/v1/website/crawler

Fetch raw HTML

GET

/v1/usage

Usage and credit balance

GET

/v1/jobs/{id}

Poll an asynchronous job

GET

/v1/capture

Capture a screenshot or PDF

GET

/v1/content

Extract page content, metadata, and links

GET

/v1/analyze

AI analysis of a webpage

GET

/v1/website/crawler

Fetch raw HTML

GET

/v1/usage

Usage and credit balance

GET

/v1/jobs/{id}

Poll an asynchronous job

Why Jentic?

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

Setup

Wiring CaptureKit by hand means sending the x-api-key header, choosing among dozens of capture options per request, and polling async jobs when a capture runs in the background. Through Jentic you install once, import CaptureKit from the API Directory, store the key once, and your agent calls it.

Permission scoping

CaptureKit puts each tool in its own URL path (/v1/capture, /v1/content, /v1/analyze), so a rule can limit your agent to the tools it needs. The target page travels as a url parameter, so rules bound which operations your agent may call, not which websites it visits.

Credential isolation

Your CaptureKit 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 'take a screenshot of a webpage' or 'get the markdown of a page', and Jentic returns the matching CaptureKit operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using CaptureKit API Reference API through Jentic.

What authentication does the CaptureKit API use?

The CaptureKit API authenticates with an API key in the `x-api-key` request header, declared as the ApiKeyAuth scheme in its OpenAPI spec. The capture endpoint also accepts optional s3_access_key_id and s3_secret_key values when you want screenshots uploaded to your own bucket. Through Jentic the CaptureKit key is held by your own Jentic One instance and attached at call time.

Can I take a mobile screenshot with the CaptureKit API?

Yes. GET /v1/capture takes a device parameter with emulated devices such as iphone_14_pro, galaxy_s23, and huawei_p60_pro, plus viewport_width, viewport_height, and scale_factor for custom sizes. Set full_page to capture the whole page and format to png, jpeg, webp, or pdf.

What is the difference between the Content and Website Crawler endpoints?

GET /v1/content loads the page and returns structured data: metadata and links, plus HTML, Markdown, and the sitemap when you ask for them, with options to remove ads and cookie banners first. GET /v1/website/crawler fetches raw HTML in request mode without rendering, which is faster but does not run the page's scripts.

What are the rate limits for the CaptureKit API?

The OpenAPI spec does not specify rate limits. It does describe credit pricing per call and a GET /v1/usage endpoint for your balance; check the CaptureKit documentation at https://capturekit.dev for current limits.

How do I screenshot a page through Jentic?

Search Jentic for 'take a screenshot of a webpage', load the GET /v1/capture operation, and execute it with url, format, and full_page. Add remove_cookie_banners to get a clean capture. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a CaptureKit MCP server?

You don't need an MCP server to give your agent CaptureKit. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the capture, content, and analyze operations on demand without extra tool definitions loaded into its context.

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

Yes. For an agent that only reads pages, write a rule that allows GET /v1/content and GET /v1/website/crawler. The agent can then fetch page content and HTML but cannot take screenshots, run AI analysis, or push files to S3, and each call it makes is logged.

CaptureKit API Reference

AI ReadinessFoundational (C+)57/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaImage ProcessingapiKey11 EndpointsREST

For Agents

Screenshot any webpage to PNG, JPEG, WebP, or PDF, extract its Markdown, HTML, metadata, and links, or get an AI summary of what the page offers.

Use for: Take a full-page screenshot of https://example.com as a PNG, Get the Markdown content of a blog post URL, I want a mobile screenshot of my landing page on an iPhone 14 Pro, Summarise what a company's homepage says it offers

Not supported: Does not host websites, edit images after capture, or crawl whole sites link by link. Use for single-page screenshots, content extraction, and AI page analysis only.

The CaptureKit API captures webpages as PNG, JPEG, WebP, or PDF screenshots and extracts their content for agents and automation. Screenshots can emulate a phone or tablet device, capture the full page or a single selector, hide cookie banners and ads, and upload straight to S3-compatible storage. The Content endpoint returns a page's metadata, links, HTML, Markdown, and optional sitemap, while the Analyze endpoint returns an AI summary with value proposition, features, categories, and use cases. A request-mode Website Crawler fetches raw HTML without rendering for fast audits and monitoring.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4

82%

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

12%

Example Density

How richly the API is illustrated with examples.

71%

Example Validity

Percentage of examples that conform to their schemas.

75%

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

53%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

82%

OperationId Quality

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

18%

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: B+Signals: 1

69%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the CaptureKit API Reference to your agent

Capabilities

Start building with CaptureKit API Reference API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

CaptureKit API Reference

Jentic AI Readiness Score

CaptureKit API Reference

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