---
title: "Take Agent Discovery Turn"
method: POST
path: "/agent/onboarding/discovery/turn"
tags: ["Agents"]
---

# Take Agent Discovery Turn

`POST /agent/onboarding/discovery/turn`

## Request

- Base URL: `https://be.graph8.com/api/v1`
- URL: `https://be.graph8.com/api/v1/agent/onboarding/discovery/turn`
- Auth: HTTP bearer

One conversational turn of the kickoff. THIS ONE COSTS MONEY.

The only route on this surface that makes an LLM call, which is why it is
tiered `billable` and why the app rate-limits it at 20 requests a minute
per organisation - far above a human conversation, far below anything that
shows up on a bill. Over that, the app answers 429 with `Retry-After`.

The model replies AND states what it learned in one forced tool call, so a
message that answers four questions records four fields. Everything it
claims is validated before it is written: a key outside the framework is
dropped, and a `green` with no supporting quote is DOWNGRADED to `amber`
rather than trusted.

The turn writes only to the discovery record. It provisions nothing, calls
no tools, and sends nothing.

There is no `history` parameter and that is deliberate - see the module
docstring.

## Headers

- `Authorization` string, nullable
- `X-Target-Org-Id` string, nullable

## Request body

- DiscoveryTurnRequest: Mirror of `DiscoveryTurnRequest`. There is deliberately NO `history` field, and that is load-bearing rather than an omission. The app removed one: the panel used to keep the transcript in browser state and ship it back on every turn, so a reload destroyed the customer's whole kickoff. The server re-grounds from the durable record instead. A caller-supplied transcript is not something the server can verify, and accepting one here would re-open exactly that hole.
  - `message` string, required
  - `session_id` string, nullable: Canvas session to report into.

## Response `200`

Successful Response

- ApiResponseOnboardingPayload
  - `data` OnboardingPayload, required: An open envelope for an onboarding or discovery result. Open on purpose. Discovery state carries a per-field coverage matrix whose field set is the product's own onboarding questionnaire - it changes as the questionnaire does, and a pinned mirror would silently DROP a field the customer had answered. On a surface whose whole job is "what do we still not know about you", a dropped field reads as an answered question.
  - `pagination` PaginationMeta
    - `page` integer, required: Current page number (1-indexed)
    - `limit` integer, required: Items per page
    - `total` integer, required: Total number of items
    - `has_next` boolean, required: Whether there are more pages
    - `next_cursor` string, nullable: Opaque cursor for the next page; null when there are no more items. Pass it back as the `cursor` query param to fetch the following page without computing page numbers.
    - `total_available` integer, nullable: Search endpoints only: how many records really match, when known. Can be larger than `total`, which is capped at the 10,000 results that can be paged. For company search this is a distinct-company estimate. Null when unknown; absent outside search.
    - `total_is_lower_bound` boolean, nullable: Search endpoints only: true when more records match than `total` shows (the result set is larger than the 10,000 results that can be paged). Absent outside search.
    - `notes` string[], nullable: Search endpoints only: plain-language notes about the result, e.g. that more records match than can be paged, or that a reversed `between` range was put in order.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/graph8/apis/graph8-developer-api.md) · [All operations](https://skmtc.dev/graph8/apis/graph8-developer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/graph8/apis/graph8-developer-api/revisions/2e7cfa0ca921?raw)