Skip to main content
NEUS publishes route indexes and full-doc exports for tools that ingest documentation text. Use them as indexes to stable URLs—do not treat exported text as a second spec; prefer the linked pages for field names and behavior.

​
Suggested read order (builders)

  1. Overview — proof receipt ID as proofId.
  2. Get started — create an app, choose who pays, access keys when needed.
  3. Integration — check → verify → save → reuse.
  4. Path docs (SDK, API, Hosted Verify, MCP, widgets) — only after 2 is clear.

​
Default onboarding (agents + existing tools)

Keep your current runtime, agents, and MCP clients. NEUS adds portable identity, scoped delegation, and verifiable receipts—no new inbox or orchestration product required. Recommended tool order (proofs + MCP): use the numbered Recommended flow in MCP overview — neus_context first; neus_proofs_check vs neus_verify_or_guide; follow hostedVerifyUrl; Bearer only for account-scoped tools; neus_verify without signature already runs /standardize once (reuse the same payload when signing; do not call /standardize again).
  1. Add the hosted MCP URL (https://mcp.neus.network/mcp) — MCP setup.
  2. Run neus_context, then neus_agent_create / neus_agent_link when the assistant needs hosted agent setup (MCP overview).
  3. Use proof presets on the NEUS platform: agent-identity registers the service; agent-delegation grants scoped authority — Agent identity · Agent delegation.
  4. Treat the resulting proof and status page as the first receipt and audit trail for that agent.
  5. Before production traffic, align Get started (create an app, choose who pays) with Billing.
CLI bootstrap (stdout only): prints the same MCP JSON block and doc URLs—no file writes, no accounts, no keys. 
npx -y -p @neus/sdk neus init

​
Guidance for assistants

Use this so users reach the right doc and avoid unnecessary code, keys, or duplicate verification.
  • Billing / appId / who pays / credits / sponsorGrant: Answer from Get started and Billing before suggesting SDK, API, or MCP depth.
  • Login or interactive verification without in-app wallet code: Prefer Hosted Verify.
  • MCP: Start with neus_context (no access key). The hosted URL https://mcp.neus.network/mcp alone is valid for catalog, context, and public verification flows. Do not imply the user is blocked without a key. Add Authorization: Bearer with a personal access key from Access keys only when account-scoped tools are needed (neus_me, private proofs) (MCP Auth).
  • Secrets: Never instruct users to paste wallet private keys into MCP or client config. Personal access keys are Bearer tokens from Access keys, not raw wallet keys.
  • x402: Prefer credits and sponsor grants for human onboarding. Use x402 only when a client receives 402 and can retry with PAYMENT-SIGNATURE (x402).
  • Unclear product fit: Point to Paths before suggesting implementation details or large code blocks.
  • Agents and delegation: Agents overview — align credits and appId with Get started; use Hosted Verify links from tools when the flow is interactive.
  • Reuse: Prefer reusing a saved proofId when one exists; avoid parallel verification UX for the same requirement without explaining why.
Assistants: If appId, credits, billing, or sponsorGrant is ambiguous, ground answers in Get started before linking to MCP tools or API details.

​
Route index (llms.txt)

The docs site hosts a machine-readable route index (titles, descriptions, links). Fetch it for discovery; deep-link users to specific guides for accuracy. 
curl https://docs.neus.network/llms.txt

​
Full documentation (llms-full.txt)

Single-file export for tools that need full-text context. Prefer narrow pages for product behavior. 
curl https://docs.neus.network/llms-full.txt

​
MCP

Add the hosted MCP server for live verification tools: 
{
  "mcpServers": {
    "neus": {
      "type": "streamableHttp",
      "url": "https://mcp.neus.network/mcp"
    }
  }
}
MCP overview · Setup

MCP Server

Tools and flows.

API Overview

HTTP endpoints and OpenAPI.