Cycling through all six. Tap any point to stop.

Measured on six things

One verified handle for your online identity, readable by...

Design

Clean, modern design with a coherent identity-focused visual language and strong hierarchy. The homepage communicates the problem effectively, but the large navigation footprint and generous hero spacing still make the experience feel broader and heavier than the simple "one handle" message suggests.

Screenshots

1 / 1

username.md

About this app

username.md solves the mess of scattered online identities. Your username is rented right now. On twitter, twitch, youtube, github. You're one BAN away from losing your community - your identity. With username, you OWN your identity. Instead of maintaining a dozen profiles and link lists, you claim a single handle like username.md/you, which serves as a page for humans, an email forwarder, and a cryptographically signed API for apps and AI agents. It's a one-time $9 founding access fee, with a full refund promise if the full vision isn't shipped by September 2026. For creators, gamers, developers, and anyone tired of constantly updating their info everywhere, username.md is a game-changer. Once set up, your handle becomes a single source of truth, with content negotiation serving HTML, JSON, or Markdown as needed. It's not just a link-in-bio tool; it's a foundational identity layer for the emerging agentic web.

Key features

1Persistent handle with a one-time $9 founding price for 5+ characters, with premium 4-character handles offered separately
2Cryptographically signed identity responses using Ed25519 and RFC 9421, plus verifiable claims, `did:web`, and DNS-based verification
3Machine-readable identity through JSON, Markdown, JSON-LD, signed bundles, per-handle `llms.txt`, and MCP-based resolution and verification
4OpenAPI 3.1 developer platform plus OIDC "Sign in with username" for third-party applications
5Bluesky/ATProto binding, Keybase proof import, email forwarding, API tokens, and enterprise provisioning options

Target customer profile

Drawn from the product itself, not from a survey.

Demographic

Content creators and influencers with a strong online presence across multiple platforms

Pain points

Managing multiple bios, link-in-bio pages, and contact methods is time-consuming and error-prone; updates are often missed, leading to outdated information for fans and potential sponsors.

Primary needs

A single, trustworthy link that centralizes all their content and contact info, easy to update once and have it reflected everywhere.

Demographic

Developers and technically savvy users who value open standards and verifiable identity

Pain points

Existing identity solutions are proprietary and locked into specific ecosystems; they lack a simple way to expose their identity as an API for their tools and projects.

Primary needs

An open, cryptographically secure handle that can be used in command-line tools, APIs, and integrations, with full control over data and verification methods.

Demographic

Gamers and esports enthusiasts who want a unified gaming identity

Pain points

Gamertags are platform-specific, and friends and communities struggle to find each other across different games and platforms; sharing session times and server details is often chaotic.

Primary needs

A single handle that shows their gaming profiles, session schedules, and server invites, resolvable by both people and gaming bots.

Demographic

Professionals and entrepreneurs who need a credible online identity for networking and business

Pain points

Scattered profiles (LinkedIn, personal website, email) create a fragmented image; they need a way to stand out and prove their identity to potential clients or partners.

Primary needs

A professional, easy-to-remember handle that consolidates their professional presence and provides verifiable credentials for enhanced trust.

Scout Review

Written by AI from measured evidence, scored out of 100.

username.md is an ambitious digital identity and identity-infrastructure platform built around a persistent, verifiable handle for people and AI agents rather than a conventional social or community application. The current product is materially broader than a simple profile page: handles support machine-readable profiles, cryptographically signed API responses, `did:web`, signed verifiable claims, DNS-based domain verification, Bluesky/ATProto binding, Keybase proof import, email forwarding, per-handle `llms.txt` instructions, MCP resolution, and a documented OpenAPI 3.1 surface. The product also exposes a standards-based OIDC provider for "Sign in with username," extending the identity layer into authentication and application integration. The biggest change from an earlier assessment is that documentation is now clearly present: there are dedicated Getting Started, How It Works, FAQ, Developer, Agents, Enterprise, and Integration surfaces. The main weakness is no longer missing documentation but product maturity and complexity. The navigation is broad for a product whose core message is simplicity, some advanced features remain in development, and the public SSO badge is still in preview pending a published client ID. Security fundamentals are strong, with HTTPS, HSTS, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy observed by an independent benchmark, but CSP is still absent and there is no public SOC 2 or ISO certification claim. The strongest positioning is as a digital identity / identity infrastructure product for humans and AI agents. The combination of portable handles, signed responses, `did:web`, verifiable claims, OIDC, and agent-facing surfaces gives username.md a substantially more differentiated proposition than a traditional link-in-bio platform.

