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. Home
  2. Get started
  3. Quickstart
  4. Integration
  5. JavaScript SDK
  6. MCP tools
  7. API overview (server and raw HTTP)

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 browser ceremony: 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 · A2A cards
  • Use returned receipt URLs or qHashes only when the API/tool response provides them.

Exports

# Plain text summary (same content as https://neus.network/llms.txt)
curl https://neus.network/llms.txt

MCP JSON

type is client-specific; use http for URL-based hosted MCP.
{
  "mcpServers": {
    "neus": {
      "type": "http",
      "url": "https://mcp.neus.network/mcp"
    }
  }
}
Jump to MCP overview, MCP setup, or the HTTP API when you need detail beyond this reading order.
Last modified on June 8, 2026