> ## Documentation Index
> Fetch the complete documentation index at: https://docs.proofable.me/llms.txt
> Use this file to discover all available pages before exploring further.

# LLM and agent docs

> Machine-readable entry points, MCP setup, and the shortest reading order.

Start with the smallest source that answers the task. Use the text export for model context and the linked reference page for exact fields.

## Read first

1. [Home](/) — hosted MCP endpoint, then Connect
2. [Connect Proofable](../mcp/setup) — chat, IDEs, jobs, listings, and proofs
3. [Agent setup](../agents/agent-verification-flow) to set identity and permissions
4. [MCP tools](../mcp/tools) for exact tool behavior
5. [Trust](../verification/overview) for checks and reusable proofs
6. [Standards & interoperability](../learn/standards) for how Proofable uses existing protocols

## MCP

**Product server:** `https://mcp.proofable.me/mcp` for profile, proofs, listings, permissions, agents, and private context.
**Not the product:** `https://docs.proofable.me/mcp` for documentation search only (Mintlify).

1. Register `https://mcp.proofable.me/mcp` in the host (marketplace, registry, or URL-only config).
2. Click **Connect** in the host.
3. Follow [Connect Proofable](../mcp/setup) and the [MCP workflow](../mcp/overview). Reuse proofs before you verify again.

Profile access keys (`npk_*`) are for servers and CI only.

## Rules

* **Browser → Proofable:** SDK (`ProofableClient`, widgets) or **Hosted Verify**. Do not call `api.proofable.me` from the browser with secrets or ad-hoc headers; use a **server proxy** when you need custom server-side calls.
* **Server → Proofable:** `gateCheck`, eligibility, secrets, raw HTTP. [API overview](../api/overview)
* Profiles, agents, listings, gates, and proofs: [Ecosystem](../platform/overview)
* Default hosted sign-in: [Hosted Verify](../cookbook/auth-hosted-verify). Optional in-app signing: [Signing format](../verification/signing-format)
* Do not use wallet **private keys** as MCP credentials. Sign in with **OAuth** or use **Profile access keys** (`npk_*`) for Bearer in MCP or server config only.
* **402:** use the x402 retry pattern
* Agents: [Overview](../agents/overview), [Agent setup](../agents/agent-verification-flow), [Discover agents](../agents/named-agent-card)
* Use returned proof URLs or qHashes only when the API/tool response provides them.

## Exports

```bash theme={"dark"}
# Page index for discovery
curl https://docs.proofable.me/llms.txt

# Full documentation context
curl https://docs.proofable.me/llms-full.txt
```

## MCP JSON

Hosts that omit the spec `type` field (including Cursor) use a URL-only entry inside `mcpServers` and discover OAuth from the server's 401 challenge:

```json theme={"dark"}
{
  "mcpServers": {
    "proofable": {
      "url": "https://mcp.proofable.me/mcp"
    }
  }
}
```

Hosts that require the spec `type` field use `type: "http"`:

```json theme={"dark"}
{
  "mcpServers": {
    "proofable": {
      "type": "http",
      "url": "https://mcp.proofable.me/mcp"
    }
  }
}
```

Jump to [MCP overview](../mcp/overview), [MCP setup](../mcp/setup), or the [HTTP API](../api/overview) when you need detail beyond this reading order.