canonical: https://jentic.com/apis/pdflayer.com/pdflayer # pdflayer API The pdflayer API converts HTML and hosted web pages into PDF documents through a single convert operation offered as a GET or a POST. It accepts a document URL or a raw HTML body, lets you name the output file, and applies rendering options such as page size, orientation, and margins. The result is a ready-to-store PDF returned from one stateless call, so no rendering engine runs on your side. ## For AI agents Convert a URL or raw HTML into a PDF document in one call, with control over the output file name and page layout. Authenticates with an access key. ## Scope Does not handle PDF editing, e-signatures, or OCR text extraction. Use for HTML and URL to PDF conversion only. ## Capabilities - Convert a hosted web page to PDF by passing its URL - Render a raw HTML body into a PDF document - Name the generated PDF file - Apply rendering options such as page size, orientation, and margins ## Use cases ### AI Agent Document Generation An AI agent producing invoices, reports, or receipts can turn a URL or an HTML string into a PDF through Jentic. The agent searches for the convert operation, passes the document URL or HTML and any rendering options, and receives the PDF, without the developer wiring the access key or reading the pdflayer reference docs. Example prompt: Call POST /convert with the invoice HTML in the request body to render a PDF ### Web Page Archiving Compliance and records tools capture how a page looked at a point in time. The convert operation accepts a page URL and returns a PDF snapshot, so an agent can archive a terms page, an order confirmation, or a dashboard as a fixed document. Example prompt: Call GET /convert with a document URL to render the page as a PDF ### Batch Report Rendering Reporting pipelines render many documents on a schedule. Because the convert operation is a single stateless call that accepts either a URL or an HTML body, an agent can loop over a set of inputs and produce a PDF for each without managing a rendering engine itself. Example prompt: Call POST /convert for each report's HTML to render a batch of PDFs ## Key resources - **Convert** — HTML-to-PDF and URL-to-PDF conversion with output and layout options ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 45 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 80 / 100 - AI-Readiness & Agent Experience: 48 / 100 - Agent Usability: 94 / 100 - Security: 15 / 100 - AI Discoverability: 31 / 100 - **View full report:** https://jentic.com/apis/pdflayer.com/pdflayer/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the pdflayer API by hand means appending your access key to every request as a query parameter and tuning the rendering options for each document. Through Jentic you install once, import pdflayer from the API Directory, store the access key once, and your agent calls it. - **Permission scoping:** pdflayer has one operation exposed as a GET and a POST, so a rule can bound your agent to just the convert call it needs. You choose that set, so the agent renders documents but cannot reach anything else. - **Credential handling:** Your pdflayer access 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. - **Discovery method:** Agents search Jentic by intent such as 'convert a web page to PDF' or 'render HTML to PDF', and Jentic returns the matching pdflayer operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Presalytics Converter** — Document conversion between office and PDF formats - **Urlbox** — Render URLs to screenshots and PDFs - **apilayer** — Marketplace of data APIs from the same provider family ## FAQ ### What authentication does the pdflayer API use? The pdflayer API authenticates with an access key passed as the `access_key` query parameter, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt, logs, or context. ### Can I convert raw HTML to PDF with the pdflayer API? Yes. The POST convert operation accepts a raw HTML body and returns the rendered PDF, and the GET convert operation does the same for a hosted page URL. You can name the output file and set layout options such as page size and orientation on the request. ### What are the rate limits for the pdflayer API? The OpenAPI spec does not specify rate limits; your monthly conversion allowance depends on your subscription. Current limits are published in the vendor documentation at https://pdflayer.com/documentation. ### How do I generate a PDF with the pdflayer API through Jentic? Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import pdflayer from the API Directory, and store your access key once. Your agent then searches for an intent such as 'convert a web page to PDF', and Jentic returns the matching operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Is there a pdflayer MCP server? You do not need an MCP server to give your agent the pdflayer API. Jentic connects it directly from the API Directory: import the API, store your key once, and your agent calls the convert operation on demand, which keeps your agent's context free of an extra server's tool definitions. ### Can I limit what my agent is allowed to do with the pdflayer API? Yes. pdflayer exposes a single convert operation in two methods, so a rule can allow your agent just the method it uses, such as the POST convert for HTML input, and nothing else. Because you run Jentic One yourself, the agent can render PDFs but holds no other access, and every call is logged.