# People and KPIs

> Who's in the organization, their job roles, and how your KPIs are tracking.

## People

`GET /v1/people?search=ana` needs `people:read`. It lists active people with their job title, role, manager and teams. Use a person's `id` as `assignee_id` when adding or updating items and tasks.

`GET /v1/job-roles` lists the organization's job roles, who holds each, and how many responsibilities it has.

## KPIs

With `kpis:read`, a key sees the KPIs its owner can see in the app.

```bash
curl https://developers.playbookops.ai/v1/kpis \
  -H "Authorization: Bearer $PLAYBOOKOPS_API_KEY"

curl "https://developers.playbookops.ai/v1/kpis/KPI_ID/values?since=2026-01-01&until=2026-06-30" \
  -H "Authorization: Bearer $PLAYBOOKOPS_API_KEY"
```

Each KPI has a `unit`, a `frequency`, a `goal`, and a `goal_direction` of `above` or `below`, saying which side of the goal is on track. Values come one per period, with the `period_start` date and any note.

> **Weekly KPI digest**
> List the KPIs, fetch the last two values of each, and compare them with `goal` and `goal_direction` to post which ones are on track and which are slipping.

## Reference

| Action | Endpoint | MCP tool |
| --- | --- | --- |
| People | `GET /v1/people` | `list_people` |
| Job roles | `GET /v1/job-roles` | `list_job_roles` |
| KPIs | `GET /v1/kpis` | `list_kpis` |
| KPI values | `GET /v1/kpis/{id}/values` | `get_kpi_values` |

Every parameter is in the API reference under [People](https://developers.playbookops.ai/reference/people) and [KPIs](https://developers.playbookops.ai/reference/kpis).
