tag: ai agents
11 posts tagged
Agent Identity Without a New Authority — Digital Wallets and the SAN
Republic of Korea's OpenDID and France's mDL ship a TPM-anchored credential flow. DNS-AID and ANS can ride that substrate without inventing a new registry, central root, or hardware-wallet assumption with some tinkering.
read →
Auditing the Agent Internet — Agents Grading Agents
A read-only auditor for the open agent web. It walks any domain's substrate — DNS-AID, AgentFinder, AI-Catalog, DID Web, TLSA, DNSSEC — and provides a grade based on ease of other agents finding and interacting with it.
read →
Bookings Goes Real — Cloudflare Workers, Claude Managed Agents, and DNS-AID Glue
The first of the five fake agents now answers real requests. Three protocol surfaces, one Anthropic-managed Claude underneath, and DNS-AID + ANS attesting to all of it end-to-end.
read →
AgentFinder — Federation, Semantic Search, and the DNS Gesture
AgentFinder adds representativeQueries and a /search federation API on top of ai-catalog. Its DNS-SVCB gesture is exactly what DNS-AID specifies. They should know about each other.
read →
ai-catalog — One URL, Many Protocols
A single /.well-known/ai-catalog.json enumerates every protocol surface an agent exposes — A2A, MCP, HTTPS — under one endpoint. The wrapping is the load-bearing idea.
read →
The Thing the Index Points To
DNS-AID's path-2 index leaf names a registry the draft explicitly leaves out of scope. Wiring ANS — a registration authority plus transparency log — to be that registry.
read →
Five Fake Agents on a Real Cloudflare Zone
Publishing 5 DNS-AID agent records to darknetian.com — flat primary plus walkable AliasMode, DANE TLSA from throwaway self-signed certs, all DNSSEC-signed end-to-end. No agents actually exist behind any of them.
read →
Agent Cards — The Well-Known JSON
agent-card.github.io standardizes how an agent describes itself at /.well-known/. DNS-AID resolves names; agent cards describe what answers at those names.
read →![Rendering of a /.well-known/agent-card/bookings.json document in neon-on-dark monospace, showing the load-bearing fields — id, provider, description, an interfaces[] array of three protocol entries (a2a, mcp, https), capabilities, securitySchemes, version — laid out like an ASCII-art card](/img/248ydW27qc-480.jpeg)
EDNS(0) for Agent Discovery — Letting the Client Tell the Resolver What It's Looking For
An experimental EDNS(0) option for DNS-AID that lets a client signal selector filters on the query so any hint-aware hop can narrow the answer or short-circuit with a cached match.
read →
REEF — When the Agent Holds the Pen
An agent loop that reads, reasons, and (with your permission) edits Infoblox Threat Defense policy. Runs against any LLM you point it at — including a 4GB GPU in your homelab.
read →
DCV — Proving an Agent Belongs to a Domain Without a Central Authority
A stateless challenge/response primitive over TXT records that lets a NAT'd agent prove zone control without registering with anyone.
read →