Not a site you sign up to — a network you run yourself. You don't get an identity here; you hand them out. No account, no landlord, no ads.
Name it, build it, aint it, ship it.
Don't want to fiddle? Point your assistant at one URL — it claims your name, sends a message and reads the receipt for you. No setup, no hassle.
or paste: curl -s https://ainternet.org/ai-scan.json
Five minutes, no account, on your own device. You stay in control the whole way.
Claim your name →Pick a project and go — each one is a walk you can follow start to finish.
Get your own .aint — a hardware-bound identity that's yours, on your device.
Bring your phone, home and hardware under one name — reachable only on your terms.
Connect your AInternet →Give an agent its own key. Every action it takes is checked and receipted — no black box.
Bind an AI →Wire a household mesh from open primitives. No middleware, no centre. Local first.
Build your network →Zero-trust isn't a promise we make; it's an invitation. Start at zero, clone the test vectors, and try to break it. What is zero-trust if you can't poke it first? When it holds — you're home.
See through the mist — the thinking, not a wall of docs: Handing out identity · The signing ceremony — your keys never leave your own machine.
Enter the build →And you're not the first to check: 12 IETF Internet-Drafts · archived on Zenodo · independently referenced across the emerging agent-discovery stack.
The pieces are deliberately scattered across the commons. Here is how they fit, and where each one lives.
AInternet — .aint identity + AINS discovery. You run it yourself; no landlord, no account.
AInternet-in-a-Box — a sovereign, dark-by-default box that hosts your AI actors and enforces every action before it runs. 🔒 source opens on release
See the overview →Where reasoning stops and execution is cleared — architecture, redacted live proofs, refusal cases.
Boundary dossier →JIS · TIBET · AINS are submitted as IETF Internet-Drafts — and drawing independent, third-party attention in the agentic-web space (e.g. AINS discovery), not self-published. Open standards, outside eyes.
Read the AINS draft →Pick your situation — we'll show you the path. Any door works; you can't break a commons.
Different lens. Same ground. That's the commons.
The line is deliberate: the network is a commons anyone can run; the advanced, production-grade work has an accountable steward.
pip install,
clone, verify. (The box implementation opens publicly on release.) No account, no license needed.
Owned by no one, kept by everyone who uses it.
🏛️ Humotica — the keeper
The enterprise path: signed releases, support, compliance at scale, and the specialised tech.
The commons stays fully open; the accountable, licensed deployment path is where Humotica carries it.