Top websites trend API

What the Top Websites feed returns

get_top_trends with type: "Top Websites" returns the current global traffic rank leaderboard as JSON. Each row is a rank position, domain name, and category slug. The snapshot timestamp appears in as_of_ts.

Unlike keyword sources that need a keyword field, live feeds need only mode: "top_trends" and a feed label. For historical web demand on specific brands, pair this feed with web traffic data keyword series.

Request body

{
  "mode": "top_trends",
  "type": "Top Websites",
  "limit": 25
}

Category filter for a vertical slice:

{
  "mode": "top_trends",
  "type": "Top Websites",
  "category": "e-commerce-and-shopping",
  "limit": 10
}

Pagination uses offset. Default limit is 25; maximum is 200 per call. Each feed page counts toward the monthly request quota.

Live snapshot: cross-industry leaderboard

Trends MCP API snapshot, June 2 2026 (limit 15):

Several rows share rank 1 because the feed groups leaders within category segments before the global sort. Client code should treat as_of_ts as the freshness anchor and store full tuples, not just domain strings.

Live snapshot: e-commerce filter

Same API snapshot with category: "e-commerce-and-shopping":

The category filter is the fastest path when an agent receives a question like "which e-commerce domains rank highest globally today." Temu at rank 2 beside Amazon and eBay is the kind of shift competitive intelligence teams watch weekly.

JavaScript example

const res = await fetch("https://api.trendsmcp.ai/api", {
  method: "POST",
  headers: {
    Authorization: "Bearer YOUR_API_KEY",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    mode: "top_trends",
    type: "Top Websites",
    category: "e-commerce-and-shopping",
    limit: 10,
  }),
});
const payload = await res.json();

MCP prompt pattern

"Using TrendsMCP, show the top e-commerce websites by global traffic rank today."

On MCP, type is required and only one feed runs per call. REST clients can omit type to fetch all feeds in one response, but that burns more quota per refresh.

Workflows that fit this feed

Competitive monitors. Store a daily JSON file per category. Diff today's list against yesterday's. New entrants in the top 10 trigger a Slack webhook.

Journalist trend briefs. When a domain spikes in news volume elsewhere, check whether it also climbed the Top Websites board. Divergence (high news, flat traffic rank) sometimes signals a PR cycle without sustained audience gain.

Agent grounding. ChatGPT and Claude connectors can call this feed before answering "what sites are dominating traffic in gaming right now." The category slug games/games or games/board-and-card-games narrows the list.

For a broader Similarweb-style comparison, see Similarweb alternative.

Category slugs to try

The API accepts category strings as returned in feed rows. Common filters observed in live data:

• e-commerce-and-shopping
• law-and-government
• health
• games
• food-and-drink
• business-and-consumer-services

If a filter returns zero rows, the slug may need a subcategory suffix (for example e-commerce-and-shopping/price-comparison). Inspect an unfiltered pull first, then copy the exact category string from a matching row.

Quota and refresh cadence

Top trends calls count per feed and per page. A monitor that pulls five categories every hour should budget five requests per hour, not one. See https://www.trendsmcp.ai/docs for tier limits.

The as_of_ts field shows when the pipeline last refreshed. Do not assume sub-minute freshness; daily or hourly polling matches how traffic rank boards typically move.

Error handling

Feed labels are case-sensitive. top websites fails; Top Websites succeeds.