See every agent at your door. Let the right ones in.
AI agents are already reading your docs and buying for their users. D3 Edge shows you who’s actually visiting — so you decide who gets in.
Free for websites · live in ten minutes.
Observe mode
the free SDK, ten minutes after installThe shift
Agents are changing faster than any site can track. Most rules haven’t moved since 2023.
More agents every month, more registries describing them, and more ways to declare who they are and why they visit. Most sites still answer all of it with a 2010-era on/off switch.
The numbers below come from the State of Agentic Traffic report — D3’s study of how the top 10,000 websites handle AI agents.
71%
No rule for the agent that answers customers
Among sites that block Anthropic’s training crawler, 71% have no rule for its answer-time agent, the one that arrives when a customer asks. OpenAI: 53%. Perplexity: 50%.
State of Agentic Traffic
38%
Of the rules were written in one quarter of 2023
Most datable GPTBot blocks landed in a single quarter of 2023, naming one bot. The traffic kept changing; most of those files haven’t.
State of Agentic Traffic
87%
Still add training crawlers, one name at a time
Of those 2023 blockers, 87% keep updating the file, almost always with another training crawler’s name. The agents that answer customers still go unaddressed.
State of Agentic Traffic
How agents prove who they are now.
Identity keeps moving. Every row below is a public launch:
One agent, four records
ChatGPT’s agent is listed by multiple public registries, signs its requests with published keys, and its operator publishes IP ranges. Several sources, several kinds of proof, one visitor at your door — and that’s one agent of 1,400.
Read the research →Your traffic is already agentic.
Assistants, search agents, and training crawlers — most of them invisible until you look.
See your own mix — grade your site →a sample month of one site’s traffic · agentic share 38.4% on day 31
What D3 Edge does
Monitor, control, and monetize your agentic traffic.
Edge covers the lifecycle from first sighting to signed rate card, inside the infrastructure you already run.
One rule blocks your buyers too.
A blanket block turns away the buyer along with the freeloader. Policy by purpose lets you open one lane at a time.
sample traffic, one policy change · line width = request volume · trainers 31,542 · search 12,306 · assistants 1,847 · 7 days
Monitor
See every agent — vendor, purpose, and whether it’s who it claims to be. Identity is verified on every request; a borrowed name gets caught.
Control
Allow, meter, or block by agent — rules written in plain words, not regex. They run in your own edge and only add to what you already trust, so nothing breaks.
Monetize
See what training crawlers took, so you can walk into your next licensing negotiation with your own numbers. D3 takes no cut of whatever you sign.
Why D3 Edge
Identity is changing faster than any bot list. We check every agent against its operator’s own proof.
Names are the easy part, and ours come from every major registry. Proof is fetched from the operator and checked on every request, in your own edge.
Every agent you’ve heard of.
And 1,400 you haven’t.
One feed, merged from every major registry. New agents land before you’ve read about them.
signatures · key directories · IP ranges · kept current
One engine checks the proof, on every request.
Signatures, certificates, published IP ranges — the proof is fetched from the operator and kept current. Stale proof expires. A borrowed name gets caught against the operator’s own proof.
74% of known AI assistants publish signing keys · 28 of 38 · D3 bot registry, August 2026
See who can prove it today →Every standard declares purpose differently. We canonicalize and prove it.
Registries, key directories, and headers each declare why an agent visits in their own words. D3 Edge canonicalizes every claim into one vocabulary your policy can act on, and treats a vague claim as training. Every answer carries its own tier for how proven the purpose is.
See the lanes and the policy →Start in observe mode
See every agent in ten minutes, with nothing at risk.
Observe mode blocks nothing, runs in your own account, and fails open. Turn on enforcement when the log convinces you.
Free for websites · no card · live in ten minutes.
Your policy
Write it once, in plain words.
Four sentences cover it, because the vocabulary underneath is canonical: one word per claim, however many standards declared it. No bot lists to maintain, and nothing you already trust changes.
Most policies’ first change is opening a lane: it re-admits the buying agents a blanket block was turning away.
Not bot defense. Cloudflare and Akamai stop the bots that attack you; D3 Edge governs the agents that pay you.
Full answers for your security review: Trust & deployment.
The research
We graded the top 10,000 sites’ robots.txt. Almost none have a rule for the agents that answer customers.
The State of Agentic Traffic report grades the web’s top 10,000 sites. Your grade comes from the same engine.
10,000
Sites’ robots.txt files, read bot by bot
The Tranco top 10,000, from Sitedex’s July 2026 scan.
Sitedex, CC BY 4.0
351
Sites block every answer-time agent
Of 5,577 readable files, just 351 block answer-time agents across the board. The rest stay reachable when a customer’s assistant comes asking.
State of Agentic Traffic
144
Sites ever said yes on purpose
Of 5,577 readable files, only 144 explicitly let an answer-time agent in. For nearly everyone else, open is just the default.
State of Agentic Traffic
See where your site lands.
Get your Agentic Traffic Readiness grade in ten seconds — A to F, with the evidence behind it.
Free · no signup · results are shareable.
Built on Sitedex’s top-10,000 robots.txt scan (July 2026, CC BY 4.0). Read the research →
See your own agentic traffic
Set up D3 Edge on your own traffic — we’ll walk you through it.
Free SDK · observe mode first, nothing blocked · fails open, in your own account.