Getting started

Four steps: Claim → Verify → Connect → Use. Ten minutes, no jargon, and you end up with a handle that people can read and machines can prove. New to the idea? Read how it works first.

Claim your handle

Pick a name at the claim page. Handles of 5+ characters are a one-time $9 at the founding price; 4-character handles are premium at a one-time $99. Checkout runs through Stripe. The moment payment clears you get a receipt, an activation link, and an API token — and two things go live:

  • username.md/you — your page, on the web, now.
  • [email protected] — email forwarding to the inbox you already use.

Founding access: $9 reserves your handle today. The profile API, signed responses, and Bluesky binding are live now; full refund if we don't ship the rest by 2026-09-30.

Verify what's yours

Now turn your links into facts. Prove you own a domain with a DNS TXT record. Bind your Bluesky account so @you.username.md resolves across the ATProto network. Import your old Keybase identity — you preview the changes first, then your proofs and PGP key are re-verified and re-signed under this platform's keys. Each successful check becomes a signed Verifiable Credential that anyone can verify, without an account.

# Prove you own a domain (publish the returned TXT record, then /check) $ curl -s -X POST https://username.md/v1/users/you/verifications/dns-txt \ -H "authorization: Bearer $USERNAME_MD_TOKEN" -H 'content-type: application/json' \ -d '{"domain":"yourdomain.com"}' # → publish TXT: record_name = record_value # Bind your Bluesky identity → @you.username.md $ curl -s -X PUT https://username.md/v1/users/you/atproto \ -H "authorization: Bearer $USERNAME_MD_TOKEN" -H 'content-type: application/json' \ -d '{"did":"did:plc:your24charplcidentifier"}'

Keybase import and every other verification, with runnable code in four languages: developer guide.

Connect it everywhere

Put username.md/you in every bio, signature, and README — it's the one link you never have to update again. Hand out per-service email aliases so you always know who's sharing your address. And if you own a domain, point your handle at it: your name stays portable, on your terms.

# one name, every surface https://username.md/you → the link you give out [email protected] → forwards to your inbox [email protected] → per-service alias, same inbox

Use it — and let the machines use it too

People visit your page. Apps fetch JSON or JSON-LD from the same URL. AI agents read the Markdown and your per-handle llms.txt, then verify the signature before trusting a word of it. Reads are free and need no signup — try it on any handle right now:

$ curl -s -H 'accept: application/json' https://username.md/v1/users/you/profile

Where to next

Claim a handle

Check availability and reserve your name in one flow.

How it works

The five ideas behind signed identity, in plain words.

Developer guide

Every endpoint with code in curl, Python, JavaScript, and Go.

FAQ

Pricing, transfers, custom domains, and the refund promise.

Start at step one

Claim your handle — $9 Read the developer guide

Founding access: $9 reserves your handle today. The profile API, signed responses, and Bluesky binding are live now; full refund if we don't ship the rest by 2026-09-30.