> ## Documentation Index
> Fetch the complete documentation index at: https://docs.poddata.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Quotes and trackers

> Find what someone said, with the exact words, the speaker, the source, the day and the second; and follow a topic or a person with a tracker.

## Find what someone said

`GET /quotes` answers quotes from podcasts, long interviews, hearings and companies' own events, each with its exact words, its speaker, the show and episode, the day, the second it starts, and a page to cite.

```bash theme={null}
curl -s 'https://api.poddata.ai/v1/quotes?q=power%20limits%20on%20data%20centers&kind=ceo&limit=2' \
  -H "Authorization: Bearer $PODDATA_API_KEY"
```

* `q` matches by meaning, best match first. Words in quotation marks match exactly, in order.
* Without `q`, the newest episode comes first.
* Narrow it with `person` (an id from `GET /people`), `company` (the speaker's), `named` (a company or person the quote names), `ticker`, `show`, `kind` (CEOs, investors and the rest), `from` and `to`, and `list`, one of your team's lists.
* A quote whose speaker isn't confirmed is left out unless `confirmed=false`, and then it's marked so.
* `format=csv` gives the list as a file.

Each quote has `text`, its words; `speaker`; `show` and `episode`; `starts_at`, the second; `url`, the page to cite on poddata.ai; and `cite`, a line to quote it by. `GET /quotes/{id}` gives one, and `GET /quotes/{id}/source` the recording from its second, with who spoke when.

| To | Route | MCP tool |
| - | - | - |
| Search quotes | `GET /quotes` | `search_quotes` |
| One quote | `GET /quotes/{id}` | `get_quote` |
| Its source, from its second | `GET /quotes/{id}/source` | `quote_source` |
| What the same person said on it before | `GET /quotes/{id}/earlier` | `earlier_quotes` |
| How many one search finds, by kind | `GET /search/counts` | `search_counts` |
| A person, by name or id | `GET /people/{id}` | `get_person` |

Cite a quote by its `url` and its `cite` line, with the speaker and the day. A key gets at most 20 different quotes from one episode a UTC day: see [Keys and limits](https://docs.poddata.ai/keys-and-limits.md).

## Follow a topic or a person

A tracker follows what a sentence describes, such as "CEOs on power limits for data centers", and sends each new quote it matches.

1. **Preview it.** See what the sentence would have caught in the last 90 days, before making it:

   ```bash theme={null}
   curl -s -X POST https://api.poddata.ai/v1/trackers/preview \
     -H "Authorization: Bearer $PODDATA_API_KEY" -H 'Content-Type: application/json' \
     -d '{"sentence": "CEOs on power limits for data centers", "days": 30}'
   ```

   A team has 60 previews a UTC day.

2. **Show the person what it caught,** and change the sentence until they're happy with it.

3. **Make it,** with a `name`:

   ```bash theme={null}
   curl -s -X POST https://api.poddata.ai/v1/trackers \
     -H "Authorization: Bearer $PODDATA_API_KEY" -H 'Content-Type: application/json' \
     -d '{"name": "Data center power", "sentence": "CEOs on power limits for data centers", "email": "off"}'
   ```

4. **Read what it matches** with `GET /trackers/{id}/matches`, or every tracker's together with `GET /matches`. Mark a wrong one with `POST /matches/{id}/feedback`, and the tracker learns from it.

A match reaches the team by Slack, Microsoft Teams or a [webhook](https://docs.poddata.ai/webhooks.md). A tracker's email is by request today. A plan sets how many trackers a team may have running: see [Keys and limits](https://docs.poddata.ai/keys-and-limits.md).

| To | Route | MCP tool |
| - | - | - |
| Preview a sentence | `POST /trackers/preview` | `preview_tracker` |
| Make a tracker | `POST /trackers` | `create_tracker` |
| List or open trackers | `GET /trackers` | `list_trackers` |
| Change or pause one | `PATCH /trackers/{id}` | `update_tracker` |
| Delete one | `DELETE /trackers/{id}` | `delete_tracker` |
| A tracker's matches | `GET /trackers/{id}/matches` | `tracker_matches` |
| Every tracker's matches | `GET /matches` | `list_matches` |
| Say a match is wrong | `POST /matches/{id}/feedback` | `not_this` |

An assistant asks the person before it makes, changes or deletes a tracker.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.