---
name: whatstrending-research
description: Use What’s Trending when a user needs current, source-linked customer-conversation evidence before deciding what content to create. Requires a user-provided Pro workspace API key for private data and confirmation before a live scan.
---

# What’s Trending research

Use What’s Trending to inspect a configured market, ranked customer-interest topics, and the original public evidence behind them. Prefer reads before triggering a new scan.

## Discover the contract

- [OpenAPI 3.1](https://whatstrending.cc/openapi.json)
- [Agent integration guide](https://whatstrending.cc/for-agents)
- [Authentication](https://whatstrending.cc/auth.md)
- [Pricing](https://whatstrending.cc/pricing.md)
- [MCP endpoint](https://api.whatstrending.cc/mcp)

## Safe workflow

1. Ask the user for the intended workspace and timeframe.
2. Read `GET /v1/workspace` or use `get_trends` before changing anything.
3. Inspect trends and supporting evidence together.
4. Preserve original source URLs and distinguish unavailable metrics from zero.
5. Trigger `POST /v1/scans` or `run_scan` only with user intent; these calls persist evidence and consume the hourly scan allowance.
6. Present content directions as recommendations for human review, not proof of market-wide demand.

## Boundaries

Keep `wt_live_` credentials server-side and out of prompts, URLs, logs, and public output. Do not claim access to private posts or unexposed metrics. Do not treat one viral post as broad market evidence.