Credits
How the HTTP API uses your organization credit balance.
Metered SnitchFeed features draw from the same organization credit pool as the product app. The public v1 API charges credits only for successful v1/data/ calls:
| Endpoint | Credits |
|---|---|
POST /v1/data/twitter/tweets/search | 2 per successful request |
POST /v1/data/linkedin/posts/search | 4 per successful request |
POST /v1/data/linkedin/company/get | 4 per successful request |
POST /v1/data/linkedin/person/posts | 10 per successful request (one page) |
POST /v1/data/linkedin/person/comments | 10 per successful request (one page) |
POST /v1/data/linkedin/posts/comments | 1 per comment returned |
POST /v1/data/linkedin/posts/reactions | 1 per reaction returned |
POST /v1/data/hackernews/search | 2 per successful request |
Successful LinkedIn search, person posts, and person comments responses return the full page. Optional count on search and person posts is ignored.
POST /v1/data/linkedin/person/comments returns comments authored by a person (profile URL). POST /v1/data/linkedin/posts/comments scrapes comments on a post (post URL).
All other v1 endpoints (GET /v1/data/linkedin/industries, GET /v1/organization/usage, and every /v1/mentions, /v1/listeners, /v1/feeds, /v1/organization/context endpoint) are read-only and do not consume credits.
OpenAPI
The same numbers appear in GET /v1/openapi.json under components.schemas.SnitchFeedCreditRates for codegen and tooling.
Full product reference
For how credits work across listeners, exports, chat, and estimates, see Credits & usage in the main documentation.