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

# Integration

> Where browser, server, and assistant code run in the NEUS trust loop.

Every integration follows the loop in [Trust stack](./platform/trust-stack#the-loop). Terms: [Get started](./get-started).

The same trust receipt works in a React widget, a server gate, an MCP assistant, or a partner app — because the **receipt** is the trust context, not a session flag in your database.

## Where code runs

| Layer     | Use                                                            |
| --------- | -------------------------------------------------------------- |
| Browser   | `VerifyGate`, `getHostedCheckoutUrl`, hosted `/verify`         |
| Server    | `gateCheck` with `gateId`                                      |
| Assistant | NEUS MCP — reuse receipts before action ([Install](./install)) |

Passkey, wallet, and OAuth flows should run on NEUS hosted pages by default. Do not ship access keys or server secrets in browser bundles.

Backend receipt creation and access keys: [Integrations](./cookbook/integrations).

## Integration options

<CardGroup cols={2}>
  <Card title="Hosted Verify" icon="shield-check" href="./cookbook/auth-hosted-verify">
    Browser flow owned by NEUS.
  </Card>

  <Card title="SDK" icon="code" href="./sdks/javascript">
    JavaScript helpers for app and server flows.
  </Card>

  <Card title="VerifyGate" icon="square-check" href="./widgets/verifygate">
    React access gates.
  </Card>

  <Card title="Agents" icon="robot" href="./agents/agent-verification-flow">
    Agent identity and permissions.
  </Card>
</CardGroup>

Receipt fields and URLs: [Receipts and results](./platform/receipts-and-results).

**Next:** [Quickstart](./quickstart) · [Hosted Verify](./cookbook/auth-hosted-verify)