docs.neus.network) is the standard integration reference. Follow the order below so fields, tools, and billing context stay consistent.
Read first
- Get started — pick app, assistant, agent, or backend
- Quickstart (apps) or Install (assistants)
- Trust stack — loop and architecture
- 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).
- Install: Install NEUS —
neus setup→neus check - Session flow: MCP overview — reuse receipts before new verification
- Example prompts: MCP journeys
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 callapi.neus.networkfrom 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 insidemcpServers and discovers OAuth from the server’s 401 challenge:
type: "http":