Install Jentic One Beta

Connect the Restpack API to your agent

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

Capture screenshot via request body

Get screenshot API usage statistics

Convert to PDF via request body

Query and filter Restpack API records by parameters

Monitor Restpack API operational status and events

GET STARTED

Start building with Restpack API

Explore with Jentic One

View OpenAPI Document

Automated Screenshot Management

Automate screenshot operations by combining multiple Restpack API endpoints. Agents can capture screenshot via query parameters and then get screenshot API usage statistics in a single workflow.

Call GET /screenshot/v7/capture to capture screenshot via query parameters, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Restpack API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'capture screenshot via request body', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

6 endpoints — restful microservices for screenshot capture and html to pdf conversion.

METHOD

PATH

DESCRIPTION

POST

/screenshot/v7/capture

Capture screenshot via request body

GET

/screenshot/v7/capture

Capture screenshot via query parameters

GET

/screenshot/v7/usage

Get screenshot API usage statistics

POST

/html2pdf/v7/convert

Convert to PDF via request body

GET

/html2pdf/v7/convert

Convert to PDF via query parameters

GET

/html2pdf/v7/usage

Get HTML to PDF API usage statistics

POST

/screenshot/v7/capture

Capture screenshot via request body

GET

/screenshot/v7/capture

Capture screenshot via query parameters

GET

/screenshot/v7/usage

Get screenshot API usage statistics

POST

/html2pdf/v7/convert

Convert to PDF via request body

GET

/html2pdf/v7/convert

Convert to PDF via query parameters

GET

/html2pdf/v7/usage

Get HTML to PDF API usage statistics

Why Jentic?

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

Setup

Wiring the Restpack API by hand means passing your API key, targeting the restpack.io/api host, and driving screenshot and HTML-to-PDF conversions yourself. Through Jentic you install once, import Restpack API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Restpack API takes the target URL and options in the request body rather than a resource id in the URL path. Limit the agent to the operations it needs, such as capturing a screenshot or converting HTML to PDF, so it works within the operations you approve.

Credential isolation

Your Restpack 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 'capture a screenshot of a page' or 'convert HTML to PDF', and Jentic returns the matching Restpack API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Restpack API through Jentic.

What authentication does the Restpack API use?

The Restpack API uses an API key passed in the `X-Access-Token` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I capture screenshot via request body with the Restpack API?

Yes. Use the POST /screenshot/v7/capture endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Restpack API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I capture screenshot via request body through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'capture screenshot via request body'. Jentic returns the matching Restpack API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Restpack API have?

The Restpack API exposes 6 endpoints covering screenshot, html to pdf operations.

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

Yes. Because Jentic One is self-hosted and its rules are set by you, you decide which Restpack operations the agent may call. You can allow only screenshot capture (POST or GET /screenshot/v7/capture) while blocking HTML-to-PDF conversion (/html2pdf/v7/convert), or restrict it to usage-statistics reads. Since Restpack takes the target URL and options in the request body rather than a resource id in the path, the agent works only within the operations and stored API key you approve.

Restpack API

Name: Restpack API
Brand: Restpack API
Availability: InStock

AI ReadinessAI-Aware (B-)62/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey6 EndpointsREST

For Agents

Programmatically capture screenshot via request body, capture screenshot via query parameters. Covers 6 operations with apiKey authentication.

Use for: I need to capture screenshot via request body, I want to capture screenshot via query parameters, Search for screenshot API usage statistics, Find all convert to pdf via request body

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

RESTful microservices for screenshot capture and HTML to PDF conversion. Provides Screenshot API (v7) for capturing webpage screenshots and HTML to PDF API (v7) for converting web content to PDF documents. The API exposes 6 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

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

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

93%

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

56%

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.

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

33%

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: ASignals: 1

83%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Restpack API to your agent

Capabilities

Start building with Restpack API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Restpack API

Jentic AI Readiness Score

Restpack 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