Skip to main content
This site (docs.neus.network) is the standard integration reference. Follow the order below so fields, tools, and billing context stay consistent.

Read first

  1. Get started — pick app, assistant, agent, or backend
  2. Quickstart (apps) or Install (assistants)
  3. Trust stack — loop and architecture
  4. MCP tools or API overview as needed

MCP for assistants

Product server: https://mcp.neus.network/mcp — identity, proofs, delegation, verify.
Not the product: https://docs.neus.network/mcp — documentation search only (Mintlify).
  1. Install: Install NEUSneus setupneus check
  2. Session flow: MCP overview — reuse receipts before new verification
  3. Example prompts: MCP journeys
Use neus auth for OAuth. Profile access keys (npk_*) are for servers and CI only.

Rules

  • Browser → NEUS: SDK (NeusClient, widgets) or Hosted Verify. Do not call api.neus.network from the browser with secrets or ad-hoc headers; use a server proxy when you need custom server-side calls.
  • Server → NEUS: gateCheck, eligibility, secrets, raw HTTP — API overview
  • Account, gates, and billing: Get started
  • Default hosted sign-in: Hosted Verify. Optional in-app signing: 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 · Verification flow · Discover agents
  • Use returned receipt URLs or qHashes only when the API/tool response provides them.

Exports

MCP JSON

Cursor uses a URL-only entry inside mcpServers and discovers OAuth from the server’s 401 challenge:
VS Code, Claude Desktop, and other spec-compliant hosts use type: "http":
Jump to MCP overview, MCP setup, or the HTTP API when you need detail beyond this reading order.
Last modified on July 14, 2026