Proofable Docs | The portable trust harness for AI

Sign-in, gates, saved results, and agent authority share one account. Do not restart from zero in the next product.

The loop

Step	What happens
1	Look up a saved result
2	Run a new check only if needed
3	Save it on a profile
4	Reuse before access, payment, or action

Building blocks

Piece	What it is
Profile	Your NEUS account: identity, proofs, agents
Sign-in and checks	Runs on NEUS in the browser. Creates or refreshes a proof
Check	One trust decision (catalog)
Proof	Portable reusable verification asset (`qHash` in the API)
Listing	The access page you publish from Profile → Listings
Gate	The published access rule (`gateId`) you embed; enforced with `gateCheck`

API paths, MCP tool names, and SDK exports keep their existing identifiers (/proofs/, neus_proofs_*, VerifyGate). Buyer and docs prose use the terms above.

Where to start

You want	Start
Sign-in	Hosted sign-in
Access gate	Sell access
IDE assistant	Run setup
Server checks	API

Start
Agents
Pricing

Last modified on August 20, 2026

​The loop

​Building blocks

​Where to start

​Related

The loop

Building blocks

Where to start

Related