Prices

GET /v1/prices returns the price in US dollars for one result in each of the four public categories, at the rate that applies to the calling account. Authenticated with your API key like every other public route.

Endpoint

curl -X GET "https://example.com/v1/prices"

{
  "status": "info",
  "data": {
    "currency": "usd",
    "prices": {
      "audience_profile": 0.021,
      "mention": 0.007,
      "post_processing": 0.0035,
      "preview_generation": 0.007
    },
    "rate": 0.007
  }
}

Why this exists

So your agent or dashboard can ground cost reasoning in live prices without scraping the docs — and, now that prices are per-account, so you never have to guess which rate you are on. The shape is flat and stable; new categories ship as additive fields.

{
  "status": "success",
  "data": {
    "currency": "usd",
    "rate": 0.007,
    "prices": {
      "mention": 0.007,
      "audience_profile": 0.021,
      "post_processing": 0.0035,
      "preview_generation": 0.007
    }
  }
}

Prices depend on your plan

Every action has a fixed unit ratio that is the same for everybody — one collected mention is 1 unit, an audience profile is 3 units, a processed post is 0.5 units. What differs per account is the rate: the dollars one unit costs on your plan. A higher plan buys a cheaper unit.

price for a category  =  units × your rate

rate is your account's dollars-per-unit, and each entry under prices is that rate already multiplied out for you. The example above is an account on a 0.007 rate, so a mention (1 unit) is $0.007 and a processed post (0.5 units) is $0.0035.

Categories

preview_generation is the per-source price for a research preview; url previews refund sources that returned no data.

mention covers both dataset runs and tracking-agent re-scrapes — they are priced identically and presented to public clients as a single category.

Next steps

• Pricing — overview of all four categories.
• GET /v1/me/usage_history — your account's charge feed, in dollars.