Get it into whatever you already use.
In the app, out as a file, or straight into your warehouse, your BI tool, and your AI assistant over MCP.
In the app
Map, group directory, DVM directory, watchlists, trends, and Ask Terminal. Nothing to install.
Out as a file
Filtered CSV for target lists, CRM loads, and board decks. Filter first, export what you actually need.
Straight into your stack
REST API and an MCP server, so Terminal answers questions inside the tools your team already has open.
Works inside Claude and ChatGPT.
Terminal speaks Model Context Protocol, so your own assistant can query the market directly and cite the rows it used.
| Tool | What it returns |
|---|---|
| search_practices | Practices matching ownership, geography, size, services, or software |
| get_practice | The full record for one practice, every field with its source |
| get_changes | A dated feed of what changed, scoped to what you track |
| ask_terminal | A plain-English question answered against the whole dataset |
| region_summary | Market structure for a state, metro, or radius |
| dvm_lookup | A veterinarian, their licences, and where they work |
| list_watchlists | The accounts and markets your team is already watching |
A stable ID, so it joins to what you have.
Every practice carries a durable identifier that does not change when the practice is renamed, rebranded, or acquired. Load it once into your warehouse and your join keeps working.
- WarehouseLand the full table in Snowflake, BigQuery, or Postgres and refresh on your own schedule.
- BIPoint Looker, Power BI, or Tableau at the same table your team already trusts.
- Your CRMExport matched rows and load them with your existing pipeline.
- Your agentsGive an internal assistant read access over MCP instead of a stale export.