Install Jentic One Beta

Connect the Galley Render API to your agent

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

Render a template and JSON payload into a PDF, PNG, or JPG behind a signed URL

Render up to 50 documents in one batch request

Create templates and publish immutable, versioned revisions

Validate a JSON payload against a template's schema before rendering

Import an existing PDF and turn it into a reusable template

GET STARTED

Start building with Galley Render API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Galley Render API for, with concrete tasks.

★ AI Agent Document Rendering via Jentic

An AI agent reaches Galley Render through Jentic to produce a finished document without wiring the bearer key itself. It searches by intent, receives the matching operation and its input schema, and executes the render with the key injected at run time. Because renders are deterministic and cached, an agent that repeats the same request gets the stored file back at no extra charge.

Search Jentic for 'render a PDF from a template and JSON', load the POST /v1/render schema, and execute it with the key injected at run time

Templated Document Generation

An application turns structured data into a branded PDF such as an invoice, receipt, or certificate. Galley Render validates the JSON payload against the template's schema and then renders the document behind a signed URL. Because templates are immutable and versioned, a document rendered against version 3 stays reproducible even after a later version ships.

Call POST /v1/templates/{ref}/validate to check the payload, then POST /v1/render to produce the PDF behind a signed URL

Batch Rendering

A job produces many documents at once, such as a run of certificates or statements. Galley Render takes up to 50 items in a single batch request and renders each behind its own signed URL. The agent can then fetch a fresh signed URL for any output by its id when it is ready to deliver the file.

Call POST /v1/render/batch with up to 50 items, then GET /v1/renders/{id} to fetch a fresh signed URL for each output

PDF to Template Import

A team turns an existing PDF into a reusable, data-driven template. Galley Render starts an import from the uploaded document, asks clarifying questions about the variable fields, and saves the result as a template once the answers are in. From then on the team renders new documents from structured JSON instead of editing the original file.

Call POST /v1/imports to start an import from a PDF, POST /v1/imports/{id}/answers to answer its questions, then POST /v1/imports/{id}/save to save it as a template

Key Endpoints

32 endpoints — the galley render api turns a template and a json payload into a pdf, png, or jpg behind a signed url.

METHOD

PATH

DESCRIPTION

POST

/v1/render

Render a document from a template and JSON

POST

/v1/render/batch

Render up to 50 documents

GET

/v1/renders/{id}

Get a render and a fresh signed URL

GET

/v1/templates

List templates on the account

POST

/v1/templates

Create a template at version 1

POST

/v1/templates/{ref}/validate

Dry-run a payload against a template schema

POST

/v1/imports

Start turning an existing document into a template

GET

/v1/usage

Usage, cost, and limits for the current period

POST

/v1/render

Render a document from a template and JSON

POST

/v1/render/batch

Render up to 50 documents

GET

/v1/renders/{id}

Get a render and a fresh signed URL

GET

/v1/templates

List templates on the account

POST

/v1/templates

Create a template at version 1

POST

/v1/templates/{ref}/validate

Dry-run a payload against a template schema

POST

/v1/imports

Start turning an existing document into a template

GET

/v1/usage

Usage, cost, and limits for the current period

Why Jentic?

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

Setup

Wiring Galley Render by hand means sending the bearer key, deciding between synchronous and async or webhook jobs by payload size, and verifying the webhook signing secret yourself. Through Jentic you install once, import Galley Render from the API Directory, store the key once, and your agent calls it.

Permission scoping

A rule can confine your agent to the render operations and template reads it needs and keep it away from account operations, so it cannot mint or revoke keys, rotate the webhook secret, or set the spend cap. You choose which operations it may call, so destructive ones such as deleting a template are not included unless you add them.

Credential isolation

Your Galley Render 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 'render a PDF from a template' or 'validate a payload against a template', and Jentic returns the matching Galley Render operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Galley Render API through Jentic.

What authentication does the Galley Render API use?

The Galley Render API authenticates with an API key (a glr_sk_ string) sent as a Bearer token in the Authorization header, or in the X-API-Key header, per its OpenAPI spec. Most operations require the key, while a few public endpoints, such as the starter library and the health check, are open and need no credential. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.

What are the rate limits for the Galley Render API?

The OpenAPI spec does not specify request rate limits. The usage endpoint reports usage, cost, and limits for the current period, and an account spend cap bounds monthly spend, while identical repeat renders return the cached object and are not billed. See https://galleyrender.com/support for current limits.

Can I render a PDF with the Galley Render API?

Yes. POST /v1/render turns a template and a JSON payload into a PDF, PNG, or JPG behind a signed URL, and POST /v1/render/batch renders up to 50 documents at once. You can validate the payload against the template schema first with POST /v1/templates/{ref}/validate.

Is there a Galley Render MCP server?

You don't need an MCP server to give your agent Galley Render. Jentic connects it directly from the API Directory: import it and your agent calls the render, template, and import operations on demand, discovering each operation's schema when it needs it rather than loading a separate server's tool definitions into context.

How do I render a document with the Galley Render API through Jentic?

Search Jentic for 'render a PDF from a template and JSON', and it returns the Galley Render operation with its input schema. Load it and execute POST /v1/render with the key injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. Write a rule that allows only the render operations and template reads a task needs, so the agent can produce documents but cannot mint or revoke keys, rotate the webhook secret, set the spend cap, or delete a template. Because every call runs through your own instance, each one is logged for you to review.

Galley Render API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaImage Processingbearer32 EndpointsREST

For Agents

Render a template plus a JSON payload into a PDF, PNG, or JPG behind a signed URL, singly or in batches of up to 50. Templates are versioned and validatable, and operations use a bearer API key.

Use for: Render an invoice PDF from a template and JSON data, Create a template and publish a new version, Validate my payload against a template schema, List the recent renders on my account

Not supported: Does not handle long-term file hosting, e-signature, or document storage beyond cached renders. Use for rendering templates into PDF, PNG, and JPG files only.

The Galley Render API turns a template and a JSON payload into a PDF, PNG, or JPG behind a signed URL. Renders are deterministic and cached on a SHA-256 key over the template version checksum, the output format, and the canonical JSON, so an identical repeat request returns the stored object and is not billed. Small jobs finish inside the request and return a URL, while large, batch, async, or webhook jobs run in the background. Templates are versioned and immutable, payloads can be validated against a template schema before rendering, and existing PDFs can be imported and turned into reusable templates.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 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).

21%

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

11%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

58%

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

41%

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.

61%

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

55%

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

74%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Galley Render API to your agent

Capabilities

Start building with Galley Render API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Galley Render API

Jentic AI Readiness Score

Galley Render 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