Pricing data for developers and agents

Early access

Read dated, source-backed SaaS pricing from your own code, the command line or a local MCP server. Keys come from your account while self-service sign-in is open, or with a pilot credential.

Early access

While self-service sign-in is open, you get a key from your account: request an emailed sign-in link, accept the agent access terms, then create read-only keys and see your usage there. The account page says whether sign-in is open right now. While it is closed, no keys can be created on this site and we issue pilot credentials separately.

Every request needs a key, including usage checks. The agent access terms and the privacy notice apply to every account.

To ask about a pilot account, email [email protected].

What the data is

Automated pricing source: Price snapshots read automatically from vendor pricing pages. Each one keeps its source address, observed and retrieved times and a content hash. None of them is human verified, and comparison results say so in each price's trust label. The pricing sources catalog shows automated pricing sources in the browser.
Human-reviewed records: Facts a person checked against the cited source, each with its own review date. A review is a point in time: an old review stays marked stale, and a reviewed price may have changed since. The methodology explains what a check covers.
Missing stays missing: A price, market, currency or tax basis the source did not state is returned as missing or unknown. Nothing is guessed, filled in or converted between currencies.
Comparisons without a winner: A comparison prices each snapshot for your scenario and lists them in a fixed order, each with its own source and date. It does not pick a cheapest or best product. When prices cannot be compared on the same basis, the result is not_comparable with the reasons. To compare checked records in the browser, use Compare.

Confirm final pricing, taxes, discounts, eligibility and contract terms with the vendor before purchase.

REST endpoints

Base address https://verifiedpricing.com/api/v1. Send the key as Authorization: Bearer. Reads need the prices:read scope; the two POST routes need comparisons:read.

GET /products: Search published products by name, paged.1 unit · prices:read
GET /prices: Current automated pricing snapshots, optionally for one product_id, paged.1 unit · prices:read
GET /prices/{id}: One pinned snapshot with its source, dates and qualifications.1 unit · prices:read
GET /prices/{id}/sources: Source address, capture times, content hash, quote and integrity for a snapshot.1 unit · prices:read
GET /products/{id}/history: Earlier and current dated snapshots for a product, paged.1 unit · prices:read
GET /records/{domain}: Human-reviewed facts and history for a domain, each with its own review date.1 unit · prices:read
POST /comparisons: Two or three pinned snapshots priced for one explicit scenario.1 per snapshot units · comparisons:read
POST /competitor-prices: Retained qualified competitors of one seed product, with their prices.limit (2 or 3) units · comparisons:read
GET /usage: Units used and remaining for the UTC day and month.No units · any key

Responses are JSON: {schema_version: 1, data, usage}. Lists return 1 to 50 rows per page, with an offset up to 10,000 and a next_offset. Errors use plain status codes: 401 for a missing or invalid key, 403 for a missing scope, 429 with Retry-After when a limit is reached, and 503 while the API is switched off.

Example requests

read -rs takes the key without showing it, and curl reads the header from stdin, so the key stays out of command arguments and shell history.

Shell, curl

read -rs VERIFIEDPRICING_API_KEY && export VERIFIEDPRICING_API_KEY

printf 'Authorization: Bearer %s\n' "$VERIFIEDPRICING_API_KEY" |
  curl -fsS -H @- "https://verifiedpricing.com/api/v1/products?q=mailerlite&limit=5"

printf 'Authorization: Bearer %s\n' "$VERIFIEDPRICING_API_KEY" |
  curl -fsS -H @- https://verifiedpricing.com/api/v1/usage

Limits and usage

Each account has 1,000 units per UTC day and 10,000 units per UTC month. The allowance is shared by every key on the account and by REST, the CLI and the MCP server. Days reset at 00:00 UTC and months on the first at 00:00 UTC.

A read costs 1 unit.
A comparison costs 1 unit per snapshot, so 2 or 3.
A competitor-prices request costs its limit, 2 or 3, once, even when some prices are missing.
/usage costs nothing and still answers when the allowance is used up.

Every response carries the used units, the limit and the reset time for the day and the month. Neither the API nor the clients retry a limited request for you.

Competitor prices

POST /competitor-prices takes one seed, a product_id or a domain, a scenario with currency, market and a timezone-aware time, and a limit of 2 or 3 products counting the seed.

LinkCensus link data proposes candidate competitor relationships. A competitor is returned only after its relationship was qualified and retained. The request reads that retained data only: it never starts a crawl or a LinkCensus query. Partial or unavailable coverage is stated in the response, with its reasons.

Install

Two Python packages: verifiedpricing-client, the REST client and verifiedpricing command, and verifiedpricing-mcp, the local MCP server. Both need Python 3.10 or newer on Linux or macOS. Windows is not supported.

Version 0.1.0. pip checks each wheel against its SHA-256 before installing both into their own virtual environment, and stops if either does not match. Release notes.

Shell, install

python3 -m venv ~/.verifiedpricing-venv
~/.verifiedpricing-venv/bin/python -m pip install \
  'https://github.com/pucilpet/verifiedpricing-agent-clients/releases/download/v0.1.0/verifiedpricing_client-0.1.0-py3-none-any.whl#sha256=13ebc82cd8b44098971a0a7e197e74442c53c04fade1ab19e4d6d519c7c664ea' \
  'https://github.com/pucilpet/verifiedpricing-agent-clients/releases/download/v0.1.0/verifiedpricing_mcp-0.1.0-py3-none-any.whl#sha256=a578e4c9488d9fbb3be6d006a8aa2a7095b31a38ad1dd0bb36dba8f00372ff7e'
export PATH="$HOME/.verifiedpricing-venv/bin:$PATH"

Command line

The verifiedpricing command covers every endpoint. Add --json for the full response; the plain output still shows sources, dates and trust labels. Replace the placeholder IDs with ones from a search or price list.

Shell, CLI

read -rs VERIFIEDPRICING_API_KEY && export VERIFIEDPRICING_API_KEY

verifiedpricing search mailerlite --json
verifiedpricing prices --product-id product:mailerlite.com --limit 10
verifiedpricing sources po_SNAPSHOT_ID
verifiedpricing compare po_SNAPSHOT_A po_SNAPSHOT_B \
  --currency USD --market US --seats 5 --as-of 2026-10-18T12:00:00Z
verifiedpricing usage

Local MCP server

verifiedpricing-mcp runs on your machine and talks to your MCP client over stdio. It is not a hosted server: there is no remote endpoint, no OAuth sign-in and no registry listing.

The configuration below holds no key. Save the key once to a private file only your user can read, or give the server VERIFIEDPRICING_API_KEY through your MCP client's private environment settings. Use the absolute path to your virtual environment.

Shell, save the key

read -rs VERIFIEDPRICING_API_KEY && export VERIFIEDPRICING_API_KEY
verifiedpricing configure
unset VERIFIEDPRICING_API_KEY

MCP client configuration, JSON

{
  "mcpServers": {
    "verifiedpricing": {
      "command": "/ABSOLUTE/PATH/TO/.verifiedpricing-venv/bin/verifiedpricing-mcp"
    }
  }
}

Tools

Nine read-only tools, one per endpoint, drawing on the same account limits. No tool accepts a key, an API address or a price of its own.

search_products: GET /products
get_prices: GET /prices
get_price: GET /prices/{id}
get_sources: GET /prices/{id}/sources
get_price_history: GET /products/{id}/history
get_reviewed_records: GET /records/{domain}
compare_prices: POST /comparisons
get_competitor_prices: POST /competitor-prices
get_usage: GET /usage