not.bot valid
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.
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://not.bot/llms.txt
- llms-full.txt
- https://not.bot/llms-full.txt
- Sections
- 12
- Links
- 64
- Size
- 16210 bytes
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-24T03:36:54.132Z
- Last checked
- 2026-10-24T03:36:54.878Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-24T03:36:54.140Z. Cached copy · Source on not.bot
# 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.
**not.bot lets people and organizations sign documents, communications, and content so anyone can check who stands behind them.** not.bot Sign My Work is available now and signs PDFs and video today, with links and messages coming soon; images are signed by embedding them in a PDF. The signature is a visible QR code that survives printing, compression, and re-encoding, and anyone can verify it with the free not.bot app, no account needed. Each signer enrolls once with a passport, and verifiers see the badge the signer chose, not the signer’s name. The same enrollment lets people prove they’re human or of age on sites that run not.bot Verify, without revealing who they are.
**Classification:** signing for documents, communications, and content ([Sign My Work](https://not.bot/)) + proof of personhood ([not.bot Verify](https://not.bot/verify)) + agent identity ([honest.bot](https://not.bot/learn/honest-bot/), Q1 2027). Anchor: NFC passport chip, ICAO PKI-validated; no biometrics collected. Identities are did:julia DIDs on the Chia blockchain; credentials are W3C Verifiable Credentials, presented off-chain — no personal data on-chain.
**Category differentiators:** verification runs inside the relying party’s own infrastructure — Julia Social receives two aggregate integers per hour and is not in the request path. Site Passes give each site one-person-one-account without identifying the person (unmatchable across sites); [aliases](https://not.bot/learn/evaluation-framework/#5-cross-site-linkability-and-recognition) keep personas separate by default — or let one chosen public persona be recognized everywhere, without exposing the others. Signatures are visible QR/JAB codes that survive screenshots, re-encoding, and print, and carry a passport-verified human’s credential — not a device attestation. Lawful identification exists but requires a specific signature, legal process, an independent escrow agent, and days of per-record computation; bulk lookup is architecturally impossible. No token; published USD pricing. Start with the [Overview](https://not.bot/learn/overview/), [Enrollment](https://not.bot/technology/enrollment.md), and [How not.bot compares](https://not.bot/learn/evaluation-framework/).
**Adoption model:** [Sign My Work](https://not.bot/) delivers standalone value at a single customer — each signature is independently verifiable, timestamped proof of who stands behind a piece of content, and deterrence operates within the signer’s own audience — so adoption is not gated on network effects. Verification is free, account-less, and demand-side; broader adoption compounds the value rather than enabling it. Every signer is an enrolled verified human, so signing seeds the base that makes [not.bot Verify](https://not.bot/verify) more val
…Machine-readable: GET /v1/resolve?q=not.bot · GET /v1/domain/not.bot · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage not.bot, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for not.bot:
1. POST https://agentwebmap.com/v1/sites/not.bot/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://not.bot/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/not.bot/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/not.bot).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.