Pricing

Pay per call. Nothing else.

Prepaid credits, charged per successful call. No subscription, no minimum spend, and credits never expire. Every endpoint price is published with the reason behind it.

Start free

50 credits when you create an account, then 100 more on the 1st of every month. No card required.

Sign in / Sign up with GoogleSign in / Sign up
Browse endpoints

Credit packs

Buy once, use whenever

One-off packs that stack with your monthly allowance. Bigger packs cost less per credit.

Starter

$5

800+200bonus

= 1,000 credits in total

0.50¢ per credit

1,000 credits. Good for a personal agent or an occasional script.

Buy in billing

Scale

$80

25,000 credits

0.32¢ per credit

25,000 credits at the lowest rate we offer. For automated workloads running continuously.

Buy in billing

Payment is handled securely by Polar. Credits land on your balance as soon as the payment is confirmed.

Price list

What each endpoint costs

Prices track real work, not a flat average - a cached DNS answer does not subsidise a crawl that makes thirty requests.

EndpointCategoryCreditsWhy
dns-lookupDNS LookupNetwork & DNS1 One DNS query, answered in milliseconds and served from cache when the record is still fresh. This is the cheapest class of call on the platform.
ip-lookupIP Address LookupNetwork & DNS1 One cached lookup against a geolocation dataset. Repeat lookups of the same address inside the cache window cost us nothing extra.
reverse-ipReverse IP LookupNetwork & DNS1 A single reverse DNS query - the same cost profile as a forward lookup.
hash-textHash TextHashing & Passwords1 Pure CPU, measured in microseconds, with no outbound call. Priced at the platform floor.
qr-generateQR Code GeneratorData & Utility1 Pure CPU image generation, a few milliseconds, with no outbound call.
currency-ratesCurrency Exchange RatesData & Utility1 Served from a shared cache that is refreshed on a schedule rather than per call, so an individual request is close to free for us.
gold-priceGold & Silver PriceData & Utility1 One or two cached outbound lookups - the one-credit floor.
ssl-checkSSL Certificate CheckNetwork & DNS2 Requires a real TLS handshake with the target host, which costs a round trip and some CPU for certificate parsing - a few times the work of a cached DNS answer.
http-requestHTTP RequestWeb & HTTP2 One outbound request to a host we do not control, held open until it answers or times out. Priced above a DNS query because the response body must be read and buffered.
redirect-chainRedirect Chain TracerWeb & HTTP2 Makes one request per hop rather than a single fetch. Most chains are one to three hops, so this is priced as a small multiple of a plain request.
seo-metaSEO Meta Tag ExtractorSEO & Content2 One page fetch plus parsing. The parse is pure CPU and negligible; the cost is the outbound request and reading the HTML.
bcrypt-hashBCrypt HashHashing & Passwords2 BCrypt is deliberately expensive by design: a work factor of 11 is roughly a tenth of a second of dedicated CPU. Priced above a plain digest because that CPU time is the entire point of the algorithm.
bcrypt-verifyBCrypt VerifyHashing & Passwords2 Verification runs the same deliberately slow key derivation as hashing, at whatever work factor is embedded in the supplied hash.
pdf-metadataPDF Metadata ReaderDocuments2 Parses only the PDF's header and information dictionary rather than rendering pages, but the file still has to be uploaded and read, which is why it sits above the one-credit floor.
pingPing HostNetwork & DNS2 Holds a socket open for a few seconds per run - more than a DNS lookup, far less than a browser.
watermark-imageWatermark ImageImages2 One download plus a pure-CPU raster pass - cheap, but it moves bytes.
argon2-hashArgon2 HashHashing & Passwords3 Argon2id is memory-hard: each call allocates and works over a sizeable block of RAM, so it consumes both CPU and memory that cannot be shared with other requests. It is the most expensive pure-CPU tool here.
argon2-verifyArgon2 VerifyHashing & Passwords3 Runs the same memory-hard derivation as hashing, at the parameters embedded in the supplied hash.
smtp-testSMTP Server TestNetwork & DNS3 A multi-step protocol session with a TLS handshake, held open for several seconds.
web-scrapeWeb Page ScraperWeb & HTTP3 Downloads and parses a whole page, which is several times the work of a metadata-only fetch.
broken-linksBroken Link CheckerWeb & HTTP10 Fetches the page and then up to 30 more URLs, five at a time - about 31 outbound requests for a single call. Priced to reflect that fan-out. Lower maxLinks when you only need a spot check; the price is flat, so a smaller crawl is simply better value per link.
word-to-pdfWord to PDFDocuments15 Spins LibreOffice on a worker for several seconds per file, which is far more compute than a DNS lookup. Priced so a loop of conversions cannot quietly drain the worker.
ppt-to-pdfPowerPoint to PDFDocuments15 Same LibreOffice worker cost as Word to PDF - one deck, several seconds of CPU.
pdf-to-wordPDF to WordDocuments20 Layout-preserving PDF reconstruction is heavier than Office-to-PDF and is capped by page count on the worker.
pdf-to-excelPDF to ExcelDocuments20 Table extraction walks every page and builds a workbook - similar worker time to PDF-to-Word.
pdf-to-pptPDF to PowerPointDocuments20 Each page becomes a slide, so worker time scales with page count like the other PDF-to-Office tools.
remove-backgroundRemove BackgroundImages25 Runs an ONNX segmentation model on the worker. That is GPU/CPU-heavy compared with hashing or DNS, so it sits well above the one-credit floor.
website-screenshotWebsite ScreenshotImages25 Every call starts and tears down a headless Chromium instance, which is an order of magnitude heavier than an HTTP fetch.
html-to-imageHTML to ImageImages25 Identical work to a URL capture: one headless Chromium instance per call.
image-upscaleAI Image UpscaleImages30 Real-ESRGAN is the heaviest synchronous job in the catalogue. One call can occupy the worker for tens of seconds.

The rules

What you are charged for

Successful calls cost the endpoint’s listed price.

Invalid requests are free. If your arguments fail validation, nothing is charged - the call never runs.

Our failures are refunded. A timeout or fault on our side is credited straight back and shown on your statement.

Your target’s failures are charged. If you point a tool at a host that is down, we still did the work of trying.

Every call returns your balance in the X-Credits-Remaining header, so you can track spend without a second request.