# What’s Trending agent skill

Use What’s Trending when a user needs current, source-linked customer conversation evidence before deciding what social content to create.

## Interfaces

- REST base: https://api.whatstrending.cc
- OpenAPI: https://api.whatstrending.cc/openapi.json
- MCP endpoint: https://api.whatstrending.cc/mcp
- MCP discovery: https://api.whatstrending.cc/.well-known/mcp.json
- Human documentation: https://whatstrending.cc/for-agents

## Authentication

Ask the user to activate Pro and create a workspace API key in What’s Trending Settings. Send it as `Authorization: Bearer wt_live_YOUR_KEY`. Never place the key in a URL, public document, log, or model-visible output.

## Recommended workflow

1. Call `GET /v1/workspace` to understand the product, WordBank and competitors.
2. Call `GET /v1/trends?days=30` to identify ranked customer topics.
3. Call `GET /v1/evidence` to inspect supporting posts and original URLs.
4. Preserve source URLs and distinguish missing metrics from zero.
5. Call `POST /v1/scans` only when evidence is stale; scans are rate-limited.
6. Present content ideas as recommendations that require human review.

## Available MCP tools

- `get_trends`: read ranked topics for 7, 30, 90, 180 or 365 days.
- `list_evidence`: read source posts filtered by timeframe, platform or text.
- `run_scan`: perform a live scan and update the workspace evidence history.

## Boundaries

What’s Trending reads public or authorized platform data. Coverage and engagement fields vary by platform. Do not claim access to private posts, private comments, private impressions, or unavailable metrics.