username.md
username.md is a personal identity platform that lets you claim a verified handle resolving across platforms with cryptographically signed API responses. When claimed, your handle gets a profile page at username.md/you, email forwarding from you@username.md, and a free queryable API that returns profile data in HTML, JSON, or Markdown format. Each API response is Ed25519-signed per RFC 9421, allowing applications and AI agents to verify identity claims without trusting a central authority. You can bind Bluesky accounts, prove domain ownership via DNS, or import Keybase proofs to establish verified identity claims. The platform uses open standards (did:web, W3C Verifiable Credentials) and charges a one-time $9 fee per handle.
username.md is an identity resolution platform, integrating with Bluesky, Keybase, and Stripe. InnovaAI scores it 4.4/10 for agency adoption, best for Developer, Account Executive, and Strategist roles.
Agency Audit
username.md is a cryptographically verified identity handle that resolves across platforms via API, allowing agencies to claim a single verified profile page with signed responses and email forwarding. It's most relevant for developer tooling agencies and identity verification service builders who need to embed verified identity lookups into client workflows or internal tools. The platform integrates with Bluesky, Keybase, and Stripe, and serves profile data as HTML, JSON, or Markdown. For most digital agencies, adoption ROI depends on whether your team regularly needs to verify identities, resolve user profiles programmatically, or build identity infrastructure into client deliverables.
3recommended
9/mo
No paid plan published
Low
Illustrative scenario. Not a guarantee. Net capacity needs a verified paid base plan, and none is published for this service, so it is not modeled. Hours saved come from the service estimate; implementation, taxes, and unprovided usage charges are excluded.
- Developer handling identity verification in client products
- Account Executive handling contractor onboarding and profile management
- Strategist handling client proposal and proof-of-concept development
- Your agency's primary workflows are design, content creation, or campaign management with no need to query or verify user identities programmatically.
- Your team has no use case for cryptographically signed identity proofs or open-standard identity resolution and would not embed identity verification into client deliverables.
- You're looking for a team identity or access management tool; username.md is a personal identity handle, not an enterprise directory or SSO solution.
Internal Adoption Path
No paid plan published
9 hr/mo
3 seats × 3 hr each
$675/mo
modeled at $75/hr labor rate
No paid plan published
Illustrative scenario. Not a guarantee. No verified paid base plan is published for this service, so subscription cost and net capacity are not modeled. Implementation, taxes, and unprovided usage charges are excluded.
Platform Features
Core capabilities of username.md
Cryptographically signed profile API
Every profile lookup returns Ed25519-signed responses per RFC 9421, allowing developers and AI agents to verify identity claims without trusting a central authority. Developers building identity verification features into client products can query the API for free without signup.
Email forwarding from handle
Incoming mail to you@username.md forwards to your existing inbox, eliminating the need to manage a separate email address. Account executives and founders can share a single verified email across all client communications and bios.
Cross-platform identity binding
Bind a Bluesky account, prove a domain via DNS, or import Keybase proofs so the same handle resolves consistently across networks. Strategists working with decentralized social or identity-first clients can demonstrate unified identity resolution in proposals.
Content negotiation for multiple formats
The same handle serves as HTML (for browsers), JSON (for applications), or Markdown (for AI agents), depending on what requests it. Developers can integrate identity lookups into client workflows without building separate endpoints for each format.
Refund guarantee through 2026-09-30
Full refund if the platform doesn't ship promised features by the deadline, reducing adoption risk for teams piloting identity verification workflows.
Open standards and no vendor lock-in
Uses did:web, W3C Verifiable Credentials, and RFC 9421 instead of proprietary formats, so identity data remains portable if your team needs to migrate or integrate with other identity systems.
What Makes username.md Different
Unique advantages vs similar tools in this niche
Cryptographically signed identity responses
vs Traditional link-in-bio services that offer no verificationEvery answer from a handle is Ed25519-signed per RFC 9421, allowing anyone to verify the authenticity of the data.
Open API with content negotiation
vs Closed platforms that only serve HTML pagesThe same URL returns HTML, JSON, or Markdown depending on what asks, making it easy for apps and AI agents to consume.
Bluesky binding for cross-network resolution
vs Isolated identity silos on individual platformsBind your Bluesky account so @you.username.md resolves across the network, providing a unified identity.
Latest Updates
Recent releases and improvements for username.md
Your name is scattered
NewA dozen profiles, a different link list in every bio, an email per platform. When something changes, you update it everywhere, or, more likely, you don't.
Nothing proves it's you
NewAnyone can make a page that _says_ it's you. username.md is the one that can _prove_ it, every answer your handle gives is cryptographically signed.
The web's new visitors are agents
NewMore and more of what visits the web isn't a person, it's software acting for a person. Those agents need one address where they can look you up and trust the answer. This is a handle. One command, one verified answer.
Refund promise, in writing
New2026-09-30Full refund if we don't ship by 2026-09-30. We mean it.
A real company
NewA project of The Holding Company. Payments handled by Stripe, we never see your card.
Value Equation
Outcome-likelihood-time-effort assessment for username.md
Limited agency channel
username.md scored below the agency-resellability threshold (agency_fit_score < 50). The Value Equation projects agency-side outcomes, which don't apply to tools without a clear resell pathway.
Contact username.mdPricing
username.md platform cost to your agency
Handle: $9 one-time
Handle
- Handle at username.md/you
- Email forwarding via you@username.md
- Profile API with signed responses
- Bluesky binding (@you.username.md)
No verified white-label program for username.md: client-facing delivery runs under the platform's native branding.
Market Intelligence
Offer + scale economics for username.md
Limited agency channel
username.md scored below the agency-resellability threshold (agency_fit_score < 50). It's a useful tool but not designed for white-labeled or retainer-based reselling, so we don't publish productized offer economics for it.
Contact username.mdInvestment Decision Framework
Strategic vetting analysis for username.md
Situational Fit
Fit depends on your client mix
Buy If
4Your developer tooling team builds identity verification or user lookup features into client products and needs a cryptographically signed, queryable identity source that doesn't require custom infrastructure.
Your strategists or account executives work with clients in identity services, fintech, or developer platforms and need to demonstrate verified identity resolution as part of a proposal or proof-of-concept.
Your operations team manages contractor or freelancer onboarding and wants a single verified identity page that contractors can share across platforms without re-entering profile data.
Your team regularly needs to resolve user profiles via API and currently relies on fragmented data sources or manual verification across multiple platforms.
Skip If
4Your agency's primary workflows are design, content creation, or campaign management with no need to query or verify user identities programmatically.
Your team has no use case for cryptographically signed identity proofs or open-standard identity resolution and would not embed identity verification into client deliverables.
You're looking for a team identity or access management tool; username.md is a personal identity handle, not an enterprise directory or SSO solution.
Your clients or internal team rarely interact with Bluesky, Keybase, or decentralized identity standards and would not benefit from cross-platform identity binding.
Bottom Line
username.md is a cryptographically verified identity handle that resolves across platforms via API, allowing agencies to claim a single verified profile page with signed responses and email forwarding. It's most relevant for developer tooling agencies and identity verification service builders who need to embed verified identity lookups into client workflows or internal tools. The platform integrates with Bluesky, Keybase, and Stripe, and serves profile data as HTML, JSON, or Markdown. For most digital agencies, adoption ROI depends on whether your team regularly needs to verify identities, resolve user profiles programmatically, or build identity infrastructure into client deliverables.
Reality Check
username.md is a personal identity tool, not a team collaboration platform. Agencies adopting it must map it to a specific workflow (identity verification, developer tooling, or personal branding) rather than expecting broad productivity gains across all roles. The one-time $9 cost per handle is low friction, but the value only compounds if your team actually queries the API or embeds verified identity into client work.
Low effort: self-service setup with guided onboarding
Academy for username.md
Work through it in order: the course for this service first, then the modules behind it.
Course for this service
username.md Agency Implementation, Verified Identity for Client Networks
Learn how to set up verified identity infrastructure for your clients using username.md's cryptographically signed profiles and cross-platform binding. This course covers claiming handles, configuring email forwarding, integrating the signed API into client workflows, and positioning identity verification as a retainer service for agencies managing multiple client identities.
Open the courseNo Academy modules are published for this service yet. Browse the full Academy
Why this category matters
The commercial case before the tooling.
Core concepts
The mental model you need to price and scope the work.
- Profile Completeness ThresholdConcept
Identity Resolution succeeds when a buyer profile crosses a completeness threshold, beyond which targeting, personalization, and attribution become reliable. Below that threshold, campaigns waste spend and ROI reports mislead. Agencies can treat this threshold as a diagnostic: measure how many known contacts have enriched firmographic, behavioral, and intent data stitched into a single profile. For example, a platform like Common Room consolidates buyer intelligence from CRM, product usage, and community activity, using a 400M+ contact directory to enrich records. When profiles reach critical mass, agencies can shift from broad campaigns to account-specific plays, improving conversion and retention. The framework also warns against over-reliance on third-party data as privacy rules tighten, pushing agencies to build first-party data strategies that sustain profile completeness over time.
- Identity Resolution as a Data-Ops MoatConcept
Identity Resolution is not just a technical fix; it is a strategic moat for agencies. By stitching fragmented buyer data into persistent, enriched profiles, agencies build a proprietary data layer that competitors cannot easily replicate. This framework positions identity resolution as the foundation of a defensible data-ops offering, turning messy CRM and product data into a client-retaining asset. For example, an agency using Common Room's Context360 engine can continuously update person-level profiles from a 400M+ contact directory, enabling precise targeting and attribution that standalone tools cannot match. As privacy regulations tighten, agencies that master this layer reduce reliance on third-party data, future-proofing their client relationships. The moat deepens with each integration, making the agency indispensable to the client's revenue operations.
- Signal-to-Identity Decay CurveConcept
The Signal-to-Identity Decay Curve describes how the value of a resolved identity profile decays as the freshness of its underlying signals declines. In identity resolution, a profile is only as useful as its most recent behavioral or firmographic data. When a buyer visits a site, engages with content, or triggers a product event, that signal carries high intent. But as days pass without new activity, the profile's predictive power fades, making personalization and targeting less effective. For agencies, this curve dictates the cadence of data enrichment and re-engagement. A profile refreshed daily with intent signals from platforms like Common Room, which consolidates buyer intelligence from web visits and product usage, retains high value, while a stale profile becomes a liability. Agencies that monitor signal decay can prioritize outreach to accounts showing recent activity, avoiding wasted spend on cold records. The curve also highlights the risk of over-reliance on third-party data, which may arrive with lag, reducing the window of actionable insight.
Decision and risk
How to judge the fit, and the ways it goes wrong.
- Identity Resolution Rule: Match Deterministic First, Then Layer ProbabilisticEvaluation Rule
Prioritize deterministic matching on first-party identifiers before adding probabilistic enrichment.
- Identity Resolution Rule: When Client Data Is Siloed, Unify Before You PersonalizeEvaluation Rule
Unify client data into a persistent profile before spending on personalization or AI-driven targeting.
- The Fragmented Profile Trap: Why Identity Resolution Stalls in AgenciesFailure Pattern
- The Attribution Blind Spot: Why Identity Resolution Fails in Agency ReportingFailure Pattern
8 modules selected for username.md
Frequently Asked Questions
Answers about pricing, setup, implementation
username.md lets you claim a verified identity handle that resolves across platforms and can be queried by applications and AI agents. You get a profile page at username.md/you, email forwarding from you@username.md, and a free API that returns cryptographically signed profile data in HTML, JSON, or Markdown. You can bind your Bluesky account, prove a domain, or import Keybase proofs to establish verified identity claims.
username.md offers 1 pricing tier, at $9 one-time (Handle).
Developers building identity verification or user lookup features into client products benefit most, since they can query the API for free and embed cryptographically signed identity resolution into workflows. Strategists and account executives working with identity services, fintech, or developer platform clients can use a verified handle to demonstrate identity resolution in proposals. Operations teams managing contractor onboarding can direct freelancers to a single verified profile page instead of collecting scattered contact info.
Time savings depend on your workflow. If your developers currently build custom identity verification or manually query multiple platforms to resolve user profiles, username.md eliminates that work by providing a free, queryable API with signed responses. For teams managing contractor onboarding or identity-heavy client work, consolidating profile data into one verified handle saves 2-4 hours per month per person by removing manual profile updates and verification steps.
username.md integrates with Bluesky, Keybase, and Stripe. The core value is the open API and signed responses, which any application can query via HTTPS without integration. If your team uses Bluesky or Keybase for identity verification, you can bind those accounts to your handle. Stripe handles payments so the vendor never sees your card.
Claiming a handle and getting your profile page live takes minutes. Binding additional identity proofs (Bluesky, domain verification, Keybase import) adds 5-15 minutes per proof depending on which platforms you use. There is no team rollout or training required.
username.md does not publish a cancellation or data retention policy in the available documentation. You should contact the vendor directly to understand what happens to your profile page, email forwarding, and API data if you stop using the service.
No. username.md is designed for personal identity handles, not team directories or enterprise access management. If your agency needs SSO, team directories, or role-based access control, use an identity provider like Okta or Auth0 instead.