Logs

Logs explain an individual request: its original target, selected provider/model, timing, outcome, and accounted usage. Investigate failed routes or reconcile estimated costs with completed requests.

Dashboard

1. Open Logs.
2. Use the available request filters.
3. Open a request.
4. Review its route, status, timing, tokens, cost, and guardrail result.

Request details also show request characterization, such as intent and complexity, when available.

Request bodies appear only when payload storage was enabled and access is allowed. Enabling storage does not recover older bodies.

Hosted classification feedback can review and correct a request classification. This does not automatically retrain a model.

API

Use an appropriately scoped API key for these requests.

List recent requests

curl 'https://api.anchorshell.com/api/relay/logs/requests?limit=20&offset=0' \
  -H 'Authorization: Bearer <API_KEY>'

Response — 200 OK

Selected response fields shown; IDs and values are illustrative.

{
  "items": [
    {
      "request_id": "<REQUEST_ID>",
      "incoming_model": "agentic",
      "selected_upstream_model": "gpt-5-mini",
      "status_code": 200,
      "task_state": "completed",
      "wait_ms": 0
    }
  ],
  "total": 1,
  "limit": 20,
  "offset": 0,
  "next_offset": 1,
  "has_more": false
}

Inspect one request

curl 'https://api.anchorshell.com/api/relay/logs/requests/<REQUEST_ID>' \
  -H 'Authorization: Bearer <API_KEY>'

Response — 200 OK

Selected response fields shown; IDs and values are illustrative.

{
  "request_id": "<REQUEST_ID>",
  "incoming_model": "agentic",
  "selected_upstream_model": "gpt-5-mini",
  "status_code": 200,
  "task_state": "completed",
  "wait_ms": 0
}

Use the returned request_id, not the row's id. Results require the corresponding self/organization log permission.

Next

Playground.