Portable Trust Infrastructure for Humans and AI.
Portable Proof carries verified identity, authority, and action evidence across apps, agents, and networks.
Verify once. Prove everywhere.
Why Proofable | Choose a path | Live surfaces | Support
Every app, agent, and marketplace rebuilds identity, ownership, and permission checks from zero. Proofable saves the accepted result as a Portable Proof any connected product can check under its own rules — so trust moves instead of restarting.
Runtime guardrails check the agent inside one runtime. Proofable makes the result portable: the same proof checks at your gate, another vendor's tool, or a partner's checkout.
Set limits on an AI agent. Record who controls it, what it may do, spend cap, expiry — as a proof a connected runtime checks before action. No authority. No action.
| Need | What you get |
|---|---|
| Reuse a completed check | A proof with source, status, scope, and expiry |
| Sell protected access | Checks, price, hosted checkout, and a server confirmation |
| Set limits on an agent | Owner, spend account, allowed and denied actions, revocation |
Proofable does not replace your authentication, policy engine, payment processor, agent runtime, or audit logs. Your integration calls the check and enforces the result on the protected path.
Add the hosted MCP remote, then click Connect.
https://mcp.neus.network/mcp
Then ask:
Reuse what I already have. Before a sensitive action, check my current proofs.
Proofable answers Passed, Action needed, or Blocked. Full steps: MCP setup.
| Path | Next step |
|---|---|
| Chat, IDE, or job runtime | Connect Proofable |
| App | Hosted sign-in |
| List on Proofable | Connect Proofable |
| Embed a gate | Sell access |
| Agent limits | Agents |
| Surface | Use it for |
|---|---|
| Product | Profiles, gates, and hosted product UX |
| Hosted sign-in | Browser verification for people and orgs |
| Proofs | Portable records of identity, authority, and outcomes |
| SDK (@neus/sdk) | Issue, poll, and check proofs from your app |
| Widgets | VerifyGate and ProofBadge for React products |
| API | Server reads, checks, verifier catalog, and verification endpoints |
| Agents | Agent identity, permissions, and proof history |
| MCP | Profile, checks, proofs, and permissions in any MCP client. Registry metadata: @neus/mcp-server |
| Examples | Runnable app and agent samples |
| Verifier catalog | Live check IDs and inputs |
The live verifier catalog is documented at docs.neus.network/verification/verifiers. JSON Schemas live in docs/verifiers/schemas/; the machine index is spec/VERIFIERS.json.
| Capability | Verifiers |
|---|---|
| Ownership and identity | ownership-basic, ownership-social, ownership-dns-txt, ownership-org-oauth, ownership-pseudonym |
| Human and wallet trust | proof-of-human, wallet-risk, wallet-link |
| Assets and contracts | token-holding, nft-ownership, contract-ownership |
| Content and safety | ai-content-moderation |
| Agent trust | agent-identity, agent-delegation |
Public docs, SDK (@neus/sdk), MCP registry package (@neus/mcp-server), widgets, examples, specs, and the neus-mcp plugin (setup).
Proofable is a reference implementation of CAIP-380 (Portable Proof) (PR), a ChainAgnostic standard at Draft status. Wallet-signed request envelopes use a deterministic SHAKE-256 hash (qHash), CAIP-2 chain context, and CAIP-10 / did:pkh identities. The hash, DID binding, and signature can be checked without Proofable. Verifier outcomes remain part of the Portable Proof. The envelope works with any CAIP-2 namespace and that chain’s native signing scheme. See Standards & interoperability, the offline examples, the CAIP-380 docs, and the Technical Whitepaper.
| Channel | Use for |
|---|---|
| Docs | Product and integration guidance |
| Changelog | Release notes and upgrade paths |
| Platform | Hosted product, API, and upgrade path |
| Discussions | Questions and implementation patterns |
| Issues | Bugs and requests |
| SECURITY.md, dev@neus.network | Vulnerability disclosure |
Proofable is under active development. Published APIs and verifier schemas may change between minor versions. Breaking changes are listed in the changelog.
Smart contracts were audited by SafeStack AI in March 2026. The audit completed with no critical, high, medium, or low severity findings. See the Trust Center for details.
- Webacy, ZKPassport, Phala Network: integration partnerships for verification, zero-knowledge identity, and confidential compute
- NVIDIA Inception: early-stage AI startup program
- Google for Startups: cloud and AI startup program
- Optimism Retro Funding Season 8: grant recipient
All code in this repository is Apache-2.0, including the reference smart contracts. The CAIP-380 specification is released under CC0 1.0. NEUS names and logos are protected trademarks; see TRADEMARKS.md.