neus_proofs_check accepts sponsorGrant for sponsored or higher-limit scans when your setup uses grants.
The assistant chooses tools; you mainly open links they return. For “verify it’s me”, prefer anything that hands you a neus.network/verify URL.
Parameter names
Your client also loads schemas from the server. This table only prevents the common mistake of using the wrong field name:| Tool | Who / address field | Verifier field |
|---|---|---|
neus_proofs_check | wallet | verifiers |
neus_verify_or_guide, neus_verify | walletAddress | verifierIds |
neus_proofs_get | identifier | — |
0x…, Solana base58, or did:pkh:… where applicable.
Suggested tool order
neus_context(public; call first for live verifier catalog and protocol context)neus_verify_or_guide/neus_proofs_checkneus_verifiers_catalog(when you need ids)neus_proofs_get(when you have an id)neus_me(with Bearer only—Auth)- Agent tools when needed
neus_context and steps 2–4 work without Bearer for typical public flows. neus_me and private reads need Authorization: Bearer with your personal access key from Access keys.