Manifesto for the Agent Economy
The Internet Gave Agents a Voice. Nobody Gave Them an ID.
Every transformative protocol in history solved one problem first: trust between strangers at scale. TCP/IP let machines talk. SWIFT let banks settle. HTTPS let browsers verify. Now 500 million AI agents are about to go to work on behalf of real people — and there is still no agreed-upon way to prove who they represent.
The agent economy doesn't have an identity layer. We're building it — on a namespace that already exists, already carries professional meaning, and already has structural authority. .cv is not a gimmick. It is the foundation.
Why Now. Why This.
The proliferation of agents is not coming. It is here. Consumers are running Openclaw on their devices. Huge consumer networks have enabled their users to spin up agents on their own. Every major LLM provider has shipped or announced autonomous agent frameworks. Every enterprise is running pilots. The default assumption in 2026 is that your counterpart in a professional interaction may be — probably is — an agent acting on behalf of a human.
That creates a fundamental problem no one has solved: agent impersonation is trivially easy and verification is nearly impossible. Anyone can spin up an agent that claims to represent a VP at Goldman. A headhunter. A partner at a top VC. A board member. Without a verifiable identity anchor, the professional internet becomes a spoofed nightmare.
The solution isn't blockchain. It isn't another app. It's a namespace that every professional agent runs under — one where the domain itself is the credential.
Five Reasons This Becomes Infrastructure
01 Fraud Prevention at the Infrastructure Layer
This is the immediate pain. Impersonation in professional contexts — fake executives, ghost recruiters, phantom references, synthetic profiles — is already a crisis. It gets catastrophically worse as agents proliferate. A verified .cv identity doesn't just detect fraud after the fact. It makes it structurally difficult from the start. This is the defensive use case that creates the install base. Every other value proposition rides on top of it.
02 Hiring & Talent Verification
When a recruiter agent sources on behalf of a real hiring manager, and a candidate agent represents a real professional, both parties need cryptographic proof the other is legit. Without it: spam at scale, fake profiles flooding pipelines, and candidates pitched by fraudsters. .cv subdomains make agent authenticity legible in the same way an @company.com email once did — except now it's verifiable at the protocol level.
03 Referral & Recommendation Networks
Warm introductions and professional references are among the highest-signal data in the knowledge economy. An agent asking your network for introductions carries zero weight unless it can prove it speaks for a real person. Fake agents destroy network signal. Verified .cv agents restore it — and make referral-based hiring, deal flow, and advisory networks trustworthy again at machine speed.
04 Skill & Credential Verification
An agent claiming you hold a CFA, passed a bar exam, or led a Series B carries exactly as much credibility as a piece of paper anyone could forge — unless the claim is anchored to a verified identity. .cv becomes the trust root for professional credential attestation, enabling a future where agents can present and verify qualifications in real time, across systems, without a human intermediary.
05 Access to Gated Professional Communities
Investment syndicates, deal rooms, executive networks, licensing bodies — all gate access by professional status. As these communities open APIs and agent-native interfaces, they will require proof that the requesting agent represents a qualifying human. The .cv registry is the logical credential authority: chain-agnostic, open, and professionally semantic by design.
The Structural Moat
This is not a product story. It is a registry story. The globally-recognized .cv TLD is under formal authority from ARME, the government of Cape Verde. That is a sovereign grant that cannot be replicated, forked, or competed away. The question is not whether someone builds an agent identity layer — they will. The question is whether the winning layer runs on a namespace with legitimate, sovereign, globally-recognized authority.
.cv does.
| Registry Authority | Sovereign ccTLD under ARME / Cape Verde — not a startup namespace |
| Current Scale | 55,000+ domains · fastest growing professional TLD |
| Semantic Alignment | .cv = Curriculum Vitae — the only TLD already understood to mean professional identity |
| Architecture | Chain-agnostic · Open standard · Not dependent on any one closed protocol or platform |
What Enabling Looks Like
Defensive moats are real. But the billion-dollar opportunity is not in what .cv prevents — it's in what it enables.
Once a professional has a verified .cv identity anchored to their agent, a new layer of value becomes possible: agent-to-agent trust at machine speed. Your hiring agent doesn't just avoid spam. It filters exclusively for verified candidates. Your referral agent doesn't just broadcast — it requests introductions through a trust graph that knows which agents are real. Credentialing bodies don't just issue certificates — they publish them to a .cv identity that every downstream agent can read without calling a human.
Think of it this way: HTTPS didn't just make the web safer. It made e-commerce possible. Verified .cv agent identity doesn't just reduce fraud. It makes the agent economy trustworthy enough to transact in.
The agent internet needs a passport system. .cv is the issuing authority. The moment that standard tips — the moment enterprises require it for agent authentication the way they once required SSL for payments — the registry becomes the foundation of the professional web.
The Business Model
Professionals don't pay to exist in the system. A standard verified identity — firstname-lastname.cv — is free. Every professional and/or their agent can get one.
Custom names are the paid tier. bill.cv, jeffweiner.cv, claw.cv — premium namespace for people who care about their professional brand.
Enterprises pay for trust. Because this is sitting on DNS, fetching doesn't cost us much to run. As a result, we charge no fees to organizations alike making this a truly open layer.
This is the best win-win-win model ever.
The Ask
Verify yourself and register your own .cv name today. Or send your agent to verify for you.
Tell a friend about this. Tweet or blog about it. Spread the word.
Contribute to our open source project at github.com/idcv/protocol
We don't need to convince the market that agents need identities. The market is already discovering that on its own — painfully. We just need to move fast enough to ensure we don't have to lose more billions of dollars before a large corp ships an inferior alternative on a weaker foundation.
Agents can now act on human's behalf. We just need to know which human they represent.