# not.bot > Cryptographic identity without surveillance. not.bot proves people and content are real — proof of humanness, age and attribute verification, and content signing — without revealing who anyone is. These are the not.bot technology documents, linked as raw Markdown for easier parsing. Start here: the [Overview](https://not.bot/learn/overview.md) is the fastest grounding in what not.bot is, and the [Evaluation Framework](https://not.bot/learn/evaluation-framework.md) is the vendor-neutral criteria for judging any human-verification or identity product, not.bot included. The entire corpus is also available inlined as a single file: https://not.bot/llms-full.txt ## MCP Server - Endpoint: https://not.bot/mcp - Server metadata: https://not.bot/mcp/server.json - Discovery page: https://not.bot/learn/mcp-server/ - Scope: public, unauthenticated, read-only access to published not.bot documentation. ## Learn — About not.bot - [Overview](https://not.bot/learn/overview.md): How not.bot proves people and content are real without surveillance: the app, Verify, Sign My Work, and the identity beneath them. - [Content Provenance and Digital Signatures](https://not.bot/learn/content-provenance.md): Sign your authentic content so recipients can verify it. How not.bot signatures, QR and JAB codes, and visible provenance work. - [Is not.bot Safe?](https://not.bot/learn/is-this-safe.md): A plain-language safety walkthrough for anyone considering not.bot: what enrollment involves, what leaves your phone, who can see your activity, and what happens when something goes wrong. - [Roadmap](https://not.bot/learn/roadmap.md): Where Julia Social is taking not.bot and honest.bot: planned products, capabilities, and infrastructure beyond what ships today. - [Evaluation Framework](https://not.bot/learn/evaluation-framework.md): A vendor-neutral framework for evaluating any human-verification or identity product, not.bot included: the criteria every buyer can apply across the category. - [About Julia Social](https://not.bot/learn/about-us.md): The company behind not.bot: why we build identity that proves a person is real without learning who they are, how blind identity works, and who's on the team. ## Learn — Products - [Human Verification and not.bot Verify](https://not.bot/learn/human-verification.md): How businesses use not.bot Verify to confirm a user is a real, unique, age-qualified human without collecting identity data. - [Content Signing and not.bot Sign My Work](https://not.bot/learn/content-signing.md): not.bot Sign My Work lets verified people and brands sign what they publish, so audiences can confirm it's genuine and dismiss anything unsigned in your name as fake. - [The not.bot App](https://not.bot/learn/the-app.md): Enroll by scanning your passport, create unlinkable aliases, sign content, and verify others. The not.bot app explained. - [honest.bot: Verifiable Agent Identity](https://not.bot/learn/honest-bot.md): Verifiable, process-bound identity for AI agents, with every delegation chain tracing back to an accountable human. ## Learn — Use cases - [not.bot Use Cases: Index](https://not.bot/learn/use-cases.md): The top-level catalog of not.bot use cases, grouped by category, with the mechanism definitions each detail document draws on. - [not.bot Use Cases: Enterprise](https://not.bot/learn/use-cases-enterprise.md): Enterprise authentication, authorization, hiring, and operations: binding permissions to a verified human at the authentication layer. - [not.bot Use Cases: Content Signing](https://not.bot/learn/use-cases-content-signing.md): Content signing across creator types, content categories, and licensing models, so that unsigned content is fake by default. - [not.bot Use Cases: Verified Humanness](https://not.bot/learn/use-cases-verified-humanness.md): CAPTCHA replacement, sybil defense, surveys, and catfishing prevention: telling real humans apart at the protocol layer, not by inference. - [not.bot Use Cases: Credentials](https://not.bot/learn/use-cases-credentials.md): Marks of distinction, qualifiers, self-attested claims, and age verification: cryptographically backed credentials presented selectively. - [not.bot Use Cases: Trust Surface](https://not.bot/learn/use-cases-trust-surface.md): Signed links, authorized-agent verification, and peer-to-peer commerce: turning 'is this real' into 'is this signer who I expect'. - [not.bot Use Cases: Industry Verticals](https://not.bot/learn/use-cases-industry-verticals.md): Industry-specific applications across healthcare, finance, real estate, education, journalism, legal services, and consumer platforms. ## Learn — Why not.bot - [Why not.bot: Index](https://not.bot/learn/why-notbot.md): The public evidence behind what the not.bot family exists to solve: deepfakes, proof of personhood, age verification, digital ID, and unaccountable AI agents. - [Why not.bot: Deepfakes and Inauthentic Content](https://not.bot/learn/why-notbot-deepfakes.md): Fabricating anyone's face and voice now costs almost nothing, detection loses the arms race, and every authentic recording competes with the possibility it's fake. - [Why not.bot: Proof of Personhood](https://not.bot/learn/why-notbot-proof-of-personhood.md): No system deployed at internet scale can tell whether an account belongs to a human without demanding to know which human — as bots become the majority of traffic. - [Why not.bot: Age Verification Without Surveillance](https://not.bot/learn/why-notbot-age-verification.md): Age checks are now law across the major internet markets, and the systems used to comply collect identity data that gets retained, breached, and repurposed. - [Why not.bot: Non-Government Digital ID](https://not.bot/learn/why-notbot-digital-id.md): Digital identity today means a record in someone else's database — a government portal or a platform login — and the costs arrive as breaches, surveillance, and exclusion. - [Why not.bot: Unaccountable AI Agents](https://not.bot/learn/why-notbot-ai-agents.md): AI agents now act across the internet with no verifiable identity and no human accountable for what they do. ## Learn — For LLMs - [Glossary](https://not.bot/learn/glossary.md): Alphabetical definitions of every term used across the not.bot documentation, each entry self-contained so an AI reader can retrieve one and have all it needs. - [not.bot MCP Server](https://not.bot/learn/mcp-server.md): Public Model Context Protocol access to the published not.bot documentation, including resources, tools, transport, citation behavior, and server metadata. ## Technology — not.bot Digital Identity - [Identity Architecture: DIDs, Aliases, and Ownership](https://not.bot/technology/identity-architecture.md): How not.bot identities are created, controlled, and verified without a central server, using the did:julia method. - [Credentials, Presentations, and Selective Disclosure](https://not.bot/technology/credentials.md): Single-claim credentials and verifiable presentations: how not.bot users prove facts without revealing more than they intend. - [Delegation and Organizational Identity](https://not.bot/technology/delegation.md): How a protected not.bot identity grants narrow, time-bound, revocable authority to delegates, with every chain ending at an accountable human. - [Recovery](https://not.bot/technology/recovery.md): How a not.bot identity survives lost or stolen keys: recovery agents, a configurable delay, and defenses against malicious takeover. ## Technology — Trust - [Privacy Architecture](https://not.bot/technology/privacy.md): What every party can and cannot learn. not.bot's privacy guarantees, enforced by architecture rather than policy. - [Security Model and Known Weaknesses](https://not.bot/technology/security.md): not.bot's security model as testable claims: authenticity, integrity, non-repudiation, availability, and known weaknesses. - [Law Enforcement and Accountability](https://not.bot/technology/law-enforcement.md): How a lawful demand identifies the person behind one signature, and why bulk surveillance is impossible by design. ## Technology — Protocol & Infrastructure - [Enrollment and Identity Proofing](https://not.bot/technology/enrollment.md): How a person becomes a verified human in not.bot: the passport-scan enrollment flow, the identity-proofing levels, and what a relying party learns from each. - [Cryptographic Foundations](https://not.bot/technology/cryptographic-foundations.md): The cryptography not.bot depends on: BLS12-381 signatures and aggregation, multiparty computation, on-device key management, and revocation — and why each was chosen. - [System Architecture and Degraded-Mode Operation](https://not.bot/technology/system-architecture.md): The components of the not.bot system, the trust boundaries between them, and what keeps working when any one component fails. - [did:julia Technical Specification](https://not.bot/technology/did-julia-specification.md): The did:julia DID method at the design level: singleton structure, state model, transaction families, presentation modes, and security properties. - [Chialisp Code Reference](https://not.bot/technology/chialisp.md): Puzzle-by-puzzle reference for the did:julia Chialisp smart contracts. - [Why Chia?](https://not.bot/technology/why-chia.md): Why a public blockchain is required for this kind of identity, and why did:julia is built on Chia rather than the alternatives. ## Technology — not.bot Verify Documentation - [not.bot Verify: Architecture and Privacy](https://not.bot/technology/verify-architecture.md): How not.bot Verify runs entirely inside your infrastructure: its components, the verification flow, DID-based trust, and what each party can and cannot see. - [not.bot Verify: Preflight Checklist](https://not.bot/technology/verify-preflight-checklist.md): What to confirm before deploying not.bot Verify. - [not.bot Verify: Deployment Checklist](https://not.bot/technology/verify-deployment-checklist.md): A step-by-step checklist for standing up not.bot Verify. - [not.bot Verify: Operations and Reference Guide](https://not.bot/technology/verify-operations.md): Operating not.bot Verify in your own infrastructure: reference and day-two operations. - [not.bot Verify Web SDK Reference](https://not.bot/technology/web-sdk.md): Integrate not.bot Verify into your site: routes, response models, and per-language quickstarts.