POST /utility/prefetch as soon as you know the domain or email, and the user-facing /brand/retrieve lands on a warm cache. The request body carries a type (currently only "brand") and an identifier object with exactly one of domain or email:
/brand/retrieve returns instantly.
0 Credits. No rate limit. Subscriber-only.
The legacy
POST /brand/prefetch and POST /brand/prefetch-by-email endpoints (and their SDK methods utility.prefetch / utility.prefetchByEmail) still work unchanged. New integrations should use POST /utility/prefetch so future identifier types are picked up automatically.How the cache works
- Cache TTL is up to 3 months. After that, the next call triggers a refresh in the background.
- The cache is shared across the account. A prefetch from a backend job warms the cache for a user-facing call seconds later.
- Prefetch is fire-and-forget. The endpoint returns immediately after queuing the work. You do not wait for the prefetch before calling
/brand/retrieve. - Prefetch by email skips known free/disposable providers. Calls against
gmail.com,yahoo.com,outlook.com, and the 10,000+ disposable services return a422(FREE_EMAIL_DETECTEDorDISPOSABLE_EMAIL_DETECTED) that you can safely ignore. - Provide exactly one identifier. Sending both
domainandemail(or neither) returns a400.
Latency
| Pattern | p50 | p90 | p99 |
|---|---|---|---|
Cold /brand/retrieve (no prefetch) | 7s | 18s | ~1 min |
Cached /brand/retrieve (after prefetch or prior hit) | <1s | <1s | <1s |
What prefetch does not do
- It does not speed up scraping endpoints.
/web/scrape/*,/web/crawl,/web/screenshot, and/brand/ai/*are not affected by the brand cache. Each call fetches the target URL. - It does not preempt rate limits. Prefetch itself is rate-limit-free, but the eventual
/brand/retrievecall still counts against your plan’s per-minute rate limit. - It does not return brand data. The endpoint queues the work and returns
{ status, message, type, domain, key_metadata }. To read the brand, call/brand/retrieveseparately.
Related resources
Rate limits
How the per-plan per-minute limits interact with cached and prefetched
calls.
Best practices
Where prefetching fits in the broader integration pattern.
Troubleshooting
Cold-hit timeouts and how to handle them.
Get brand data
The endpoint prefetching warms.