Measure by measure

Usability

The original documentation concern is largely resolved: username.md now provides dedicated Getting Started, How It Works, FAQ, Developer, Agent, Enterprise, and Integration documentation, plus runnable API examples. The remaining issue is complexity—the many audience and product paths can make discovery less immediate, while claiming a handle still relies primarily on JavaScript despite alternate checkout options.

Design

Speed

Performance remains a standout. The existing site review recorded strong Lighthouse results, while a current independent benchmark measured the username.md SSO surface at 90/100 performance with a 302 ms time to first byte and all sampled routes reachable.

Security

Strong technical foundation: HTTPS, HSTS, frame and content-type protections, Ed25519/RFC 9421 signatures, public verification keys, `did:web`, signed claims, DNS verification, encrypted secrets, and a documented DPA. The main gaps are the missing CSP, lack of public SOC 2/ISO certification claims, and the fact that the legal/security documentation is still marked as launch-stage material under review.

Accessibility

Automated accessibility testing is excellent, with a current 100/100 score reported for the SSO surface. The main remaining shortcomings are the lack of an explicit WCAG statement and the absence of multilingual support.

Growth

The strongest area. username.md now combines portable identity, signed claims, DIDs, agent instructions, MCP, API access, Bluesky binding, Keybase migration, and OIDC authentication. That creates a differentiated position in emerging digital identity and agent infrastructure rather than another generic profile category.

Improvement areas

Add a public security page or security center that consolidates CSP status, threat model, encryption details, incident reporting, and any future certifications
Simplify the navigation and information architecture so the identity-infrastructure proposition is immediately clearer
Continue shipping the remaining identity features, especially handle transfers, presence records, and short-handle functionality
Publish the production SSO client configuration and move the public "Sign in with username" badge beyond preview status

Design & Usability

username.md presents a clean, modern design with consistent typography, a restrained visual system, and a clear primary CTA. The homepage explains the core problem through three highly scannable concepts—scattered identity, lack of proof, and the rise of software agents—and makes the basic Claim → Verify → Connect → Use workflow easy to follow. The visual language now supports a more serious identity-infrastructure positioning than a social/community application. Usability has improved materially because the product now has a proper documentation ecosystem, including a getting-started guide, developer reference, API specification, FAQ, agent documentation, and integration examples. The site also provides a plain-text version of the homepage and a non-JavaScript checkout path. The main usability drawback is information density: the navigation spans product, audience, developer, agent, integration, pricing, FAQ, and company surfaces, which creates more cognitive load than the "one handle" proposition initially suggests. The claim flow also depends primarily on JavaScript, although alternate checkout and reservation paths are provided.

Speed & Security

Performance remains one of the product's strengths. The existing site review reported excellent Lighthouse results, and a more recent independent benchmark of the username.md SSO surface measured 90/100 for performance with a 302 ms time to first byte. The same benchmark found all sampled routes reachable and confirmed valid HTTPS. Security is considerably stronger than a typical profile platform because the core product is built around cryptographic verification. API responses use Ed25519 HTTP Message Signatures under RFC 9421, response integrity is paired with Content-Digest, public verification keys are exposed, and the product documents `did:web`, verifiable credentials, DNS-TXT verification, Bluesky binding, and signed claims. The privacy policy also states that encryption in transit, scoped access controls, and secret material in a secrets vault are used. The remaining security weaknesses are mostly transparency and maturity gaps rather than missing fundamentals. An independent benchmark found HSTS, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy but no Content-Security-Policy. There is also no public SOC 2 or ISO certification claim, while the current Terms, Privacy Policy, and DPA explicitly describe themselves as launch-stage templates still being finalized under attorney review. On the positive side, the platform has a dedicated privacy/security section, an enterprise DPA, international-transfer language, and documented subprocessors rather than leaving data handling unexplained.

