> ## 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.

# Get started

> Pick your path and set up trust once — drop-in widgets for apps, one command for agents, API for any backend.

Pick your surface — app, agent, or backend. NEUS gives you the same portable trust receipts everywhere.

| You are building                   | Simplest path                                    | Start                                                                                  |
| ---------------------------------- | ------------------------------------------------ | -------------------------------------------------------------------------------------- |
| **Sign-in or access for your app** | Hosted Verify — sign-in or gate checkout on NEUS | [Trust stack](./platform/trust-stack) · [Hosted Verify](./cookbook/auth-hosted-verify) |
| **Gated content or checkout**      | `<VerifyGate>` + one published `gateId`          | [Quickstart](./quickstart)                                                             |
| **An agent or AI workflow**        | One-command MCP setup                            | [Install NEUS](./install)                                                              |
| **A backend in any language**      | HTTP API and server checks                       | [API overview](./api/overview)                                                         |

## Apps: drop-in widgets

`VerifyGate` and `ProofBadge` are the lowest-friction way to ship trust. Your app never implements verifier logic — the gate owns the checks, pricing, and checkout.

<Steps>
  <Step title="Publish a gate">
    Sign in at [neus.network](https://neus.network), open your profile → **Portals**, choose the checks visitors must pass, set pricing (you pay by default, or charge visitors), and **Publish**. Copy your `gateId`.
  </Step>

  <Step title="Gate your content">
    ```jsx theme={"dark"}
    import { VerifyGate } from '@neus/sdk/widgets';

    <VerifyGate gateId="gate_your-app-name">
      <ProtectedContent />
    </VerifyGate>;
    ```

    `VerifyGate` reuses an existing receipt, opens Hosted Verify only when one is needed, then renders your content.
  </Step>

  <Step title="Show verified status">
    ```jsx theme={"dark"}
    import { ProofBadge } from '@neus/sdk/widgets';

    <ProofBadge qHash={proof.qHash} showChains />;
    ```

    The receipt ID in API responses is `qHash` — save it if your server needs to look up the receipt later.
  </Step>
</Steps>

End users never need a NEUS account or API key. To confirm eligibility on your server before trusted actions and to use a hosted link instead of React, follow the full [Quickstart](./quickstart).

## Agents and assistants: one command

```bash theme={"dark"}
neus setup
neus check
```

Wires hosted NEUS MCP into Cursor, Codex, VS Code, and Claude Code. Then ask your assistant: **"Use NEUS Verify before taking sensitive actions."**

Codex only: `neus setup --client codex`, then `neus auth --client codex`.

Details: [Install NEUS](./install) · [Agent verification flow](./agents/agent-verification-flow)

## Backends: API and access keys

Use the HTTP API from servers, workers, and CI — never from end-user browsers. Eligibility, reads, and verification all return the same trust receipt ID (`qHash`). Server automation uses a profile access key from **Profile → Keys** (`npk_*`).

Details: [API overview](./api/overview) · [Integrations](./cookbook/integrations)

**Next:** [Quickstart](./quickstart) · [Integration](./integration)