Skip to main content
NEUS records completed identity, ownership, risk, and permission checks as trust receipts. Connected systems can check a receipt’s current status, scope, and expiration before access, payment, or another sensitive action. Create a receipt once, then reuse it where an integration accepts the same check. Your NEUS profile shows the receipts and agents associated with your account. You control which supported receipts are public. NEUS is a portable trust layer. It connects the authentication systems, verification providers, wallet tools, payment processors, policy engines, and agent runtimes you already use. Those systems keep doing their jobs; NEUS carries an accepted result into the next connected gate.

​
Choose an integration path

Two drop-in paths cover most products. Pick the one that matches what you are building.

Add receipt checks to an app

Require specific receipts before content, rewards, or checkout.

Add identity and permissions to an agent or assistant

Register an agent or assistant and grant limits that its connected runtime can check before action.

​
Products and use cases

Identity verification and authorization

Carry accepted identity, organization, ownership, and permission results into connected access decisions.

Access control and eligibility

Require current receipts before content, memberships, rewards, API access, or checkout.

AI agent and assistant permissions

Register an agent or assistant, connect its controller, and set limits a supported runtime checks before action.

Wallet risk and human checks

Reuse accepted proof-of-human and wallet-risk receipts across connected flows.

Payments and payouts

Combine receipt requirements with checkout, credits, sponsored access, or supported x402 flows.

Partner handoffs and review

Preserve the decision record another connected system needs without restarting the full check.
Use NEUS across AI and automation, fintech and payments, marketplaces, communities, wallet products, SaaS, and partner ecosystems. Browse solutions for industry examples.

​
Core receipt flow

Most integrations follow the same loop: check → verify → save receipt → reuse. See Integration. Advanced: metered API billing (x402) · Plans and credits

​
Build with

Widgets

Drop-in gates and badges for React — no backend required.

SDK

Create, check, and reuse receipts from any server or app.

Hosted Verify

NEUS handles the browser step — passkey, wallet, and OAuth.

API

Server-side eligibility checks and receipt reads.

MCP

Connect supported assistants to receipt checks through one hosted endpoint.

Examples

Reference apps and samples.
Last modified on July 10, 2026