---
title: "Admin Intent Segments"
method: GET
path: "/admin/intent-segments"
---

# Admin Intent Segments

`GET /admin/intent-segments`

## Request

- Base URL: `https://api.local-mcp.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.local-mcp.com/admin/intent-segments`
- Auth: none declared. Required headers: `x-admin-key`

Segment the fleet by Job-To-Be-Done from aggregate per-tool telemetry.

~92% of tool usage is local stdio (no call sequence — see /admin/cloud-detail
for the thin cloud-relay sample), so real journeys can't be reconstructed.
What we CAN do is map each machine's TOOL BASKET (over the window) through the
JTBD taxonomy to answer "what are users trying to accomplish". Volume comes
from tool_call_events (summed per machine+tool over the window). Meta/plumbing
JTBDs (System & setup) are excluded from intent segmentation unless
include_meta=true. Unmapped tools are surfaced so the taxonomy stays honest.

## Query parameters

- `days` integer
- `include_meta` boolean

## Headers

- `x-admin-key` string, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/local-mcp/apis/lmcp-api.md) · [All operations](https://skmtc.dev/local-mcp/apis/lmcp-api/llms.txt) · [OpenAPI document](https://skmtc.dev/local-mcp/apis/lmcp-api/revisions/f1f1c502623a?raw)