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

# Briefed Research

> Research that runs on a schedule and delivers itself: Terminal, Anya, and the Workflows API.

# Briefed Research

Briefed Research is a research platform for investment professionals. It has
three parts:

<CardGroup cols={3}>
  <Card title="Terminal" icon="terminal" href="/research/terminal">
    Run a named research job against a pinned company or peer set, and get back
    a document with every source shown.
  </Card>

  <Card title="Anya" icon="sparkles" href="/research/anya">
    The analyst. Reads the evidence a Terminal run produced and forms a
    judgement about it.
  </Card>

  <Card title="Workflows" icon="repeat" href="/api-reference/workflows/overview">
    The same research on a schedule or an event, delivered where your team
    already works.
  </Card>
</CardGroup>

## What the API covers

Everything lives on one host:

```
https://research-api.briefedmedia.com
```

Two surfaces on it are addressable programmatically, and they are not
substitutes for each other.

**Workflows** is documented here endpoint by endpoint. You can author a
composition, publish it, run it, read its results, and manage its delivery:
everything the web application does, with an API key.

**Anya** has her own API, under `/anya` on the same host, and keeps it. A
workflow can invoke an Anya investigation as a step, but a great deal of what Anya does has no
workflow equivalent at all: universes and positions, cases and handoffs,
beliefs and their revisions, alert rules, calibration and track record. Those
are stateful, conversational, and reviewed by a person. Routing them through a
composition graph would be forcing the wrong shape onto them.

<Note>
  The Anya surface is not yet documented page by page here. It is reachable
  today with a credential carrying the `anya` entitlement. Reference pages
  follow.
</Note>

Terminal is documented as a concept rather than an endpoint, because it is not
separately addressable: you reach it by pinning a job inside a workflow.

<Note>
  Workflows API access requires the **Workflows API** entitlement, available on
  Max and Team plans. Pro accounts can use Workflows through the web
  application.
</Note>

## Start here

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/api-reference/workflows/quickstart">
    Authenticate and run your first workflow.
  </Card>

  <Card title="Authentication" icon="key" href="/api-reference/workflows/authentication">
    API keys, scopes, and what each one permits.
  </Card>
</CardGroup>