Skip to main content
First call: run neus_context after you connect. One response covers verifier context, billing model, and protocol rules. No access key required. Follow this order unless you have a specific reason not to:
  1. neus_context — Live verifier IDs, hub hint, billing hints, constraints (no access key).
  2. Check — neus_proofs_check(wallet, verifiers) for yes/no eligibility only (no browser). Prefer neus_verify_or_guide when the user may need a browser, passkey, or onboarding.
  3. Hosted verify — If a tool returns hostedVerifyUrl, open it (https://neus.network/verify); do not substitute a different URL.
  4. Proof list — neus_proofs_get(identifier) for proof records + profile summary.
  5. Account / private vault — Add Authorization: Bearer (personal access key from Access keys) only when you need neus_me or private reads. See Auth.
  6. Programmatic signing — neus_verify without signature triggers one server /standardize step and returns signerString + hostedVerifyUrl. On the signed follow-up, reuse the same walletAddress, verifierIds, data, signedTimestamp, and chain; you do not call /standardize again. Response may include sigVersion / bodyPreview for signing parity.
  7. Agents (advanced) — neus_agent_create → complete hosted steps → neus_agent_link to confirm.
If the API returns 402, follow Billing and x402 (retry with PAYMENT-SIGNATURE when your client supports it). Summary: the hosted MCP URL covers public catalog, context, and hosted verify handoffs without a key. Add Authorization: Bearer (personal access key from Access keys) only for neus_me, private reads, or debiting your credits — Auth. For appId, payer model, and keys before scale: Get started · Billing · Setup. https://mcp.neus.network/mcp

​
Workflow

Add the MCP endpoint once in your client—see Setup for URL-only and authenticated configuration blocks.
  1. neus_context — load live verifier catalog and protocol context (public).
  2. Browser verify: assistant runs neus_verify_or_guide or neus_proofs_check. User opens https://neus.network/verify from the tool. Passkey or wallet stays in NEUS (no pasted one-time codes in MCP).
  3. Signed-in assistant: add Bearer with your personal access key, then neus_me when you need the current principal. Auth
  4. Proof history: when you already have an address or id, neus_proofs_get. Tools
GoalTool
Verifiers, billing model, protocol rules (call first)neus_context
Send someone to browser verificationneus_verify_or_guide
Yes/no eligibility onlyneus_proofs_check
Proof list + profile (you have an id)neus_proofs_get
Signed-in “who am I”neus_me · Bearer · Auth
Pick verifier IDs safelyneus_verifiers_catalog
Agentsneus_agent_create, neus_agent_link
Open hosted URLs from tools.

​
Agents

  1. neus_agent_create → open any hosted URL returned → neus_agent_link to confirm.

​
Next

  • Get started — onboarding and billing before scale
  • Setup — URL-only and authenticated configuration
  • Tools — parameter names
  • Auth — sessions and privacy
  • Hosted Verify — browser verification flow