Credits & Pricing
How credits work, what each endpoint costs, and how to monitor your usage.
Pricing is customized. Credit package pricing is not published here — contact us to discuss your use case and volume. Credit prices are subject to change.
How Credits Work
The Signals API uses a simple credit-based model: you have a monthly credit allowance, and each API call draws from it.
1 credit = 1 API call for most endpoints.
Credits reset at the start of each billing period (every 30 days from your account start date). Unused credits do not roll over.
Credit Costs by Endpoint Type
Standard endpoints — 1 credit per call
Search, enrich, timeline, and single-signal fetch all cost 1 credit per call, regardless of how many signals are returned in the response.
Bulk endpoints — 1 credit per record
For bulk enrichment, credits are charged per input record, not per request. This keeps the model predictable at scale:
| Endpoint | Credit cost |
|---|---|
POST /v1/companies/bulk with 50 domains | 50 credits |
POST /v1/contacts/bulk with 20 contacts | 20 credits |
Webhooks — 1 credit per delivery
Webhook subscription management (create, update, list, delete) is free. Credits are consumed when a signal event is actually delivered to your endpoint. Backfill deliveries count the same as live deliveries.
Intent endpoints (Coming Soon) — higher credit rate
Intent scoring endpoints (/v1/intent/companies, /v1/intent/contacts) perform deeper semantic analysis across many signals per entity, requiring significantly more compute. These will be priced at a higher credit rate than standard calls. Exact pricing TBD.
Credit-Free Endpoints
The following endpoints never consume credits:
| Endpoint | Description |
|---|---|
GET /v1/signals/types | List available signal types |
GET /v1/signals/trending | Trending signals feed |
GET /v1/stats | Collection statistics |
GET /v1/account | API key account info |
GET /v1/credits | Credit balance |
GET /v1/logs | Request history |
All /v1/webhooks management routes | Subscription CRUD |
Monitoring Usage
Every API response includes current credit usage in the headers — no separate call needed:
x-credits-used: 142
x-credits-remaining: 9858
x-credits-limit: 10000
x-credits-reset: 2026-04-01T00:00:00.000Z
To check your balance explicitly:
curl https://signals.autobound.ai/v1/credits \
-H "x-api-key: YOUR_API_KEY"{
"monthly_limit": 10000,
"used": 142,
"remaining": 9858,
"period_start": "2026-03-01T00:00:00.000Z",
"period_reset": "2026-04-01T00:00:00.000Z",
"unlimited": false
}You'll also receive automated email alerts when you hit 80% and 100% of your monthly limit.
When Credits Run Out
Once your monthly limit is reached, all credit-consuming endpoints return a 402 error:
{
"error": "credits_exhausted",
"message": "Monthly credit limit of 10,000 reached. Credits reset at the start of your billing period.",
"code": 402,
"credits_used": 10000,
"credits_limit": 10000
}Credit-free endpoints (see table above) continue to work even when credits are exhausted.
Questions
Contact [email protected] to discuss credit packages, volume pricing, or enterprise plans.
Updated about 7 hours ago
