Install Jentic One Beta

Connect the ezeep Blue Printing API to your agent

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

Retrieve the configuration and printer list for the current user via /GetConfiguration

Inspect printer-specific options and trays through /GetPrinterProperties

Request a presigned upload location with /PrepareUpload before transmitting the document

GET STARTED

Start building with ezeep Blue Printing API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use ezeep Blue Printing API for, with concrete tasks.

★ Cloud Print from a Web App

Add print-from-anywhere functionality to a web application by chaining the six ezeep Blue endpoints: pull the user's configuration, fetch printer properties, prepare an upload, send the bytes, dispatch the print, and poll for status. The pattern works for PDF and other supported document formats and avoids the need to install printer drivers on user devices.

Call /GetConfiguration to find the printer id, /PrepareUpload then /Upload for the PDF bytes, /Print with the printer id and document reference, then poll /Status until completion.

Server-Side Document Dispatch

Print invoices, shipping labels, or reports generated by a backend service through ezeep Blue without needing local print queues. The OAuth 2.0 client credentials flow yields an access token, which the server uses with /PrepareUpload, /Upload and /Print to deliver each document. Status is polled via /Status to surface errors back to the originating workflow.

After generating an invoice PDF, POST it to /PrepareUpload then /Upload, call /Print referencing the office printer, and poll /Status until succeeded.

Printer Discovery for an Onboarding UI

Build an onboarding screen that lists the user's available printers and the supported options for each using /GetConfiguration and /GetPrinterProperties. Useful for SaaS apps that need users to pick a default printer and paper size before submitting their first job, without installing local drivers or CUPS on each device.

Call /GetConfiguration to enumerate printers, then /GetPrinterProperties for each printer id to list the supported paper sizes for the onboarding screen.

Agent-Driven Print Jobs via Jentic

An AI agent that produces documents on a user's behalf can use Jentic to discover and chain the ezeep Blue endpoints rather than embedding the upload-and-print logic. The OAuth 2.0 token stays in your Jentic One instance, so the agent never sees the long-lived client secret while it submits jobs to the user's printer fleet.

Through Jentic, search 'submit a print job to ezeep Blue', load /PrepareUpload, /Upload and /Print, and execute them with the generated PDF and chosen printer id.

Key Endpoints

6 endpoints — jentic publishes the only available openapi specification for ezeep blue printing api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/GetConfiguration

Retrieve the user's configuration and printer list

POST

/GetPrinterProperties

Inspect a printer's supported options

POST

/PrepareUpload

Get a presigned upload location for the document

POST

/Upload

Upload the document bytes

POST

/Print

Dispatch a print job for an uploaded document

POST

/Status

Poll the status of a print job

POST

/GetConfiguration

Retrieve the user's configuration and printer list

POST

/GetPrinterProperties

Inspect a printer's supported options

POST

/PrepareUpload

Get a presigned upload location for the document

POST

/Upload

Upload the document bytes

POST

/Print

Dispatch a print job for an uploaded document

Why Jentic?

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

Setup

Wiring the ezeep Blue Printing API by hand means running its OAuth 2.0 flow, targeting the printapi.ezeep.com/sfapi host, and ordering the prepare-upload-print calls yourself. Through Jentic you install once, import the ezeep Blue Printing API from the API Directory, store the OAuth credential once, and your agent calls it.

Permission scoping

ezeep carries print details in the request body of its POST operations rather than a resource id in the path, so you limit the agent to the operations it needs, such as PrepareUpload, Upload, Print, and Status. You choose those operations, so configuration or printer-property calls are not included unless you add them.

Credential isolation

Your ezeep OAuth 2.0 credential is stored once, encrypted, by your own Jentic One instance and supplied as a Bearer header at execution time. The long-lived client secret never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'submit a print job to ezeep Blue' or 'check print status', and Jentic returns the /Print operation alongside the prerequisite /PrepareUpload and /Upload calls with their schemas so the agent calls the right endpoints without browsing the reference docs.

FAQs

Specific to using ezeep Blue Printing API through Jentic.

Why is there no official OpenAPI spec for ezeep Blue Printing API?

ezeep does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ezeep Blue Printing 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 ezeep Blue Printing API use?

The spec declares OAuth 2.0 with an implicit flow; in production ezeep also supports authorisation-code and client-credentials flows. Through Jentic the access token is stored in the vault and supplied as a Bearer header to /Print, /Upload and /Status without ever entering the agent context.

Can I print a PDF through the ezeep Blue Printing API?

Yes. Call /PrepareUpload to receive an upload location, send the PDF bytes to /Upload, then call /Print with the printer id and the upload reference; poll /Status to confirm the job completed.

How do I list available printers?

Call /GetConfiguration to retrieve the user's configuration including the printer list, then call /GetPrinterProperties for each printer id to inspect the supported options.

How do I submit a print job through Jentic?

Run pip install jentic, search 'submit a print job to ezeep Blue', load the /PrepareUpload, /Upload and /Print operations, and execute them in sequence; Jentic injects the OAuth 2.0 access token from the vault automatically.

What are the rate limits for the ezeep Blue Printing API?

The spec does not document explicit rate limits, so respect any 429 responses with backoff and stagger high-volume submissions across multiple printers when running batch print runs.

Can I limit what my agent is allowed to do with the ezeep Blue Printing API?

Yes. Because you run Jentic One yourself, your own rules decide which ezeep Blue operations and credentials the agent may use. ezeep carries print details in the POST request body rather than a resource id in the path, so you scope access by granting only the operations the job needs, such as PrepareUpload, Upload, Print, and Status. Since you pick those operations, GetConfiguration and GetPrinterProperties calls stay out of reach unless you explicitly add them.

ezeep Blue Printing API

Name: ezeep Blue Printing API
Brand: ezeep Blue Printing API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticProductivityCollaborationoauth26 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Submit print jobs to the ezeep Blue cloud-printing platform by discovering printers, uploading documents, and dispatching prints across six endpoints with OAuth 2.0.

Use for: I need to send a PDF to my office printer, List the printers available to my ezeep account, Get the supported paper sizes for a specific printer, Upload a document so it can be printed

Not supported: Does not handle scanning, fax delivery, or fleet-wide printer provisioning - use for cloud print job submission and status tracking only.

Jentic publishes the only available OpenAPI specification for ezeep Blue Printing API, keeping it validated and agent-ready. ezeep Blue is a cloud printing platform, and the API exposes the print pipeline used by client applications: discover printers and printer properties, request an upload URL for the document, upload the file, dispatch the print job, and poll for status. Authentication is OAuth 2.0, and the surface is intentionally small so that a print-from-anywhere workflow can be wired up against six endpoints.

Jentic One on Github View OpenAPI Document

Connect the ezeep Blue Printing API to your agent

Capabilities

Start building with ezeep Blue Printing API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

ezeep Blue Printing API