Credits
How the HTTP API uses your organization credit balance and where to find prices in OpenAPI.
Metered SnitchFeed features draw from the same organization credit pool as the product app. The public v1 API charges credits only for successful search calls:
| Endpoint | Credits (per successful request) |
|---|---|
POST /v1/data/twitter/searchTweets | 2 |
POST /v1/data/linkedin/searchPosts | 4 |
GET /v1/billing/usage is read-only and does not consume credits.
OpenAPI
The same numbers appear in GET /v1/openapi.json under components.schemas.SnitchFeedCreditRates for codegen and tooling. This page is the canonical place to read what each field means and how the HTTP API uses credits.
In Docs → API, use the Twitter, LinkedIn, and Billing sections for operations; each search operation description includes the per-request credit cost.
Full product reference
For how credits work across listeners, exports, chat, and estimates, see Credits & usage in the main documentation.