Choose an integration path
Three drop-in paths cover most products. Pick the one that matches what you are building.Gate an app or marketplace
Publish a portal, embed VerifyGate, reuse receipts at checkout.
Connect an assistant
One command:
neus setup — same account and receipts in Cursor, Claude Code, Codex, and VS Code.Check agents before action
Agent identity and permission receipts a runtime can check before tools run.
What NEUS handles
| Job | What you ship | Where to start |
|---|---|---|
| Access without rebuilding KYC/OAuth | Hosted Verify + published gate | Quickstart · Create a portal |
| Assistants that respect limits | MCP with hosted sign-in + verify-or-guide | Install · MCP journeys |
| Agents with scoped authority | Identity + permission receipts | Agent verification |
| Monetize checks | You-pay credits, visitor checkout, or pay-per-call | Pricing · Billing |
Products and use cases
AI agent and assistant permissions
Register an agent, set limits, check them before action in a connected runtime.
Identity and account checks
Passkey, OAuth, social, org, and domain results as reusable receipts.
Access gates and eligibility
Require current receipts before content, memberships, rewards, or API access.
Human and abuse checks
Layer human and account checks so one weak signal is not enough.
Credits and checkout
You pay for checks by default — or charge visitors at the gate.
Reuse across apps
Check → verify → save → reuse — one loop for widgets, API, and MCP.
Core receipt flow
Most integrations follow the same loop: check → verify → save receipt → reuse. See Integration.Build with
Hosted Verify
Hosted sign-in and checks on NEUS — passkey, OAuth, and gates. No wallet UI in your app.
MCP
Connect assistants to receipt checks through one hosted endpoint.
Widgets
Drop-in gates and badges for React.
SDK
Create, check, and reuse receipts from any server or app.
API
Server-side eligibility checks and receipt reads.
Examples
Working reference apps and samples.