REST API for Developer Tool Pricing

Free, open, and ready to use. No API key, no signup, and no rate limits on the read endpoints. Query 1,493+ deals across 60 categories with plain HTTP requests.

Quick Start

Three examples to get you started. Every endpoint returns JSON.

Endpoint Reference

Every endpoint below is read-only (GET) except the 1 marked POST in the Method column. Responses are JSON. Every one of them is described in our OpenAPI document, browsable as interactive Swagger documentation.

Full OpenAPI 3.0 spec: /api/openapi.json · Interactive docs: Swagger UI

Paging on /api/changes

/api/changes returns 20 records by default. limit sets the page size, offset skips records, and both are echoed back on the response alongside returned — the count in this page — and total, the count matching your query before paging. There is no maximum: ?limit=1000 returns the whole window in one response. An invalid limit or a negative offset answers 400 rather than being ignored.

Records we have withdrawn as our own error are not served here, and total counts what you received rather than what the log holds. retracted_excluded reports how many your query matched and we held back. ?include_retracted=true returns them alongside the rest, each carrying standing: "retracted" and impact: "none" — and every record carries a standing, so a live record and a withdrawn one are told apart without a null check. A value other than true or false answers 400.

Our own index housekeeping is not served here either. These records say we stopped listing an offer of ours because the page we imported it from stopped resolving — the vendor's terms did not move — so counting them as vendor activity overstates it. They carry reports: "our_index", index_housekeeping_excluded reports how many your query matched and we held back, and ?include_index_housekeeping=true returns them alongside the rest. A value other than true or false answers 400. This is why ?type=product_deprecated and the same count taken off the whole log agree: both leave them out.

The window behind a count

With no filter, /api/changes returns the last 30 days. Name a type, vendor, vendors or category and you are answered from the whole change log however old the record — a vendor you ask for by name is never reported as having changed nothing because the last thing it changed was six months ago. since overrides both. Every response carries date_window naming which of the three ran and the date it opens on, so a total of 0 can be read as "we hold no such record" rather than guessed at.

Referral Codes

Every code these endpoints return is one we hold ourselves and earn a commission on, with the reader benefit and every restriction attached to it. We hold codes for a handful of the vendors we cover; the affiliate disclosure lists the same set. Agent-submitted codes are retired — ?source=agent answers with an empty list and the reason, and POST /api/referral-codes answers 410.

Referral codes are also inlined on every /api/offers, /api/compare, /api/details/:vendor, and /api/newest result as a referral_code field (null if no code available) — so agents get codes without a second call.

List all active codes

Filter by vendor category

Look up a single vendor

Python

JavaScript

Use Cases

Response Format

All responses return JSON with consistent structure. Offers include vendor name, category, description, tier, URL, tags, verification date, and stability indicators.

Provenance

Every response that carries index data includes a _provenance object, so an agent can attribute a figure without parsing prose out of a sentence.

Operational endpoints — /api/stats, /api/traffic, /api/query-log, /api/pageviews and /api/freshness — carry no provenance block. They report on this service rather than on the index.

If you use a figure, cite url and checked. The index is free and we keep it current; attribution is how the people who need it find their way here.

Rate Limits

The read endpoints above have no rate limits. We trust developers to be reasonable.

One write path is limited. The attribution beacon at /api/signal allows 60 per minute — its own page covers how that limit is keyed. Over the limit you get a 429 with Retry-After.

Related Resources

Swagger UI (Interactive Docs) · OpenAPI Spec (JSON) · MCP Server Setup · State of Free Tiers Report · Vendor Stability Dashboard · Weekly Digest · Subscribe via RSS · Embeddable Badges · GitHub