identity rails for businesses
Every request, signed.
Every agent, accountable.
Email addresses aren't identity — they're just strings your attackers also know. about-us.md is the B2B layer of the Agentic Web: your customers arrive with verified handles, cryptographic consent receipts, and explicit agent delegation, so support, refunds, account recovery, and agent-to-agent traffic stop running on trust-by-email.
Agents welcome. This site speaks plain text and JSON too:
curl https://about-us.md/llms.txtThe problem we're solving
Anyone can claim to be your customer
Account takeover, refund fraud, and chargebacks all start the same way: a stranger emails support pretending to be someone real. You verify with knowledge-based questions that LinkedIn already leaked.
Bots already outnumber humans
LLM agents are filing tickets, scraping pricing, and probing auth flows. You can't tell which ones your customer authorized and which are wearing their hoodie.
KYC is too heavy for everything
Full KYC for a refund inquiry is overkill. A magic link to a Gmail address is laughably under-kill. There's no middle layer — until now.
What about-us.md gives you
- Verified handles. Every customer arrives with a signed, portable identity backed by their own keys. You verify the signature, not the trivia.
- Consent receipts. Every consent decision (marketing opt-in, support access, agent delegation) is a signed artifact you can replay in court. No more screenshots of checkboxes.
- Agent firewall. Customers explicitly allowlist which agents can act on their behalf. You stop guessing whether a Claude/ChatGPT/Operator request is legitimate.
- KYC-light identity rails. Stronger than email-magic-link. Cheaper and less invasive than full IDV. Right-sized for support, refunds, returns, account recovery, and B2B procurement.
- Portable across vendors. Customer identity works at your business, your competitors, and their bank. You inherit identity instead of rebuilding it.
Before vs. after
| Workflow | Before | After |
|---|---|---|
| Refund request | "What were the last four digits on the card?" Hope. | Verified handle + signed refund-request receipt. Done in 3 seconds. |
| Agent ticket | Block all bots and lose real assistants. Or trust all of them. | Customer-signed delegation token. Allow only their agent. |
| Account recovery | SMS to a SIM-swapped number. | Re-prove handle ownership cryptographically. |
| Marketing consent | "You checked the box on Feb 3, 2022, we swear." | Signed consent receipt with revocable scope. |
| B2B procurement | PDF NDA, DocuSign, three weeks. | Handle-signed scope-of-access in one round-trip. |
How verification works
Your system receives the signed request above, verifies the signature against
https://username.md/u/aclay/.well-known/keys, checks the delegation scope, and acts.
No knowledge-based questions. No SMS. No guessing whether the agent is legit.
The full handshake is three steps — walk through it.
Where it fits in your stack
Support & helpdesk
Zendesk, Freshdesk, FreeScout, Intercom — verify the requester before any agent (human or AI) takes the ticket.
Auth & recovery
Sits beside Auth0 / Cognito / Keycloak. Adds a strong recovery factor that survives SIM swaps and email compromise.
Agent & API gateway
Verify which agent is acting and whether the user delegated this scope. Throw the rest in the bin.
Who this is for
- E-commerce ops drowning in refund fraud and AI-generated chargebacks.
- SaaS companies whose support tickets are 40% bot traffic and rising.
- Marketplaces that need stronger than email-verify but lighter than KYC.
- B2B procurement teams sick of PDF-and-DocuSign identity theater.
- Anyone building an agent platform who needs a real "is this user really the user" answer.
The Agentic Web, in one diagram
about-us.md is the B2B face of a small family of cooperating sites. Customers use the user side; you use this one.
username.md
Your customers claim /u/handle, set agent policy, and sign consent. Edgy, user-owned.
finger.md
Machine-readable presence and agent handshake. The protocol layer beneath both sides.
about-me.md
Personal flagship. Where individuals publish their canonical presence to the network.
Get on the early list
We're onboarding design-partner businesses through Q3 2026. You get reserved namespace, white-glove integration help, and influence over the consent-receipt schema before it freezes.