---
title: "What’s Trending API and Agent Integration"
description: "Use What’s Trending from an agent through its REST API, OpenAPI description, or MCP-compatible tool endpoint."
canonical: "https://whatstrending.cc/for-agents"
updated: "2026-10-11"
---

For agents and developers · Pro

# Use live market evidence as a tool.

Agent access is included with the $50/month Pro plan. Create a key in **Settings → Agent access**. 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 [whatstrending.cc/openapi.json](https://whatstrending.cc/openapi.json). Agent-readable Markdown is published at [skills.md](https://whatstrending.cc/.well-known/agent-skills/whatstrending-research/SKILL.md) and [api.md](https://whatstrending.cc/api.md).

## 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, up to once per hour with no monthly cap. |

## 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](https://whatstrending.cc/.well-known/mcp).

## 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.
