{ "markdown": "

Proofable

\n\n

\n Portable Trust Infrastructure for Humans and AI.\n

\n\n

\n Portable Proof carries verified identity, authority, and action evidence across apps, agents, and networks.\n

\n\n

\n Verify once. Prove everywhere.\n

\n\n

\n \"@neus/sdk\n \"@neus/mcp-server\n \"License\"\n \"Discussions\"\n \"NEUS\n

\n\n

\n Why Proofable | Choose a path | Live surfaces | Support\n

\n\n---\n\n## Why Proofable\n\nEvery 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.\n\nRuntime 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.\n\n**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.\n\n| Need | What you get |\n| ---- | ------------- |\n| Reuse a completed check | A proof with source, status, scope, and expiry |\n| Sell protected access | Checks, price, hosted checkout, and a server confirmation |\n| Set limits on an agent | Owner, spend account, allowed and denied actions, revocation |\n\nProofable 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.\n\n## Choose a path\n\nAdd the hosted MCP remote, then click **Connect**.\n\n`https://mcp.neus.network/mcp`\n\nThen ask:\n\n> Reuse what I already have. Before a sensitive action, check my current proofs.\n\nProofable answers **Passed**, **Action needed**, or **Blocked**. Full steps: [MCP setup](https://docs.neus.network/mcp/setup).\n\n| Path | Next step |\n| ---- | --------- |\n| Chat, IDE, or job runtime | [Connect Proofable](https://docs.neus.network/mcp/setup) |\n| App | [Hosted sign-in](https://docs.neus.network/cookbook/auth-hosted-verify) |\n| List on Proofable | [Connect Proofable](https://docs.neus.network/mcp/setup#list-and-sell) |\n| Embed a gate | [Sell access](https://docs.neus.network/quickstart) |\n| Agent limits | [Agents](https://docs.neus.network/agents/overview) |\n\n---\n\n## Live surfaces\n\n| Surface | Use it for |\n| ------- | ---------- |\n| [Product](https://neus.network) | Profiles, gates, and hosted product UX |\n| [Hosted sign-in](https://neus.network/verify) | Browser verification for people and orgs |\n| [Proofs](https://docs.neus.network/platform/proofs) | Portable records of identity, authority, and outcomes |\n| [SDK](https://docs.neus.network/sdks/javascript) ([@neus/sdk](https://www.npmjs.com/package/@neus/sdk)) | Issue, poll, and check proofs from your app |\n| [Widgets](https://docs.neus.network/widgets/overview) | `VerifyGate` and `ProofBadge` for React products |\n| [API](https://docs.neus.network/api/overview) | Server reads, checks, verifier catalog, and verification endpoints |\n| [Agents](https://docs.neus.network/agents/overview) | Agent identity, permissions, and proof history |\n| [MCP](https://docs.neus.network/mcp/overview) | Profile, checks, proofs, and permissions in any MCP client. Registry metadata: [`@neus/mcp-server`](https://www.npmjs.com/package/@neus/mcp-server) |\n| [Examples](./examples) | Runnable app and agent samples |\n| [Verifier catalog](https://docs.neus.network/verification/verifiers) | Live check IDs and inputs |\n\n## Capability snapshot\n\nThe live verifier catalog is documented at [docs.neus.network/verification/verifiers](https://docs.neus.network/verification/verifiers). JSON Schemas live in [`docs/verifiers/schemas/`](./docs/verifiers/schemas/); the machine index is [`spec/VERIFIERS.json`](./spec/VERIFIERS.json).\n\n| Capability | Verifiers |\n| ---------- | --------- |\n| Ownership and identity | `ownership-basic`, `ownership-social`, `ownership-dns-txt`, `ownership-org-oauth`, `ownership-pseudonym` |\n| Human and wallet trust | `proof-of-human`, `wallet-risk`, `wallet-link` |\n| Assets and contracts | `token-holding`, `nft-ownership`, `contract-ownership` |\n| Content and safety | `ai-content-moderation` |\n| Agent trust | `agent-identity`, `agent-delegation` |\n\n## This repository\n\nPublic docs, SDK (`@neus/sdk`), MCP registry package (`@neus/mcp-server`), widgets, examples, specs, and the **`neus-mcp`** plugin ([setup](https://docs.neus.network/mcp/setup)).\n\n## Open standard\n\nProofable is a reference implementation of [CAIP-380 (Portable Proof)](https://standards.chainagnostic.org/CAIPs/caip-380) ([PR](https://github.com/ChainAgnostic/CAIPs/pull/380)), 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](https://docs.neus.network/learn/standards), the [offline examples](./examples/caip-380), the [CAIP-380 docs](https://docs.neus.network/learn/standards/caip-380), and the [Technical Whitepaper](https://docs.neus.network/whitepaper).\n\n## Support\n\n| Channel | Use for |\n| ------- | ------- |\n| [Docs](https://docs.neus.network) | Product and integration guidance |\n| [Changelog](./CHANGELOG.md) | Release notes and upgrade paths |\n| [Platform](https://docs.neus.network/platform/overview) | Hosted product, API, and upgrade path |\n| [Discussions](https://github.com/neus/network/discussions) | Questions and implementation patterns |\n| [Issues](https://github.com/neus/network/issues) | Bugs and requests |\n| [SECURITY.md](./SECURITY.md), [dev@neus.network](mailto:dev@neus.network) | Vulnerability disclosure |\n\n## Status\n\nProofable is under active development. Published APIs and verifier schemas may change between minor versions. Breaking changes are listed in the [changelog](./CHANGELOG.md).\n\n## Audit\n\nSmart contracts were audited by [SafeStack AI](https://safestackai.com) in March 2026. The audit completed with no critical, high, medium, or low severity findings. See the [Trust Center](https://neus.network/trust-center#smart-contract-audit) for details.\n\n## Partners and programs\n\n- **Webacy, ZKPassport, Phala Network:** integration partnerships for verification, zero-knowledge identity, and confidential compute\n- **NVIDIA Inception:** early-stage AI startup program\n- **Google for Startups:** cloud and AI startup program\n- **Optimism Retro Funding Season 8:** grant recipient\n\n## License\n\nAll 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](./TRADEMARKS.md).\n", "bytes": 9065, "sha": "56fefbc1dd87e7146a0235f3146b108201c4b101e2cc17cfe61e62af27acf20f", "repo_slug": "neus/network", "fonte": "repo", "truncated": false, "api": "https://agentalog.com/api/listings/plg_neus_network_neus_trust_6cd89ac3/readme" }