Glimpse (page updated 5 August 2026) positions its API as Google search volume calibrated to Trends. Two GET routes live on https://enterprise.meetglimpse.com. /v1/interest is a 0-100 series. /v1/interest_enriched is absolute volume. geo is a two-letter country or worldwide. resolution is daily, weekly, or monthly. phrase_match mirrors quoted Trends syntax. Auth is an apikey header. Trends API is a POST. body is a JSON string and must be parsed a second time. Docs: the API reference. Caps: pricing. Google notes: the Google Trends guide.
Absolute volume is Glimpse's claim
Glimpse argues that a 0-100 index is not enough for models and that other SEO tools lag by months. interest_enriched is the product of that claim. Trends API also returns volume when a source has it. On google search that volume can be estimated and derived from the trend value. Do not treat the two volume columns as the same methodology.
Two documented Glimpse endpoints
curl --request GET --url "https://enterprise.meetglimpse.com/v1/interest?keyword=keto&geo=WW&resolution=weekly" --header "apikey: YOUR_API_KEY"
POST https://api.trendsapi.ai/api
Authorization: Bearer <api_key>
Content-Type: application/json
{"mode":"get_time_series","source":"google search","keyword":"keto"}
Glimpse supports Google Topic codes from the Explore URL (/m/...). Trends API takes a phrase on google search. It does not take a mid as a special type.
Enterprise add-on, no public API price
The Glimpse API page invites "Get API Access" and points support at [email protected] for rate limits. There is no self-serve price table on that page. Trends API publishes plan text on pricing. Compare invoices, not blog guesses.
Google-only versus a shared scale
Glimpse is a Google search product. Trends API is a multi-source product. A dashboard that must put keto next to a TikTok phrase uses source tiktok on a second field in get_growth. Glimpse will not fill that cell. Keep Glimpse when absolute Google volume, phrase match, and topic mids are the requirement.