For agents and developers
Use live market evidence as a tool.
Create a key in Settings → Agent API. Keys are shown once, stored as hashes, scoped to one workspace, and revocable at any time.
Quick start
Pass your key as a Bearer token. This request returns ranked topics for the workspace’s configured WordBank.
curl "https://api.whatstrending.cc/v1/trends?days=30" \ -H "Authorization: Bearer wt_live_YOUR_KEY"
The machine-readable contract is available at api.whatstrending.cc/openapi.json.
REST API
| Method | Path | Purpose |
|---|---|---|
| GET | /v1/workspace | Read the configured website, WordBank and competitors. |
| GET | /v1/trends | Rank customer-interest topics over 7, 30, 90, 180 or 365 days. |
| GET | /v1/evidence | Read source URLs, excerpts and available public engagement. |
| POST | /v1/scans | Run a fresh scan. Limited to one agent-triggered run per 15 minutes. |
Agent tools
The stateless HTTP endpoint at https://api.whatstrending.cc/mcp exposes three tools: get_trends, list_evidence, and run_scan. It accepts JSON-RPC tool discovery and calls over POST.
curl https://api.whatstrending.cc/mcp \
-H "Content-Type: application/json" \
-H "Authorization: Bearer wt_live_YOUR_KEY" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Discovery metadata is published at /.well-known/mcp.json.
Data and safety
The API returns only evidence already stored for the authenticated workspace. Source coverage and engagement fields vary by platform. A tool result never implies access to private content.
Agents should show source URLs next to conclusions, distinguish observed metrics from inferred significance, and reuse stored evidence before triggering another scan.
