Free
$0 /mo
Test the raw-data workflow from your local agent. No card required.
- 200 delivered records / month
- MCP, REST API and console
- managed AI scraper catalog
- Raw answers, citations and provider metadata
- Local demo workspace
- No scheduled runs
Pay per delivered record
Simple data-plane pricing
One credit equals one raw provider record. No score generation, report fees or charges for failed delivery.
Pro
Popular
$39 /mo
Put one or more local agents on a managed answer-data connection.
- 5,000 delivered records / month
- $0.012 / extra credit
- Up to 10 scheduled prompt runs
- Completion and failure webhooks
- 1 seat
- Per-key budgets and account spend cap
Studio
Coming
$149 /mo
For teams moving prompt batches into repeatable agent workflows.
- 20,000 delivered records / month
- $0.009 / extra credit
- 100 schedules with hourly cadence
- 5 seats + shared credit pool
- Async batches and signed delivery webhooks
- Raw-record export to your storage
- Priority provider routing
Scale
Coming
$499 /mo
Higher-volume collection for many agents and production pipelines.
- 75,000 credits / mo
- $0.007 / extra credit
- Unlimited schedules and batch jobs
- 15 seats
- SSO
- Custom surface and delivery policies
Enterprise
Coming
Custom
Committed use, dedicated routing and private delivery controls.
- Committed-use credits
- SLA
- Dedicated routing
- Private provider connections
- SSO / SCIM
- Reseller white-label metering
Spend caps stay on
Set account and per-key limits before an agent runs. Provider failures deliver no record and consume no credit.
Pricing questions
What counts as one credit?
One successfully delivered provider record counts as one credit. A prompt sent to three AI surfaces can deliver up to three records.
Do failed scrapes cost credits?
No. ChatSights charges credits only for records returned successfully by the provider.
Does ChatSights charge for analysis?
No analysis is performed. Your local agent interprets the raw answer text and sources.
Is the scraper provider included?
ChatSights manages the provider connection and exposes it through one MCP and REST contract. Provider usage is represented by ChatSights credits.