Skip to main content
PocketUtils is a collection of REST APIs for the web tasks that show up in almost every product: rendering a page as a screenshot or PDF, checking whether a site is up, scanning its meta tags or SSL certificate, extracting or auditing its links, and converting XBEL bookmark files. Every endpoint is billed in credits, not requests, and every endpoint is the exact same one that powers the free playground on each tool page — there’s no separate “production” implementation for your integration to drift out of sync with.

​
Base URL

Every endpoint is versioned and served from a dedicated API host:
Calling from a browser on pocketutils.com itself? The website proxies these same routes at /api/v1 on its own origin so tool pages never need CORS. Server-to-server integrations should call api.pocketutils.com directly.

​
Available APIs

Screenshot

Render a full-page PNG, WebP, or JPEG at any viewport. 2 credits

URL to PDF

Convert a live URL into a print-ready PDF document. 2 credits

Broken Link Checker

Crawl a site and return every dead link with its status. 2 credits

Meta Scanner

Parse title, description, Open Graph, and Twitter Card tags. 1 credit

SSL Scanner

Inspect the certificate chain, cipher suite, and expiry window. 1 credit

Down Checker

Report reachability, HTTP status, latency, and resolved IP. 1 credit

Link Extractor

Extract every link on a page or site, grouped by type. 1 credit

XBEL Decryptor

Decrypt a protected XBEL bookmark archive to plain XML. 1 credit

XBEL to HTML

Convert an XBEL archive into browser-importable HTML. 1 credit

Quota

Check the caller’s current credit balance. Free

​
How it works

1

Credits, not request counts

Every plan grants a pool of credits per billing cycle. A light endpoint — a fetch-and-parse lookup — costs 1 credit; a render endpoint — anything that boots headless Chromium or crawls more than one page — costs 2. A failed request is never billed: credits are only spent on a response that actually succeeds. See Rate Limits & Credits.
2

One implementation, three callers

The same handler serves a signed-out visitor on a tool page (a small daily allowance), a signed-in user browsing the site (their monthly plan credits via session cookie), and a subscriber calling with an API key. Only the credential and the billing ledger differ — see Authentication.

​
Next steps

Quickstart

Make your first API call in under five minutes.

Authentication

Create an API key and learn the three ways to call the API.

Rate Limits & Credits

Credit costs, plan limits, and the headers every response carries.

Errors

The error shape, status codes, and every error code you can get back.