---
title: Support
description: "How to get help with looot: what to quote, where to ask, and how to request a missing provider."
---

## What to quote

Every error and every run carries ids that let anyone find exactly what happened:

- **`requestId`**, from the error object of any failed request (CLI stderr, a REST `error.requestId`,
  or an MCP tool's `structuredContent.data.requestId`). See [Errors](/errors) for where each
  surface puts it.
- **`runId`**, for a run itself, whether it succeeded, failed, or is stuck `queued` or `running`.
  `looot runs get <run-id>` or MCP [`runs_get`](/mcp-tools/runs-get) shows its current state; [`runs_evidence`](/mcp-tools/runs-evidence) shows every
  attempt with the provider's own response status, latency, receipt id and cost.

Quoting both, plus the command or tool call you made, is normally enough for someone else to find
the exact request without you having to describe it.

## Where to ask

Use the contact page at [looot.ai/contact](https://looot.ai/contact).

## A provider or endpoint you need isn't in the catalog

Don't wait on a support thread for this one: ask for it directly.

**MCP**

Call the `capability_request` tool with a `title`, a `description` of what you need it to do,
and optionally `desiredInputs`/`desiredOutputs`.

**REST**

`POST /v1/capability-requests` with the same fields.

See [Capability request](/mcp-tools/capability-request).

## Checking or fixing a token

Settings, Agent tokens, on looot.ai lists every token issued for your organization: which client
it belongs to, its scopes, and its status (active or revoked). Revoke one from there if it looks
wrong, then sign in again from the affected client. See [Sign in](/get-started/sign-in) and
[Connect your agent](/connect) for how each client authenticates.

<Related />