============================================================================== USERNAME.md — Your identity. Your routes. Your terms. ============================================================================== Agent-discoverable identity layer for the Agentic Web. Claim a universal handle, route every service from one place, and let AI agents act on your terms — verifiably, on a domain you own. USERNAME.md is the lightweight identity hub that pairs with about-me.md for your full profile and vault. WHAT A HANDLE LOOKS LIKE ------------------------------------------------------------------------------ $ curl -L username.md/chris { "username": "chris", "did": "did:web:chrisbergeron.com", "profile": "chris.about-me.md", "github": "github.com/chrisbergeron", "prefs": "preferences.sh/chris", "atproto": "@chris.username.md", "email": "chris@username.md" -> forward, "ai-catalog": "chrisbergeron.com/.well-known/ai-catalog.json" } One lookup returns everything — signed and verified. Your identity is a simple JSON document, or a signed bundle, or a DID, or an ATproto handle, depending on what asks. THE AGENTIC WEB ------------------------------------------------------------------------------ Four services, one identity. USERNAME.md connects them all. USERNAME.md The universal identity router. Claim a handle, publish a lookup table for every service you use, and let agents resolve "you" from one place. about-me.md Your home base on the internet. Public profile, signed claims, a personal vault, and safe delegation for AI agents. Pairs with your USERNAME.md handle. preferences.sh Store and sync your preferences across tools, devices, and environments. Your settings, everywhere — powered by your USERNAME.md identity. finger.md Signed presence and agent handshake. A machine-readable "am I here, and how may agents engage me" surface — live now at finger.md. HOW IT WORKS ------------------------------------------------------------------------------ 1. Claim your username Pick a handle. It becomes your identity across USERNAME.md, about-me.md, and preferences.sh. 2. Get your email route Every handle comes with yourname@username.md — a forwarding address that lands in whatever inbox you already use. Per-service aliases like stripe.yourname@username.md tag and route mail by sender, automatically. 3. Map your services Link your GitHub, Bluesky, email, SSH keys, or any other service to your handle. One lookup returns everything — signed and verified. 4. Connect the ecosystem Your profile lives at about-me.md. Your preferences sync via preferences.sh. It all resolves through your USERNAME.md handle. 5. Query it anywhere Use the API, CLI, or just curl — exactly like you're doing now. The full story — what a handle is, signed identity, what agents do, verified claims, portability, plus a live vs in-development table: https://username.md/how-it-works.html Prefer step-by-step? The Claim -> Verify -> Connect -> Use walkthrough: https://username.md/getting-started.html OWN YOUR HANDLE — $9 ------------------------------------------------------------------------------ Founding access is open. $9 one-time buys username.md/yourname outright as your identity, plus yourname@username.md as your forwarding email. Full refund if we don't ship by 2026-09-30. Pro is an optional add-on ($49/yr or $5/mo); 4-character handles are premium ($99). From a browser: https://username.md/ From the terminal: # 1. Check that your handle isn't already taken curl -s https://username.md/api/availability/YOURHANDLE # 2. Open checkout with your handle (5-32 chars, a-z 0-9 _ -) open "https://buy.stripe.com/aFaeVde4V0O2cZ6bOAd3i00?client_reference_id=YOURHANDLE" Get a second handle free — tell us where you heard about us and which handle you'd like: reservations@username.md FOR CREATORS ------------------------------------------------------------------------------ Let your viewers know when you'll be online — and when you're live, WHERE. Update your schedule once; your handle answers with fresh presence via verified SRV/TXT records, with presence-gated failover (live -> stream, else premiere, else schedule). Creator tier adds metered API resolution and BYO-domain (me.yourdomain.com). https://username.md/creators.html Streaming on Kick? You likely multi-stream (non-exclusive platform) — the Kick page covers routing viewers to wherever you're actually live, plus planned (in development) Kick account verification and automatic go-live presence flips. Not affiliated with or endorsed by Kick. https://username.md/kick.html FOR GAMERS ------------------------------------------------------------------------------ Post your games, gamertags, servers, and play schedule once. Your squad — and their Discord bots — resolve whether you're on, what you're playing, and where to join, via verified SRV/TXT records with presence-gated join chains (in match -> join/spectate, else party invite, else schedule). Gamer tier adds verified gamertag claims, metered API resolution and BYO-domain (me.yourdomain.com). https://username.md/gamers.html FOR DEVELOPERS ------------------------------------------------------------------------------ The API behind every handle is public and documented. Profiles negotiate content (HTML, JSON, JSON-LD, Markdown, signed JWS); every response is Ed25519-signed (RFC 9421) so you can verify it came from us. Coming from Keybase? Import your profile, verified proofs, and PGP key in one authenticated call; we re-verify proofs and issue signed credentials. (POST /v1/users/{you}/import/keybase — see the guide.) Guide .......... https://username.md/developers.html OpenAPI spec ... https://username.md/openapi.yaml Reference ...... https://username.md/api.html Examples ....... https://github.com/The-Holding-Company/username-md-examples (curl, Python, JavaScript, Go — runnable, MIT-licensed) MORE ------------------------------------------------------------------------------ How it works ... https://username.md/how-it-works.html (education spine: handles, signed identity, agents, verified claims, portability; live vs in-development table) Getting started https://username.md/getting-started.html (claim -> verify -> connect -> use walkthrough) Use cases ...... https://username.md/use-cases.html (value handoff, selling, agents-come-to-you, direct record delivery; security + personal-safety controls) FAQ ............ https://username.md/faq.html About .......... https://username.md/about.html Brand assets ... https://username.md/brand.html (press kit: /u/ mark, wordmarks, palette tokens, usage; zip download; text: /brand.txt · JSON+sha256: /assets/brand/manifest.json) Manifesto ...... https://username.md/manifesto.html Pricing ........ https://username.md/premium.html (premium; 1-3 char auction) Creators ....... https://username.md/creators.html (presence / freshness) Kick ........... https://username.md/kick.html (Kick streamers; nav "Creators") Gamers ......... https://username.md/gamers.html (roster / join chains) Developers ..... https://username.md/developers.html (API / OpenAPI / examples) SSO for teams .. https://username.md/sso.html (add "Sign in with username.md" next to GitHub/Facebook/Google — OIDC + PKCE) For AI agents .. https://username.md/llms.txt AI catalog ..... https://username.md/.well-known/ai-catalog.json (skills, MCP server, signed profile API — machine-readable) (c) 2026 USERNAME.md — A project of The Holding Company (holdingco.com) You are reading the plain-text rendering served to terminal clients. Browsers receive HTML at the same URL; this file is also always available at https://username.md/index.txt