agent-identity (agent signs) and agent-delegation (approving account signs). Same person or two accounts.
Instead of every app rebuilding agent identity and permissions, NEUS agents carry their own proof.
To bill hosted checks through your product, complete Quickstart (create a portal under profile → Portals). For backend receipt creation after user approval, see Integrations. Agent concepts: Agent concepts
MCP
1
Check
neus_context → neus_agent_link with both agentWallet and agentId. Done if linked: true.2
Create
neus_agent_create when proofs are missing.3
Finish
Follow
next_action. Dedicated wallets sign identity first; the approving account finishes delegation.4
Confirm
neus_agent_link until linked: true.SDK
For a dedicated agent wallet, keep the identity receipt from the agent-signed step, then build a delegation-only hosted callback:
Schemas:
docs/verifiers/schemas/
Agent that pays
To let an agent pay for metered APIs autonomously, give its delegation a spend cap and the payments scope, then let it settle pay-per-call requests:- Delegate with
scope: 'payments:x402',allowedPaymentTypes: ['x402'], and amaxSpendcap — see Agent delegation. - The agent calls your priced endpoint; a
402returns the price. - The agent pays and retries with a
PAYMENT-SIGNATUREheader — full flow in x402 pay-per-call.
maxSpend cap is enforced as a hard limit, so the agent can never exceed its budget.
Related
Agents overview
Start here.
MCP overview
Tool list and auth.