buzzabout docsPricing
How buzzabout charges per API call — four categories, per-result for collection, per-turn for the assistant.
buzzabout charges credits per result, not per request. The four public categories below cover every chargeable endpoint and MCP tool. 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 | no |
ai_assistant | 15 | per POST /v1/ask turn — also per buzzabout__ask MCP call | no |
Custom-parameter preview is free.
Reservation-based charging
Collection categories (mention and audience_profile) reserve credits
up-front based on the upper-bound result count, then refund 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.
If a run fails before it can produce results, the full reservation is refunded.
Non-reservation categories (post_processing, ai_assistant) charge
exactly the amount produced — there is no up-front hold.
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-staging.com/v1/credit_prices{
"status": "success",
"data": {
"mention": 1,
"audience_profile": 3,
"post_processing": 0.5,
"ai_assistant": 15
}
}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 in-app category strings (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.
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.