---
title: "Get Agent Dispatch Status"
method: GET
path: "/v1/interview/session/{session_id}/agent-dispatch"
tags: ["interview-realtime"]
---

# Get Agent Dispatch Status

`GET /v1/interview/session/{session_id}/agent-dispatch`

Report whether a worker-backed agent claim is pending for this session.

Public (booking/session token), read-only, and deliberately minimal: it
never mutates the run row and never re-requests a session — the client's
visible retry (a fresh token fetch) owns re-dispatching.

## Path parameters

- `session_id` string, required

## Query parameters

- `token` string, nullable

## Response `200`

Successful Response

- AgentDispatchStatusResponse — Read-only agent-dispatch state for the client's first-join wait (A1). While the LiveKit room is up but no agent announced session_ready, the client probes this to decide whether to keep waiting: ``claim_pending`` is True exactly while an agent is still destined for the room (queued request, fresh claim still connecting, or a rerequest marker parked on an active lease — the resume race, where the old runtime's lease outlives its pipeline until after the recording upload). Deliberately minimal (B-P2-5b): this is a PUBLIC participant endpoint, so it exposes exactly the one bit the client's wait decision needs — internal run-status strings stay internal (worker logs/staff surfaces own them).
  - `claim_pending` boolean, required

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/ontora/apis/ontora-api.md) · [All operations](https://skmtc.dev/ontora/apis/ontora-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/ontora/ontora-api/revisions/7f57037fd94b/schema)