neus setup and neus check, ask your assistant to use NEUS in plain language. It reports the result as Passed, Action needed, or Blocked instead of showing raw tool output.
When you are signed in, account-based tools use your current profile automatically.
Verify before a sensitive action
The default workflow reuses a valid receipt when one fits and runs a new check only when needed. Try: “Use NEUS Verify before taking sensitive actions.”Show your trust receipts
Pull the receipt URL, status, tags, or summary behind any prior check. Try: “Show my trust receipts for identity checks.”Reuse portable context
Tagged receipts carry prior instructions, rules, or session references — so your assistant picks up where you left off without re-asking. Optional linking patterns: Receipt links and versioning. Try: “Use my NEUS context from prior receipts before asking me again.”Trust an agent before it runs tools
Confirm an agent has both identity and approved authority before it acts. Try: “Verify this agent is trusted before it runs tools.”Pay per call within a cap
With apayments:x402 delegation and a maxSpend cap, an agent can settle metered calls on its own — and is refused past the cap.
Try: “Pay for this API call with my x402 delegation, up to the cap.”
Details: x402 pay-per-call.
Store and use secrets safely
Keep tokens in encrypted Vault instead of pasting them into chat. Try: “Use NEUS Vault before storing or using secrets.” Details: Secrets.Tool reference: MCP tools · Install: Install NEUS