Read traffic estimates, search data and public domain facts from your own tools. HTTP and MCP use the same bearer key; sign in when you are ready to create one.
The API returns the same public data as the site: a cached domain snapshot first, the search footprint when the plan allows it, or a comparison of several domains.
Scale · full-site estimate
Registry · registration facts
Profile · public site, DNS, hosting and TLS facts
Popularity · public link and board ranks
Search · Pro search footprint for this month
Your first request
This example reads a cached domain snapshot and returns the data currently available.
01
Get a key
Sign in, open the API console and create or reveal a vf_live_ key. Keep it on your server or in an environment variable.
02
Call an endpoint
Start with a domain snapshot. It reads the cache and tells you when a family is missing.
03
Read the response
Keep as_of, confidence and estimate with every number. A missing field stays missing.
Read US/English search demand and Google results. Pro-only; a cache miss uses the search grant.
Parameter
Description
qRequired
Keyword such as ai or website traffic checker.
GET/api/v1/bulk
Bulk comparison
Compare several domains side by side. Each domain uses one daily lookup.
Parameter
Description
qRequired
Comma-separated domains, for example google.com,apple.com.
GET/api/v1/tld
Extension comparison
Compare the same registrable name across extensions. The default is com, ai and io.
Parameter
Description
qRequired
Registrable base name such as google.
sOptional
Optional comma-separated suffixes.
GET/api/v1/account
Account usage
Read the plan and remaining allowances before a batch. This request does not use a lookup.
Domain family shortcuts`/api/v1/domains/{domain}/scale`, `/registry`, `/profile`, `/popularity` and `/search` return a DomainResource with one family. Search is Pro-only.
What comes back
Responses use product field names rather than vendor names. Estimates keep their date and confidence; missing families stay explicit.