For developers

Trend data, in your own stack

Two ways to reach the same data that powers YoTrends: a REST API for your backend, and an MCP server so an AI assistant can query it directly.

Two interfaces

REST API

Seven read endpoints over trending videos, creators and categories. JSON, API-key auth, documented in OpenAPI.

Open API docs

MCP server

Nine tools for Claude, Cursor and other MCP clients: search trends, track topics, generate a text pack without leaving the chat.

How it works

Endpoints

All endpoints are read-only and return JSON. Parameters, response shapes and a live try-it console are in the interactive docs.

EndpointReturns
GET /api/public/v1/youtube/trends/videosTrending YouTube videos by region, category and window
GET /api/public/v1/tiktok/trends/videosTrending TikTok videos by region, category and window
GET /api/public/v1/youtube/trends/influencersYouTube creators ranked by how often they appear in trends
GET /api/public/v1/tiktok/trends/influencersTikTok creators ranked the same way
GET /api/public/v1/categoriesThe category taxonomy
GET /api/public/v1/categories/{group}/subcategoriesSubcategories inside one category group
GET /api/public/v1/categories/{group}/trendlineA category's trend line over time

Authentication

Every request carries your key in the X-API-Key header. Generate one in Settings once your plan includes API access.

curl -H "X-API-Key: $YOTRENDS_API_KEY" \
  "https://yotrends.ai/api/public/v1/youtube/trends/videos?region=US&limit=10"

Keys are secret and carry your plan's access. Keep them server-side, never in browser code.

What each plan includes

PlanAPI calls per monthMCP server
Free, Creator, ProNot includedCreator and Pro: yes
Team500Yes
Agency1000Yes

The MCP server is included with every paid plan. The REST API is on Team and Agency. Need a higher allowance? Contact us.