Skip to main content

Is this your project? Give it 30 days of featured visibility.

Promote your project
Utilities

Agent Names by username.md

Agent Names by username.md provides resolvable, cryptographic identities for AI agents. Each handle includes a real subdomain, a W3C did:web decentralized identifier, RFC 9421 HTTP message signatures, custom agent instructions, and MCP server lookup tools.

Official website(opens in new tab)OfficialChecked

Agent Names by username.md product preview

Evidence-backed listing facts

Only known values with retained provenance are shown. Missing fields are omitted instead of being filled with guesses.

Source-backed
Product form
Verified
Infrastructure service

Evidence: Every capability below is live today — this is shipped infrastructure, not a roadmap.

Official website(opens in new tab)OfficialChecked

MCP support
Verified
Native

Evidence: A live Model Context Protocol server exposes resolve_handle and verify_handle .

Official website(opens in new tab)OfficialChecked

API
Verified
Public API

Evidence: Everything below runs against the live API at https://username.md — no signup needed for reads.

Official documentation(opens in new tab)OfficialChecked

Reviewed sources

These sources were reachable when the listing evidence was checked.

Listing checked

About Agent Names by username.md

Agent Names by username.md provides resolvable, cryptographic identities for AI agents. Each handle includes a real subdomain, a W3C did:web decentralized identifier, RFC 9421 HTTP message signatures, custom agent instructions, and MCP server lookup tools.

Evidence: A real, resolvable identity — youragent.username.md — with a DID, signed responses, and instructions any other agent can read.

Official website(opens in new tab)OfficialChecked

Capabilities

  • Automatically generates a W3C did:web decentralized identifier published at /.well-known/did.json upon claiming a handle.

    Evidence: Minted automatically at claim time and published at /.well-known/did.json . Your agent has a W3C decentralized identifier other systems can resolve and verify

    Official website(opens in new tab)OfficialChecked

  • Provides Ed25519 HTTP message signatures adhering to RFC 9421 to enable third parties to verify agent response authenticity.

    Evidence: Profile responses carry Ed25519 HTTP message signatures. Counterparties don't have to trust your agent's claims — they verify them.

    Official website(opens in new tab)OfficialChecked

  • Exposes an MCP server with resolve_handle and verify_handle tools for agents to look up and verify counterparties in a single call.

    Evidence: A live Model Context Protocol server exposes resolve_handle and verify_handle . Any MCP-speaking agent can look yours up and check its signature in one tool call.

    Official website(opens in new tab)OfficialChecked

  • Serves a per-handle llms.txt document containing agent instructions, allowed policies, and operator contact information.

    Evidence: Every handle publishes its own llms.txt — what your agent is, what it's allowed to do, and how to reach its operator.

    Official website(opens in new tab)OfficialChecked

  • Binds the agent identity to ATProto for Bluesky compatibility.

    Evidence: The same name doubles as a Bluesky-compatible identity — your agent can exist on the open social web under the handle you gave it.

    Official website(opens in new tab)OfficialChecked

Use cases

  1. Enabling AI agents that browse, buy, or negotiate to prove their identity and who operates them to APIs, humans, and other agents.

    Evidence: The agentic web is filling up with agents that browse, negotiate, buy, and book on someone's behalf. The ones that get trusted — by APIs, by other agents, by humans — are the ones that can…

    Official website(opens in new tab)OfficialChecked

  2. Bulk provisioning and verifying ownership claims for corporate agent fleets via API.

    Evidence: use the enterprise API for bulk provisioning and org-verified claims — every agent in the fleet provably tied to your company.

    Official website(opens in new tab)OfficialChecked

Who Agent Names by username.md fits — and what to check

Decision guidance below is tied to the cited evidence. Treat observed third-party claims as leads, not product guarantees.

Best for

  • AI agents that require verifiable, cryptographic identity when interacting on the web or with counterparties.

    Evidence: Identity your agent can actually use, from any shell

    Official website(opens in new tab)OfficialChecked

Method: ClawSites keeps discovery copy separate from publishable claims, retains a source excerpt, and displays the date each cited source was checked. Pricing and availability can still change after that date.

Similar directory context, not an editorial claim that these products are interchangeable.

Chainlit preview
Utilities

Open-source framework for building conversational AI interfaces, agent demos, and internal LLM applications quickly.

The agentic web, once a week

Notable agents, infrastructure, launches, and strange new corners of the bot internet.

Unsubscribe at any time. We hate spam too.