Pricing
How buzzabout charges per API call — four categories, all per-result and all reservation-based.
buzzabout charges credits per result, not per request. The four public
categories below cover every chargeable endpoint and MCP tool. Asking the
assistant (POST /v1/ask and the buzzabout__ask MCP tool) is free. A
credit is the smallest billable unit; one US dollar buys 1,000 of
them on the standard plan (your exact rate is on
buzzabout.ai/pricing).
Categories
| Category | Credits | When | Reservation-based? |
|---|---|---|---|
mention | 1 | per mention collected (dataset run or tracking-agent re-scrape — unified for clients) | yes |
audience_profile | 3 | per profile collected by an audience-dataset run | yes |
post_processing | 0.5 | per post processed by a custom-parameter run or pattern-detection run | yes |
preview_generation | 1 | per source in a research preview (url previews refund profiles that returned no data) | yes |
Custom-parameter preview is free, and so is asking the assistant
(POST /v1/ask / buzzabout__ask).
Reservation-based charging
Every chargeable category on the public surface is reservation-based.
The endpoint reserves credits up-front based on the upper-bound result
count (e.g. the requested count on a dataset run, the source dataset's
mention count for a custom-parameter or pattern-detection run), then
refunds any unused credits when the run completes. A run that asked for
500 mentions and returned 412 leaves you charged for 412 — the remaining
88 credits go back to your balance.
A research preview reserves 1 credit
per source; url previews refund any source that returned no data
(private, non-existing, or failed to retrieve).
If a run fails before it can produce results, the full reservation is refunded.
Insufficient credits
Endpoints that would exceed your balance return 402 insufficient_credits
before any work starts. Top up via the web app or upgrade your plan;
in-flight requests are never partially charged.
Programmatic access
The current price table is available without authentication at
GET /v1/credit_prices:
curl https://api.buzzabout.ai/v1/credit_prices{
"status": "success",
"data": {
"mention": 1,
"audience_profile": 3,
"post_processing": 0.5,
"preview_generation": 1
}
}Use this to build cost dashboards, pre-flight budget checks, or to ground a cost-conscious agent's reasoning. The shape is flat and the keys are stable — new categories ship as additive fields.
Usage history
GET /v1/me/usage_history returns a paginated feed of charges and
refunds against your account. Each item carries the category, the
endpoint that produced it, and the delta in credits. See
/v1/me.
The feed may include legacy category strings (ai_assistant, REPORT,
AUDIENCE_RESEARCH, TRACKING) for charges that pre-date this surface —
those endpoints aren't part of the public API but their history shows
up on the same feed. In particular, ai_assistant belongs to the
assistant in the previous version of the app; asking the assistant
today (POST /v1/ask / buzzabout__ask) is free, so the category
appears only on old rows.
Next steps
GET /v1/credit_prices— programmatic price lookup.GET /v1/me— current balance + usage history.- API overview — once you know what each call costs.