RFC 0001 · DRAFT · OCT 2026

aittps://

HTTPS proved the server was real. aittps proves the agent is.

The trust layer for the agentic internet. Every agent request carries who it is, who it acts for and exactly what it may do — signed, scoped and checkable at the edge.

Identity ✓Delegation ✓Scope ✓Proof ✓Verify, don't guess.

§1 — THE HANDSHAKE

One request. Three agents. The edge decides.

Pick who's knocking. Watch what the site sees.

INBOUND REQUESTshop.example › edge

VERDICT

§2 — WHY NOW

The internet was built for people clicking links. That internet is gone.

01 · AGENTS AS WEAPON−7 days

Bugs now get exploited before the patch ships. Security by obscurity doesn't survive a model that reads every line.

Patch-to-exploit, 2025 est. · Mandiant M-Trends 2026
02 · AGENTS AS TARGET10×

AI writes more code with more holes, and agents themselves can be talked into leaking keys and PII.

Security findings with AI assistants · Apiiro 2025
03 · AGENTS AS CROWD35%

Humans are now the minority of web requests. Sites can't tell a person from a script, or a good bot from a bad one.

Human share of HTML requests, Oct 2026 · Cloudflare Radar

§3 — THE STACK

Four questions every request answers before it lands.

Drop-in for sites and agent builders. No CAPTCHAs, no guessing from IPs and user-agents.

L1Identity
Which agent is this, really?Agent: did:aittps:shopper/7f3a
L2Delegation
Which human or company is it acting for?On-Behalf-Of: human (proof-of-person)
L3Scope
What is it allowed to do here, and until when?Scope: purchase<=50USD; once; exp=3600
L4Proof
Can everyone verify it later?Signature + receipt → human & site

§4 — ANTIFRAGILE BY DESIGN

Every agent that joins makes the network harder to fool.

Verify, don’t guess.Cryptographic identity replaces IP lists, fingerprints and CAPTCHAs.
Scope, don’t trust.Permission travels with each request, so a hijacked agent can’t exceed its mandate.
Receipts, not logs.Every action leaves a signed record the human and the site can both check.
Kill bug classes.Design out whole categories of attack instead of patching them one CVE at a time.

§5 — REQUEST FOR COMMENTS

Help write the first handshake.

Building agents, running a site, or drowning in bot traffic? Get the draft spec and a seat at the table before v1 ships.

One email when the draft spec is ready. No spam.