Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.terrapinfinance.com/llms.txt

Use this file to discover all available pages before exploring further.

A watchlist is a group of CUSIPs and entities you want to monitor, usually because they share a sector, a parent, a portfolio, or a theme. Watchlists are how you do something across many credits at once: attach an assignment and the platform runs it against every entity for you.

​
The watchlist page

Watchlists (/munis/watchlists) is a 3-pane layout:
  • Left sidebar: your watchlists. Click to open. Hover to rename or delete.
  • Centre pane: the resolved entities and CUSIPs on the selected watchlist.
  • Right pane: the assignments attached, plus the events those assignments have produced.

​
Creating a watchlist

From the left sidebar:
1

Name the watchlist

Pick a name that makes its purpose obvious. For example, “Texas hospitals”, “Charter schools 2024 originations”, “Toll roads tear sheet”.
2

Paste CUSIPs or entity names

Drop one or more CUSIPs (or full obligor names) into the CUSIPs/entities field, comma- or newline-separated.
3

Submit

The platform resolves each input to an obligor, dedupes against entities already on the list, and surfaces anything it couldn’t recognise so you can correct it.

​
Adding more CUSIPs later

On the watchlist detail page, click Add CUSIPs. The same resolution and validation rules apply.

​
What you can do with a watchlist

A watchlist by itself is just a list. To make it useful, attach one or more assignments. The assignment defines what the platform should do across the watchlist’s entities. Three assignment types are available:
  • Prompt Template: run a saved prompt template for every entity (e.g. tear sheets).
  • Document Publication: emit an event each time a new disclosure is published for any entity in the watchlist, with an AI-generated summary attached.
  • Price Update: emit an event each time a bond in the watchlist trades.
Events show up on the watchlist detail page and in the global Surveillance feed.

​
One watchlist, one purpose

Watchlists are cheap to create. You’ll get more out of them by keeping one per workflow rather than mixing several use cases into one big list: for example, one watchlist for “tear sheets across all my Texas hospitals” and a separate one for “track new disclosures on my high-yield names”.

​
See also

  • Assignments: every assignment type and its parameters.
  • Surveillance: the cross-watchlist event feed.
  • Data Tables: comparable metrics across the entities in a watchlist.