Install Jentic One Beta

Connect the PrexView API to your agent

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

Generate PDF documents from JSON or XML data using pre-defined templates

Render HTML output from structured data with dynamic value substitution

Produce PNG and JPG image outputs from template-based document rendering

Substitute values dynamically using JSON path syntax within templates

Support multiple output formats from a single template definition

GET STARTED

Start building with PrexView API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use PrexView API for, with concrete tasks.

★ Invoice and Receipt Generation

Generate professional PDF invoices and receipts from structured JSON data containing line items, totals, customer details, and tax information. PrexView applies a pre-designed template with dynamic value substitution to produce pixel-perfect documents ready for email delivery or archival. This replaces manual document composition with a single API call that accepts data and returns a rendered PDF.

Submit a JSON payload with invoice line items, customer name, and total to the /transform endpoint with output format set to PDF and retrieve the generated invoice document

Report and Certificate Rendering

Render formatted reports, certificates, or compliance documents from structured data sources. PrexView supports multiple output formats (PDF, HTML, PNG, JPG) from the same template, enabling both web display and print-ready output from a single data submission. The JSON path substitution syntax allows complex nested data to map to any position in the template layout.

Send XML data representing a compliance report to the /transform endpoint requesting HTML output, then re-request with PDF format for a printable version

AI Agent Document Production

AI agents use PrexView through Jentic to produce formatted documents as part of larger automation pipelines. The agent collects or generates structured data, searches Jentic for document transformation operations, loads the transform endpoint schema, and produces PDF or image output without managing template rendering infrastructure. This enables agents to generate customer-facing documents on demand.

Search Jentic for 'generate PDF from JSON template', load the transform operation schema, and execute with sample invoice data to produce a PDF document

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for prexview api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/transform

Transform data into a document using a template

POST

/transform

Transform data into a document using a template

Why Jentic?

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

Setup

Wiring PrexView by hand means setting its API key on the Authorization header, targeting api.prexview.com/v1, and shaping the transform payload with data, template, and output format yourself. Through Jentic you install once, import PrexView from the API Directory, store the key once, and your agent calls it.

Permission scoping

PrexView exposes a single transform operation with no resource id in the URL path, so scope the agent by operations: allow it the transform call it needs and nothing more. You choose the operations it may call, so it only runs the document generation you permit.

Credential isolation

Your PrexView 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 'generate a PDF from JSON data', and Jentic returns the PrexView transform operation with its input schema showing data format, template reference, and output options so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using PrexView API through Jentic.

Why is there no official OpenAPI spec for PrexView API?

PrexView does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call PrexView API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the PrexView API use?

The PrexView API uses API key authentication passed in the Authorization header. You obtain your API key from the PrexView account dashboard. Through Jentic, this key is stored encrypted in your Jentic One instance and agents receive requests with the Authorization header pre-configured.

What output formats does PrexView support?

The /transform endpoint supports four output formats: PDF for print-ready documents, HTML for web display, and PNG or JPG for image outputs. You specify the desired format in your request along with the data and template reference.

What are the rate limits for the PrexView API?

Rate limits depend on your PrexView subscription tier. The API processes document transformations synchronously, so throughput scales with your plan. For high-volume generation, queue requests client-side and process sequentially to avoid exceeding your plan limits.

How do I generate a PDF from JSON data through Jentic?

Install the SDK with pip install jentic, set your JENTIC_AGENT_API_KEY, then search for 'generate PDF from JSON template'. Jentic returns the /transform operation schema showing required fields: input data (JSON or XML), template reference, and output format. Execute to receive the generated document.

Does PrexView support dynamic value substitution in templates?

Yes. Templates use JSON path syntax to reference values from your input data. When you submit JSON or XML data to the /transform endpoint, the engine resolves all path expressions in the template against your data, inserting values at the designated positions in the rendered output.

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

Yes. Because you run Jentic One yourself, your own rules decide which PrexView operations and credentials your agent may use. PrexView exposes a single transform operation with no resource id in the path, so you scope the agent by operation: grant it only the /transform call that turns your JSON or XML data into a PDF, HTML, PNG, or JPG document, and withhold anything else. Your PrexView API key stays with your instance and is attached only when the agent runs the transform calls you have permitted.

PrexView API

Name: PrexView API
Brand: PrexView API
Availability: InStock

AI ReadinessAI-Aware (B+)67/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticDeveloper ToolsTesting QaapiKey1 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Transform XML or JSON data into PDF, HTML, PNG, or JPG documents using customizable templates with dynamic value substitution.

Use for: I need to generate a PDF invoice from JSON data, I want to render an HTML report from structured data, Transform XML data into a formatted PDF document, Generate a PNG image of a certificate from template data

Not supported: Does not handle template design, document signing, or file storage - use for data-to-document transformation only.

Jentic publishes the only available OpenAPI specification for PrexView API, keeping it validated and agent-ready. PrexView transforms XML or JSON data into high-quality documents in PDF, HTML, PNG, or JPG format using customizable templates with dynamic value substitution via JSON path syntax. The single /transform endpoint accepts structured data and a template reference, producing rendered output in the requested format for invoices, reports, certificates, or any templated document.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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.

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

62%

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.

50%

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

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the PrexView API to your agent

Capabilities

Start building with PrexView API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

PrexView API

Jentic AI Readiness Score

PrexView 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