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

# Integrations and reference

> Connect supported agent harnesses, SDKs, CLIs, and the HTTP API.

Choose the integration closest to where your agent already runs.

<Columns cols={2}>
  <Card title="Agent harnesses" icon="plug-zap" href="/reference/harnesses">
    Install hooks for supported coding and autonomous agent CLIs.
  </Card>

  <Card title="Custom agents" icon="python" href="/reference/python-sdk">
    Instrument traces to find failures in custom agents, then contact us to add prevention to your runtime.
  </Card>

  <Card title="Local dashboard" icon="monitor-cog" href="/reference/local-dashboard">
    Review local projects, sessions, policy activity, and offline audits.
  </Card>

  <Card title="Failproof AI CLI" icon="terminal" href="/reference/failproof-cli">
    Configure local capture, hooks, policies, audits, delivery, and machine state.
  </Card>

  <Card title="Failproof Cloud CLI" icon="cloud-cog" href="/reference/cloud-cli#cli-commands">
    Query and administer Cloud sessions, audits, issues, alerts, keys, users, and settings.
  </Card>

  <Card title="Evaluator SDK" icon="gauge" href="/reference/evaluator-sdk">
    Score complete or inactive sessions with a FastAPI service.
  </Card>

  <Card title="Custom policies" icon="shield-plus" href="/reference/policy-sdk">
    Author and test workflow-specific allow, instruct, and deny decisions.
  </Card>

  <Card title="Self-hosting" icon="cloud-cog" href="/reference/self-hosting">
    Deploy the Cloud control plane on a customer-managed Kubernetes cluster.
  </Card>
</Columns>

The generated [HTTP API reference](/reference/http-api) covers the public `/v1` surface. Hand-written pages explain workflows that span multiple endpoints or use administrative interfaces outside that public surface.

## Connect an agent and verify data

<Tabs>
  <Tab title="Dashboard">
    1. Open **Administration → Keys**, create a key with `events:add` and `policies:pull`, and copy the secret.
    2. Configure the integration using the matching page above.
    3. Open **Observe → Events** to confirm events arrive, then **Observe → Sessions** to confirm they form complete runs.
    4. Filter to the integration's environment and inspect one session for the model, tool, error, and policy fields needed by audits.

    Start with the key drawer. The selected grants determine whether the machine can send events and receive Cloud-managed policies.

    <img src="https://mintcdn.com/exosphere/WgPwQzedeDNwJBTy/images/dashboard/key-create.png?fit=max&auto=format&n=WgPwQzedeDNwJBTy&q=85&s=a428bdae79f837471acb66414ff6455b" alt="The new API key drawer used to grant event ingestion and policy delivery permissions." width="2940" height="1604" data-path="images/dashboard/key-create.png" />

    After connecting the integration, use the Sessions list to confirm that its events are being grouped into complete runs in the expected environment.

    <img src="https://mintcdn.com/exosphere/WgPwQzedeDNwJBTy/images/dashboard/sessions-list.png?fit=max&auto=format&n=WgPwQzedeDNwJBTy&q=85&s=f1fb545746143e87b8b5daedabfc5559" alt="The Sessions list used to verify that a newly connected integration is reporting complete agent runs." width="3200" height="2000" data-path="images/dashboard/sessions-list.png" />

    Open one of these sessions before considering the integration complete; the trace should contain the model, tool, error, and policy evidence your audits need.
  </Tab>

  <Tab title="CLI">
    Create a machine key, connect the Failproof daemon, and verify the first session.

    ```bash theme={null}
    fp keys create agent-production \
      --add events:add \
      --add policies:pull

    failproofai config \
      --connect https://app.befailproof.ai \
      --token <machine-key>

    failproofai flush --wait
    fp sessions --since 1h --env production
    fp events --since 1h --env production --limit 20
    ```

    Use `fp --json sessions ...` when another tool will consume the result. Global flags such as `--json`, `--org`, and `--base-url` must come before the command.

    See the [Failproof AI CLI reference](/reference/failproof-cli) for local commands and the [Failproof Cloud CLI reference](/reference/cloud-cli#cli-commands) for `fp` commands.
  </Tab>
</Tabs>