Accessibility & Growth

Accessibility remains a strong area from an automated-testing perspective. The current independent benchmark reports 100/100 accessibility for the username.md SSO surface, while the earlier review also recorded a perfect Lighthouse accessibility score. However, there is still no explicit WCAG conformance statement on the public product surface, and the experience remains English-only. The lack of documented multilingual support is a meaningful limitation for an identity product intended to operate across the open web. Growth potential is now substantially stronger than the original review suggested. username.md has moved beyond the link-in-bio comparison and is building an identity layer that can serve people, developers, enterprises, and autonomous agents. The live feature set includes content-negotiated identity records, signed claims, `did:web`, Bluesky/ATProto binding, Keybase import, per-handle `llms.txt`, MCP resolution and verification, API tokens, and an OIDC provider for third-party applications. Enterprise offerings add high-volume identity resolution, organization provisioning, org-verified claims, and contract-based access. The main growth risk is category education. Users may initially understand username.md as another profile or link service, while the more valuable proposition is machine-verifiable identity infrastructure. Some of the most ambitious capabilities—including presence records, handle transfers, and the short-handle auction—are still in development. That leaves the product with a strong strategic wedge but a market that is still being defined.

Conclusion

username.md has evolved into a much more credible digital identity platform than a conventional social or community product. Its strongest differentiator is not the profile page itself, but the infrastructure behind the handle: machine-readable identity, cryptographically signed responses, verifiable claims, `did:web`, agent instructions, MCP support, and standards-based OIDC authentication. That makes the product especially relevant to developers, AI-agent builders, organizations, and anyone who needs a portable identity that software can resolve and verify. The product is also more transparent than the earlier review implied. Documentation is live, the developer API is specified in OpenAPI 3.1, the privacy and DPA surfaces are public, and the site clearly distinguishes what is live from what remains in development. The remaining concerns are legitimate: the navigation is broad, some capabilities are unfinished, CSP is missing, formal security certifications are not advertised, and the legal documents are still marked as launch-stage templates. For its current stage, however, the underlying architecture and positioning are unusually focused. username.md fits more naturally into Digital Identity / Identity Infrastructure / Authentication than Social or Community, and its agent-facing capabilities give it a meaningful opportunity to define a new category rather than compete solely with Linktree-style tools.

Suggestions for improvement

Position username.md explicitly as a Digital Identity / Identity Infrastructure platform rather than a social or community product.
Keep the current developer and agent documentation, but surface the core API, verification, and identity concepts earlier in the main navigation.
Add a dedicated security/trust center covering CSP, security architecture, vulnerability reporting, key management, certifications, and operational controls.
Add an explicit WCAG/accessibility statement and consider multilingual support for a product intended to function as a global identity layer.
Continue expanding enterprise identity capabilities around organization verification, provisioning, and high-volume identity resolution.

How we score

Alternatives comparison

Named competitors, point by point. Nobody paid to appear here or to be left out.

	username.md	Beacon	Linktree
Cryptographic identity verification	Ed25519-signed responses, did:web, W3C Verifiable Credentials	No cryptographic verification; simple link aggregation	No cryptographic verification; focuses on analytics and monetization
API for apps and AI agents	Open API with content negotiation (HTML, JSON, Markdown), free reads	No public API for identity; limited to web page	No public API for identity; limited to web page
Pricing model	One-time $9 founding fee with refund promise	Free tier with paid plans for advanced features	Free tier with paid plans for analytics and custom domains