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

# Automations

> The unified API model for running workflows and agents.

An **automation** is the thing you can run through the API or SDK. It can be
implemented by a [workflow](/concepts/workflows) or by a Git-backed
[agent](/concepts/agents), but callers use one run surface:

```bash theme={null}
POST /api/v1/runs
```

Use automation targets when you start runs:

```text theme={null}
workflows.<slug>
agents.<slug>
```

The prefix matters because workflow and agent slugs can overlap. You can also
use stable ids returned by the API, such as `wf_...` for workflows.

## Why the API says automation

The dashboard has workflows and agents because they are authored differently.
The public API groups them as automations because they share the same runtime
shape:

* both can be listed with `GET /api/v1/automations`
* both can be run with `POST /api/v1/runs`
* both produce runs, files, traces, reviews, and evaluator scores
* both can have datasets and experiments

Use workflow or agent docs when you are authoring behavior. Use automation docs
when you are integrating with that behavior from code.

Once an automation is running in production, use [Reviews](/concepts/reviews) to
record human feedback and [Review production runs](/guides/review-runs) to close
the loop from a bad run to a verified fix.