canonical: https://jentic.com/apis/api-snap.com/api-snap # API Snap The API Snap API bundles more than a dozen common developer utilities behind a single key, with the heaviest tools generating visual and document output: capturing web page screenshots, converting HTML to PDF, resizing and converting images, and producing QR codes and placeholder images. It also extracts Open Graph and URL metadata and offers lightweight helpers for hashing, UUID generation, Base64, JWT decoding, colour conversion, Markdown rendering, and lorem ipsum. Endpoints return JSON or binary output depending on the tool. ## For AI agents Capture screenshots, convert HTML to PDF, resize images, generate QR codes, and run encoding and metadata utilities through one API Snap key. ## Scope Does not host files, run scheduled jobs, or store generated assets. Use for on-demand developer utilities such as screenshots, PDF, image, QR, and encoding tools only. ## Capabilities - Capture a screenshot of a web page - Convert HTML to a PDF document - Resize and convert images between formats - Generate QR codes and placeholder images - Extract Open Graph and URL metadata from a page - Hash strings, decode JWTs, and encode or decode Base64 ## Use cases ### AI agent generating visual assets An agent assembling a report or message needs an image, a screenshot, or a QR code on demand. Through Jentic the agent searches for capturing a web page screenshot, loads the screenshot operation with the key already injected, and gets back the rendered image. The same key covers QR generation, image resizing, and placeholder images, so the agent produces several asset types without separate integrations. Example prompt: Call GET `/api/screenshot` for a URL, then GET `/api/qr` to produce a QR code linking to the same page ### HTML to PDF documents A workflow that produces invoices or summaries needs to turn rendered HTML into a downloadable PDF. The API Snap API converts posted HTML into a PDF document in one call, so an agent can generate the file without running a headless browser itself. This fits report generation steps where the agent already has the HTML. Example prompt: Call POST `/api/pdf` with the invoice HTML and return the generated PDF ### Link preview enrichment When an agent processes a list of URLs, it can pull the title, description, and Open Graph image for each to build link previews. The API Snap API extracts URL metadata and Open Graph tags from a page in a single call, giving the agent structured preview data without parsing the HTML. This supports chat link unfurling and content curation. Example prompt: Call GET `/api/meta` for each URL and return the title, description, and Open Graph image ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/screenshot` | Capture a web page screenshot | | POST | `/api/pdf` | Convert HTML to a PDF document | | POST | `/api/resize` | Resize and convert an image | | GET | `/api/qr` | Generate a QR code | | GET | `/api/meta` | Extract URL metadata and Open Graph tags | | GET | `/api/uuid` | Generate UUIDs and unique IDs | ## Key resources - **Visual and document tools** — Screenshot capture, HTML-to-PDF conversion, image resize, QR codes, and placeholder images - **Metadata** — Extract Open Graph and URL metadata from a page - **Encoding utilities** — Hash strings, decode JWTs, Base64 encode or decode, convert colours, render Markdown, and generate UUIDs ## 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:** 67 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 93 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 48 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 79 / 100 - **View full report:** https://jentic.com/apis/api-snap.com/api-snap/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 API Snap API by hand means managing one bearer key across more than a dozen separate tools, choosing whether to pass it as a header or a query parameter, and handling binary or JSON responses per endpoint. Through Jentic you install once, import API Snap from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** The API Snap API exposes each tool as its own operation, from screenshots and HTML-to-PDF to hashing and Base64. You choose the operations your agent may call, so you can allow just the screenshot and PDF tools and leave the rest of the bundle out unless you add them. - **Credential handling:** Your API Snap 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 'capture a screenshot' or 'convert HTML to PDF', and Jentic returns the matching API Snap operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **Urlbox API** — A dedicated website screenshot and rendering service with deeper capture options - **PDFEndpoint API** — A specialised HTML-to-PDF service for heavier document generation needs - **QRCode Monkey API** — A focused QR code generator with styling and logo options ## FAQ ### What authentication does the API Snap API use? The API Snap API uses a bearer key, sent either as Authorization: Bearer or as an api_key query parameter, per its OpenAPI spec. One key covers every tool in the bundle. Through Jentic the key is stored once and injected at call time, so the agent never handles it directly. ### Can I convert HTML to PDF with the API Snap API? Yes. Call POST `/api/pdf` with your HTML and the API returns a generated PDF document. The same key also drives GET `/api/screenshot` for page captures and POST `/api/resize` for image conversion. ### What are the rate limits for the API Snap API? The OpenAPI spec does not define request-rate ceilings. The service offers a free monthly tier before paid usage, so throughput depends on your plan rather than a fixed per-second cap. Check the API Snap documentation for the quota that applies to your key before running bulk screenshot or PDF jobs. ### Is there an API Snap MCP server? You don't need an MCP server to give your agent the API Snap API. Jentic connects it directly from the API Directory: import the API, store your key once, and your agent calls operations such as GET `/api/screenshot` on demand without loading another server's tool definitions into its context. ### Can I limit what my agent is allowed to do with the API Snap API? Yes. Write a rule that allows only the tools the agent needs, such as the screenshot and HTML-to-PDF operations, so it can render pages and documents but cannot call the other utilities in the bundle, and every call it makes is logged. You add more tools to the allowed set as you need them. ### How do I capture a web page screenshot through Jentic? Search Jentic for 'capture a web page screenshot', load the GET `/api/screenshot` operation, and run it after your key is stored. To run it on your own infrastructure, install Jentic One from its GitHub repo.