REST API + MCP

Every item's history on any page, through an API

Point BriefPanel at a pricing page, a changelog or a catalog. Each product, plan or job becomes an item with its own identity, and each change arrives typed: the field that changed, its previous and current value, and how much it matters.

Get your API key Read the docs

No subscription · Pay only for the pages read · API key on the spot, no sales call

For technical teams

Structured changes for systems, automations, and agents

Query item-level history through the REST API or MCP. No reprocessing HTML, screenshots, or page diffs.

A data contract ready to integrate

The same typed feed serves custom integrations and AI agents.

Paginated item-level feed
Read changes across every source by cursor, time, and importance.
Before and after by attribute
Price and custom fields arrive with their type, previous value, and current value.
REST and MCP on the same model
Your system queries the API; agents use get_source_changes without losing context.

View API documentation Connect via MCP

RESTGET /v1/updates?importance=material

200 OK

{
  "data": [
    {
      "sourceName": "Acme Cloud (fictional)",
      "entryTitle": "Scale plan",
      "kind": "plan",
      "updateType": "modified",
      "importance": "material",
      "field": "price",
      "valueChange": {
        "type": "number",
        "previous": 49,
        "current": 59,
        "unit": "USD"
      },
      "priceDelta": 10
    },
    {
      "entryTitle": "Payments API",
      "kind": "documentation",
      "updateType": "modified",
      "importance": "critical",
      "field": "authentication",
      "valueChange": {
        "type": "string",
        "previous": "API key",
        "current": "OAuth 2.0"
      }
    }
  ],
  "pagination": {
    "nextCursor": null,
    "hasMore": false
  }
}

The same feed is available through MCP

get_source_changes

Fictional example; the fields and envelope match the public API contract.

Anatomy of a change event

entryTitle: The resolved item — not the page. History attaches here.
updateType: new, modified, or removed. A removal is a signal too.
importance: critical, material, or minor, so you can filter noise server-side.
field: The named attribute that moved, derived from your monitoring prompt.
valueChange: Typed previous and current values, with unit where it applies.

Usage-based pricing

Pay for monitored volume. No monthly subscription.

One page read consumes 1 credit. Model your operation's monthly volume.

1 credit = 1 page read. A source whose items have their own pages reads up to pages per check, plus up to more when it also follows the list's next pages.

Set cadence per source and focus volume where freshness is critical.

Top up credits on demand.

Start with free checks after verifying your email. Self-service purchase, with no contract or recurring plan.

Configure volume

Monitored sources

Frequency per source

Pages read per check

1 when the source's items have no pages of their own, up to 1 when they do — plus up to more if it follows the list's next pages.

This estimate uses a 30-day month. Actual usage depends on configured cadences, checks that run, and how many item pages each check follows.

Operational projection

Monthly volume and cost

Checks150

Page reads300

Projected cost—/mo

Loading current pricing…

Start monitoring

Turn a URL into actionable history

Start with the page that lists what matters. BriefPanel finds the items and builds a history for each one.

Add a source

Self-service · no required subscription · pay as you go.