Skip to main content

Documentation Index

Fetch the complete documentation index at: https://prefetch.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

​
Credit costs

Each data extraction endpoint consumes a fixed number of credits per successful request:
EndpointCreditsWhat you get
GET /enrich20Brand + company + classification
GET /brand10Colors, logos, fonts, social links
GET /company5Company name, emails, addresses
GET /classify5IAB category, descriptions, tickers, ISINs
GET /screenshot2Webpage screenshot URL
GET /health—Liveness check
GET /ready—Readiness check

​
When credits are deducted

Credits are deducted only on successful responses — meaning the API returned "success": true with a 200 status code. You are not charged for:
  • Failed requests (4xx or 5xx responses)
  • Validation errors (missing URL, bad parameters)
  • Authentication failures
  • Rate limit rejections (429)
  • Timeouts (504)

​
Credit limits

Each API key can have a credits_limit configured. When cumulative credits_used reaches this limit, all further requests return: 
{
  "success": false,
  "error": "Credit limit exceeded",
  "meta": { ... }
}
Manage and monitor your credit usage from the dashboard.

​
Choosing the right endpoint

When you need brand, company, and classification data for a URL, use /enrich for a single optimised call instead of three separate requests:

Use /enrich

20 credits for brand + company + classification.Best when you want a complete domain profile in one call.

Use individual endpoints

More targeted — only pay for what you need.Best when you only need one or two data types.
ScenarioBest approachCredits spent
Need all three data types/enrich20
Need brand + company only/brand + /company15
Need brand only/brand10
Need classification only/classify5
Need screenshot only/screenshot2
Need brand + classification/brand + /classify15