Overview
Your VidNavigator plan includes a monthly credit pool shared across all API operations. Different services consume credits at different rates. You can monitor your current balance at any time by calling the/usage endpoint.
There are no per-service limits — all operations draw from the same credit pool. The activity counters shown in
/usage are informational only.Credit Costs per Service
Deduction Order
Credits are deducted in this order:- Monthly credits are consumed first
- Purchased credits cover any overflow
Plan Credit Allowances
Voyager and above can purchase additional credit packs: 50 credits (100), or 1,200 credits ($300).
Service Details
Standard Requests
Each non-YouTube transcript request to
/transcript consumes standard_request units. 1 credit covers 10,000 standard requests.Residential Proxy Requests
Fetches that route through residential proxies consume
residential_request units. 1 credit covers 200 residential requests.For YouTube, even
metadata_only: true routes through the residential proxy and is billed as a residential_request. YouTube search and TikTok search also bill per residential page fetched.Transcription Hours
/transcribe, /upload/file, and speech-to-text fallback consume transcription_hour units. 1 credit covers 3 hours of audio/video processed.
Files uploaded via
/upload/file also count towards your storage quota.Analysis Requests
/analyze/*, /extract/*, /youtube/search, /search/file, and /tweet/statement consume analysis_request units. 1 credit covers 100 analysis requests.LLM analysis is token-based: 1
analysis_request unit covers up to 15,000 total tokens. Larger contexts use ceil(total_tokens / 15000) units. Multiple internal LLM calls in one request are consolidated into a single charge.Search Requests
Semantic (vector) searches over already indexed content consume a
search_request unit. This includes indexed YouTube channel search and each call to /search/file. 1 credit covers 1,000 semantic searches.Global YouTube search (
/youtube/search) and TikTok keyword search (/tiktok/search) do not bill search_request — they bill per residential_request (and analysis_request for YouTube search) instead.Data Extraction
Each call to
/extract/video or /extract/file uses AI to extract structured data from transcripts. Analysis Request units scale with token usage.Per-Call Usage Disclosure
Most billable endpoints accept aninclude_usage flag. When set to true, the response includes a usage block that lists exactly what was charged for that specific call — every meter that fired, the net credits deducted, and (for LLM endpoints) the token tally.
For the async TikTok endpoints, billing happens in the background worker, so
include_usage is passed on the polling GET (once task_status=completed), not on submit. See TikTok Search Result and TikTok Profile Result.This per-call
usage block is distinct from the aggregate GET /usage endpoint, which reports cumulative counters and balances for the whole billing period.Hard Limits (Not Credit-Gated)
Some resources have fixed plan limits that are not deducted from your credit pool:YouTube vs Other Platforms
Why do Residential Proxy Requests cost more?YouTube and some scraper flows require residential proxy infrastructure for reliable access. This is reflected in the credit rate (1 credit per 200 Residential Proxy Requests vs. 1 per 10,000 Standard Requests).
Free Endpoints
The following endpoints do not consume credits:GET /files— List your uploaded filesGET /file/{file_id}— Get file info and transcriptGET /file/{file_id}/url— Get temporary file URLGET /namespaces— List namespacesPOST /namespaces— Create a namespacePUT /namespaces/{namespace_id}— Rename a namespaceDELETE /namespaces/{namespace_id}— Delete a namespacePUT /file/{file_id}/namespaces— Update file namespace assignmentsGET /tiktok/profile/{task_id}— Poll a TikTok profile scrape (billing happens in the background worker)GET /tiktok/search/{task_id}— Poll a TikTok keyword search (billing happens in the background worker)GET /health— Health checkGET /usage— Usage statistics

