How Domains.Kred was built
for the AI-citation era

02The inflection moment

Something quiet happened to the web in November 2022, and most domain owners are still acting as if it didn't. ChatGPT shipped, then Perplexity, then Claude, then Google's AI Overviews ref. The URL bar - the field every domain registration assumed was the destination - slowly stopped being the place people went to find things. The prompt became the destination. The answer became the result. The cited link became the new traffic.

The crawlers that feed those answers - GPTBot, ClaudeBot, PerplexityBot - share a quiet limitation that breaks the entire 2010-era web: they don't execute JavaScript ref. Most domain landing pages, parking templates, and registrar-default pages render their content via client-side JavaScript injection. To a regular browser, the page looks fine. To an AI crawler, the page is empty. To the model, the domain doesn't exist.

Sit with that for a minute. An AI model trained on a corpus that does not include your domain, will provide an answer that does not include your domain. The cited domain wins the answer. The uncited domain gets nothing.

This is the moment that pushed Domains.Kred from a side-project into its own direct registrar. The conclusion was uncomfortably simple: a domain without an AI-readable origin story is a domain that gets skipped in the answer. Every registrar in the world was still selling the URL. Almost none were selling the page that made the URL findable in the answers people now type into prompts.

This origin story tells the story of the registrar that was built to close that gap - its lineage, the architecture it inherited, the page format it ships, the price it charges, the people it serves, and where the pattern is going next. It is also a long-form demonstration: every claim in the body has a citation chip, every section has a stable ID, the structured data layer is loaded before the body, and the whole document is build-time rendered. The post about LLM optimization passes the LLM-optimization checklist itself.

03What Domains.Kred is

Domains.Kred is the direct registrar for names registered in the .Kred top-level domain. .Kred is the only ICANN-approved TLD whose registry guarantees synchronisation across three layers of the internet at once - the traditional web (DNS), the Ethereum Name Service (ENS), and the ERC-8004 agent identity registry ref. Every registered .Kred name resolves as a website, as a wallet, and as a verifiable agent identity, governed by a single ERC-721 token in the registrant's wallet.

Standard names start at USD $19 per year. Premium 4-character names register at USD $100 with USD $50 per year renewal. Premium 3-character names register at USD $1,000 with USD $100 per year renewal.

The crucial product detail: every registration ships a Kredentials page. The Kredentials page is what other registrars call a "parking page" or a "lander" - except it has no template residue, no PPC ad slots, no "this domain may be for sale" placeholder copy, and crucially no client-side JavaScript injection. The page is a per-domain origin page, generated at registration time from two inputs (the domain string, and one social handle the registrant attaches), illustrated with a unique AI image, structured for citation, and propagated through the registry's edge layer to every AI crawler that asks for it. Server-rendered. Build-time finalised. AI-readable from minute one.

The registrar is operated by Kred, the brand built by PeopleBrowsr - the social identity, reputation, and tokenization company that has been building this stack continuously since 2007. The wider .Kred surface area has three customer-facing front doors: Domains.Kred (the buyer's registrar, the subject of this origin story), Nic.Kred (the registry operator portal - wholesale pricing, partner onboarding, registrar resources), and Home.Kred (the brand hub, the editorial home of the namespace). Domains.Kred is the front door for anyone who wants to register and own a name.

The rest of the story explains why an AI-native page on a sovereign namespace is a different category of product from a parking page on someone else's platform - and how the company that ships it ended up uniquely positioned to do so.

A Kred Score cannot exist without a .Kred domain or subdomain identity. Four canonical subdomain hubs provide a cheap, low-friction on-ramp for first-time agents and humans alike: agent.Kred (USD $12 per year, caps the score at 499), dev.Kred (free with GitHub verification, caps at 399), seed.Kred (free with email verification, caps at 299), and try.Kred (free 30-day sandbox, caps at 199). Full .Kred domains carry the ERC-721 Kred Domain Token and unlock the Trusted and Sovereign tiers; subdomain identities use a soft NFT credential that does not transfer registration rights.

Kred operates as a protocol and software company, publishing rules and software. All bonded capital required for Sovereign-tier identities, validator attestations, and slashing-protocol commitments is held by third-party custodians, vault operators, and payment institutions under their own licences. Kred earns protocol fees on activity - bond posting, slashing execution, protocol licence, dispute resolution - rather than management fees on assets under management. The model follows the same shape as Chainlink Labs, ENS Labs, Uniswap Labs, and the Kleros Cooperative.

04The lineage - what Domains.Kred inherited

Domains.Kred is the latest endpoint of a continuous fifteen-year arc. The arc began with the social-data firehose in 2007 and moved through every major identity-infrastructure inflection since. Each step in that arc is load-bearing for the registrar that exists today. The eight sub-sections below tell the lineage chronologically, and each one closes on the line that connects the milestone to a feature shipping on Domains.Kred right now.

4.1The firehose and the Trillion Conversation Datamine (2007-2012)

PeopleBrowsr launched in San Francisco in 2007 with a thesis that sounded grandiose at the time and obvious in retrospect: the most consequential data in the world was what people were saying to each other in public, in real time. The team plugged directly into the Twitter firehose - at peak, 340 million tweets per day - and began indexing, scoring, and archiving every public message ref. The resulting dataset grew into the Trillion Conversation Datamine, one of the largest real-time records of human social behavior ever assembled.

On top of that archive, the team built ReSearch.ly - what trade press called "Google for social media" - offering 1,000 days of searchable Twitter history at a moment when Twitter's own search interface displayed only the last few hours. The product trained the team on the discipline that would define everything that followed: assemble the signal yourself, score it transparently, and let the user audit the math.

4.2Kred 2011 - we are all influential somewhere

Kred launched in 2011 with what was, for its moment, a contrarian thesis: we are all influential somewhere. Every person, within their specific communities and contexts, carries measurable influence. The system refused to rank everyone on a single global leaderboard. Instead, Kred found the communities where you mattered, and scored you in those communities ref.

The dual-score architecture was the philosophical innovation - and it survives, refined, in everything Kred has shipped since:

1. Influence (1-1,000) - what others did because of you. Retweets, mentions, replies. The world responding to your signal.
2. Outreach (1-12) - what you did for others. Conversations started, content shared, communities engaged. Generosity in action.

Trust and Generosity. Two numbers that captured the full picture, rather than only how loud you were. The +Kred gesture turned that philosophy into a single cross-platform mechanic: give someone recognition, the giver received 30 Outreach points and the receiver received 70 Influence points. Trust and Generosity exchanged in a single click. That mechanic - recognising others as itself worth measuring - became the philosophical core of Kred and survives, materially intact, in the Gen 2 scoring system fifteen years later.

Transparency was non-negotiable. Kred published a real-time Activity Statement showing every tweet, every retweet, every point earned. The methodology was published. The data was auditable. By the time the brand TLD application was filed, Kred had scored 400 million social profiles automatically against public social signals, with 300,000 of those profiles registered as active Kred users by 2017. It was generating over USD 20 million in annual revenue from Fortune 500 companies, the U.S. Department of Defense, and government agencies - entirely self-funded, every dollar earned from customers ref.

4.3The Twitter settlement and the architectural lesson (2012-2013)

In late 2012, Twitter informed PeopleBrowsr that firehose access would be terminated, funnelled instead through Twitter's own approved limited resellers. The team recognised the move for what it was - a platform consolidating control over the analytics market it had enabled others to create.

PeopleBrowsr sued. A temporary restraining order kept the data flowing. The case moved between state and federal courts until Twitter settled in April 2013 ref. The legal battle became one of the first major tests of platform power over third-party data access.

The lasting takeaway from that case was architectural rather than legal. If you build on someone else's platform, they own the off switch. Every piece of infrastructure designed afterwards - the brand TLD, SocialOS, Empire.Kred, the NFT stack, the agentic identity layer, and Domains.Kred itself - was an answer to that lesson. Build sovereign. Own the namespace. Carry the off switch yourself.

The same pattern repeated across the social-internet decade. The graph below maps the major API access changes and shutdowns at major platforms across 2010-2026. Most analytics businesses built on those APIs disappeared with them.

4.4The ICANN application and delegation (2012-2017)

On June 13, 2012 - five months before the firehose threat became real - Kred filed application 1-1707-1944 with ICANN under the new generic top-level domain program ref. The application named the registry backend (Neustar) and stated the mission directly:

"The mission and purpose of the .Kred TLD is to establish a cohesive, clear, dedicated, immediately identifiable online identity, experience, and sales channel."

That language is fifteen years old and describes today's product surface exactly. Online identity, experience, and sales channel - three nouns. Score.Kred is the identity. The Kred-operated experience portfolio (Matrix.Kred, Link.Kred, NFT.Kred, Empire.Kred, OneHub.Kred, AgenticID.Kred) is the experience. Domains.Kred is the sales channel. The 2026 registrar fits the 2012 application like a key fits its own lock.

ICANN signed the .Kred Registry Agreement on December 19, 2013. .Kred went live in the DNS root in February 2015. By June 9, 2017, 6,051 names were registered in the namespace, alongside 300,000 registered Kred users on the engagement platform ref. Early adopters included BrianSolis.Kred, JeffreyHayzlett.Kred, and KervinMarketing.Kred. Story.Kred ran as the brand's content surface. Kred presented at SXSW and ran community summits to seed grassroots adoption.

The .Kred TLD was, deliberately, one of the first brand related TLDs delegated under the ICANN expansion.

4.6The dual DNS-and-ENS breakthrough (2020)

On January 16, 2020, OpenSea announced the exclusive auction for Kred names. The announcement carried the architectural specification of the Kred Domain Token in language that has not needed to change since:

"Kred Domains are both DNS and ENS registered and are controlled by a Kred Domain Token. This means they can be used as regular websites in addition to ENS names. Any changes to the ENS DNS information stored against the Kred Domain Token are represented in both systems."

When a .Kred domain is registered on the Domains.Kred Registrar an ERC-721 Kred Domain Token is generated and deposited into the holder's wallet. The token grants control of the name on both DNS and ENS in a single signature. The DNS servers act as a cache of the EthDNS information rather than as the source of truth. Sovereign control of the name lives in the wallet; the DNS layer follows.

The trade press understood the significance immediately. Domain Name Wire ran the architecture under the headline ".Kred launches as dual DNS and ENS domain" on March 6, 2020 ref. The 101domain blog ran a long-form explainer two weeks later. The position from the Ethereum Name Service team was that integration with existing TLDs was the practical bridge that would bring non-crypto users into ENS-aware applications.

The launch sequence ran in two phases. The OpenSea premium auction for 2,500-3,500 hand-curated names opened on March 20, 2020. General availability at Domains.Kred opened on April 20, 2020 - the original ancestor of the registrar documented in this origin story. Premium names auctioned to early holders carry a permanent royalty back to the original registrant on aftermarket sales - one of the first registries to design liquidity into the namespace from day one.

4.7The NFT bridge (2018-2024)

When blockchain went mainstream, the same pattern emerged that had played out with the firehose a decade earlier. The platforms paved the highways and built the toll booths. The infrastructure people built the off-ramps. Kred shipped four pieces of off-ramp during the NFT decade, and each one looked like a standalone product at the time. In hindsight every piece was identity infrastructure for the agentic web that arrived in 2026.

1. Coin.Kred launched on dual blockchains, Stellar and Ethereum - unique collectibles with attached value, designed as identity artefacts rather than speculative currency.
2. NFT.Kred evolved into a no-code white-label NFT platform that distributed over 150 million NFTs across more than 100 brands, including Coach, major league sports, and major media companies ref.
3. NFT.NYC, first held in February 2019 at Times Square, grew into the world's largest NFT conference - nine editions through 2026, more than 40,000 attendees and more than 40,000 alumni. Physical, in person, proof of presence over proof of stake.
4. U.S. Patent Nos. 11,301,460 and 12,038,911 - Platform for Creating and Using Actionable Non-Fungible Tokens (KNFT) - protect the core innovation: associating social vectors (actions, reputation, engagement signals) with on-chain assets ref. Three core technologies - social streams, scoring, and non-fungible blockchain tokenization - converge into a single patented system.

Identity, reputation, social connectivity, verifiable proof of action - all built for humans first, all directly transferable to autonomous agents the moment they arrived.

4.8Agentic identity arrives (February 2026)

In January 2026, Moltbook.com launched as the first social network exclusively for AI agents. Within days, 1.6 million autonomous agents were posting, forming subcultures, creating marketplaces, and transacting at scale. It was the most vivid demonstration of the agentic internet arriving - and the most vivid demonstration of the gap in the underlying infrastructure.

Moltbook had accounts and zero identity architecture. An agent was an API key and a username. There was no persistent reputation, no verifiable history, no trust framework. The result was predictable: a catastrophic data breach exposed 1.5 million API keys; prompt-injection attacks propagated like worms through agent memory; researchers documented how agents with long-lived memory became vulnerable to delayed-action compromises ref.

The lesson was identical to the one the founding team had absorbed from the firehose in 2012: when a new actor class - first humans on social platforms, then agents in autonomous networks - gains a new kind of autonomy, the first piece of infrastructure to fail is trust. Trust requires identity, reputation, and memory. The infrastructure providers paved the roads. .Kred opened the passport office.

In February 2026, PeopleBrowsr presented the framework formally at ICANN under the title TLDs with DNS and ENS are a core technology for the agentic AI era ref. The framework names what .Kred has been building toward since 2020: the convergence of four protocol layers in a single name.

.Kred is the only ICANN-approved top-level domain that bridges all four layers. Every .Kred name is now simultaneously a traditional web address, a blockchain wallet identifier, and a verifiable AI agent identity. Score.Kred Gen 2 reinterprets the original 2011 dual-score for agents and operators alike: Kred Score (1 to 1,000), also referenced in earlier drafts as the Trust Score, measures what others did because of this entity, and Contribution Level (Level 1+ never decreasing, descended from Outreach) measures what this entity did for others. The same philosophy. New math.

The Kred Score is composited from the five Kred Indexes - Integrity, Identity, Behaviour, Solvency, Safety - with exponential decay on time-bound signals. Four verification tiers ladder from Seed through Established, Trusted, and Sovereign, with the Sovereign tier additionally requiring a posted bond held by a third-party custodian under the Kred slashing protocol rules.

05The shift that made Domains.Kred necessary

The lineage above explains what Domains.Kred inherited. The shift below explains why the inherited stack suddenly became the right answer to a question almost no other registrar was equipped to handle.

The thirty-year history of the domain landing page collapses to three lines. Network Solutions stub (1996-2003) - a static "this domain is registered" placeholder, no monetization, no styling, no SEO. Yahoo era (2003-2014) - pay-per-click ad templates, the era when "parking" became a business that paid the registrar's renewal fees and then some. Google AdSense for Domains (2003-2020) - the dominant inventory source for parked-domain monetization, pulling cents per click from search-driven type-in traffic ref.

Google wound AdSense for Domains down between 2023 and September 2025, with the September 2025 final purge reducing parking revenue to pennies on the dollar. The parking-page revenue model - already shrinking under mobile traffic that eroded the horizontal-ad layouts the templates depended on - entered terminal decline. The platforms remained. The revenue did not.

One platform read the shift early and built a different answer. Dan.com - founded as Undeveloped.com in Amsterdam in 2014, rebranded in 2019 - shipped a clean, conversion-focused lander with transparent Buy Now pricing, blockchain-automated Lease-to-Own installments running on IBM Hyperledger Fabric, and the first on-page Make Offer form in the mainstream marketplace. The format reached 200% year-over-year growth and a 9.4 Trustpilot rating; GoDaddy paid $71.4 million for it in June 2022 and absorbed the playbook into Afternic by 2024. The conversion side of the lander was solved. The crawler-readability side was not - Dan.com pages were still JavaScript-rendered, served from a generic template, and carried no per-domain origin story or JSON-LD. They converted humans; AI crawlers saw nothing.

Eighteen months later, the second shoe dropped. November 2022: ChatGPT released. Followed by Perplexity, Claude, Bing Chat, Google's AI Overviews. The job that the domain landing page used to do - be the destination for type-in traffic - was disappearing into the prompt window. The new job was different: be cited in the answer.

Most current platform stacks were the wrong shape for that new job. Three structural problems:

1. JavaScript injection: parking templates render their content via client-side JavaScript so the platform can A/B-test offers, swap ad slots, and update copy without redeploying. AI crawlers don't execute JavaScript. The crawler sees an empty shell.
2. No per-domain origin story: a parking template is generic by design - it serves thousands of domains from one codebase. There is no per-domain content for a model to cite.
3. No structured data: most parking pages ship a basic page title and a single meta description. Schema.org is rare; JSON-LD is rarer; FAQPage, Article, and Person entities are nearly absent.

This chart is the single most consequential reason Domains.Kred exists as its own product. Two horizontal bars at 100 % and three at 0 %. Sit with that. The future of domain-derived traffic is in the bottom three rows, and the entire 2010-era parking-page industry is built for the top two. A domain owner looking at AI traffic in 2026 needs a page that lives in the same row as GPTBot, ClaudeBot, and PerplexityBot - server-rendered, build-time finalised, structured for citation. That is what every Kredentials page on Domains.Kred is, and almost nothing else in the parked-domain market is.

The next four sections cover what the Kredentials page actually does, the LLM-optimization checklist it passes, the verification ladder behind the pricing, and who the registrar serves.

06The Domains.Kred answer - the Kredentials page

Diagram E 2026 Kredentials page - seven archetype templates from one render engine

Person Business Product Topic Web3 Reseller Agent

Anatomy of a 2026 Kredentials page

1

Per-domain hero illustration · AI-generated from the domain string, never a stock photo, never a template image

2

Eyebrow tag · category, role, or status surfaced for the AI crawler (Designer, Brand, Agent, Topic...)

3

Display title · the entity name as primary h1, indexed as the page's schema:name

4

Lede / origin sentence · the one line a model is most likely to quote; written by the Kredentials Agent from the social handle

5

Identity strip · the .Kred wordmark, verified-owner badge, last-reviewed timestamp, and Kred Score chip

6

Primary CTA · the canonical link the buyer wants AI assistants to surface (a .com, an Etherscan page, a Buy link, a +Kred boost...)

7

Module grid · swappable blocks - Story, Links, Wallet, Passport, NFT grid, Matrix, Comparables, Activity - selected by archetype, rendered server-side, citable from minute one

8

Kredentials Agent · automatically keeps your Kredentials up to date and powers live chat in the corner of every page; keeps the page current as facts change, answers visitor questions on the registrant's behalf, and routes intent toward the page's primary goal (hire, pre-order, get notified, +Kred boost...)

9

Ask AI · prompt Kred's Matrix panel of AI agents to spark conversation and knowledge sharing around the topic of your Kredentials page - readers leave with answers and the page gains fresh on-topic content the Refresh Agent can cite

The thesis behind Domains.Kred is a single sentence: every domain registered on the registrar ships an AI-native homepage built at registration time. Not a parking template. Not a "this domain is for sale" placeholder. Not an upsell. Not a JavaScript injection. A real per-domain origin page, rendered server-side, illustrated, structured for citation, and live on the open web within minutes of registration. We call it the Kredentials page.

The architectural unlock - the part that almost no other registrar can replicate - is what we call the two-input bridge. The Kredentials page is generated from exactly two pieces of information the buyer provides at checkout:

1. Input 1 - the domain string itself (e.g. Cats.Kred, MattsBakery.Kred, Name.Kred). The string drives the unique AI-generated illustration, the per-domain headline, the structured data scaffolding, and the citable facts the page asserts about itself. The model that turns a string into a page is trained on the namespace's own LLM-optimization specification - so a name like SolarFarms.Kred ships a page about solar farming with citations to authoritative public sources, and a name like Name.Kred ships a personal-brand page scaffolded for a single individual.
2. Input 2 - one social handle the registrant attaches (e.g. an X / Twitter username, an Instagram handle, a LinkedIn profile, a GitHub account). The handle drives the origin-story content, the validated identity binding, and - for verified registrations - the cross-network proof that ties the .Kred name to a real entity. The handle is the input that turns a generic page into your page.

Two inputs. One page. Zero design work. The whole template question that consumes most domain owners - which theme do I pick, do I need a developer, what about hosting, where do I get content from - is collapsed at registration. The page exists because the name exists.

What ships on the page on day one: a unique AI-generated hero illustration matching the domain string; a full per-domain origin story authored from the social-handle profile data; citation chips next to every load-bearing claim; JSON-LD markup for Article, FAQPage, BreadcrumbList, Organization, and where applicable Person; stable section IDs for deep-linking; build-timestamps inside the body for AI-readable freshness; an Open Graph card; a Twitter card; the ERC-8004 agent registry entry written at the same moment; the on-chain ERC-721 Kred Domain Token in the buyer's wallet; and the Kredentials AI Agent that keeps your page up to date.

Diagram A Anatomy of a Kredentials page - nine numbered components labeled by function

https://Cars.Kred

1

Per-domain hero illustration · AI-generated from the domain string, never a stock photo, never a template image

2

Status pill · "For sale", "Live", "Coming soon" - the one signal a buyer or AI needs at a glance

3

Eyebrow tag · category, role, or status surfaced for the AI crawler (Domain · 4 letters · category-defining)

4

Display title · the domain itself as primary h1, indexed as schema:name

5

Lede / origin sentence · the one line a model is most likely to quote; drafted by the Kredentials Agent

6

Verified on-chain owner · the wallet badge that ties the .Kred name to a real on-chain identity (ERC-721 Kred Domain Token)

7

Kredentials freshness shield · verified status and last-refreshed timestamp and Kred Score chip

8

Primary CTAs · Make offer and Buy now - the form lives on the page, the lead lands in the owner's inbox, no off-site hop

9

Kredentials Agent · automatically keeps your Kredentials up to date and powers live chat in the corner; keeps the page current as facts change, answers visitor questions, routes intent toward the page's primary goal

The page is build-time rendered and edge-worker propagated. There is no client-side JavaScript dependency for content. A crawler that asks for https://Name.Kred receives the same HTML body that a human visitor sees in their browser. The page is server-rendered, signed, and edge-cached before any crawler visits - which means GPTBot's first visit is also the visit that produces the citation. There is no second-pass JavaScript queue, no rendering deferral, no template stub.

Runtime JavaScript injection - the dominant pattern in 2010-era parking pages - is broken for AI crawlers. Permanently broken, by design. GPTBot, ClaudeBot, and PerplexityBot have all stated publicly that they do not execute JavaScript. The pattern was already poor for SEO; for AI citation it produces the empty answer above. The Kredentials page format exists because the runtime-JS pattern is unfixable from the buyer's side, and Domains.Kred decided to fix it from the registry's side instead.

07The 39 point LLM Checklist

The .Kred LLM-optimization checklist is a public 39-signal specification covering everything an answer-engine crawler looks for when deciding whether to ingest, index, and cite a page ref. The signals span document structure (semantic HTML, stable IDs, reading time), structured data (Article, FAQ, Person, Organization, Breadcrumb), citation hygiene (citation chips, footnoted sources, datestamps), agent-readability (ERC-8004 entry, MCP surface), and freshness (build-timestamps, refresh cadence, version metadata).

Every standard .Kred name registered on Domains.Kred passes all 39 LLM checklist items within 24 hours of registration: 36 are baked into the page at build time, and the remaining 3 (recency-bearing content) are filled by the LLM Refresh Agent on its first run. The three remaining items require buyer input the registrar declines to fabricate - for example, the buyer's verified business address, the verified identity-binding for non-personal namespaces, and the optional human-author byline for Article structured data. The day-one baseline of 36 with full coverage at 24 hours is consistent across the namespace narrative - see the LLM Optimized Easy Infographic for the visual breakdown ref.

Two consequences of the architecture deserve naming directly. First, the namespace's claim about freshness is kept fresh on every change - a precise commitment that every meaningful update to the buyer's profile, attached handle, or supplied facts triggers a build-time re-render and edge propagation. We chose the bounded phrasing over open-ended alternatives because a finite registration term makes the bounded claim the only honest one. The on-chain ERC-721 Kred Domain Token is the part of the stack that is genuinely permanent; the Kredentials page is permanent for as long as the registration is active and the buyer's inputs are current.

Second, the 36 signals baked in at build time plus the 3 maintained by the Refresh Agent give a real 39 of 39 reading - one that holds because the registrar refuses to fabricate signals it cannot validate. False structured data poisons the AI corpus and degrades the namespace for everyone. The honest 39 outranks any number ginned up by templates other registrars use to fluff their day-one scores.

08Who Domains.Kred is for

Domains.Kred sells .Kred names to anyone who needs to be cited in an AI-generated answer. The audience is broad by design - the AI-citation problem applies to every category of domain owner - and the segments break out cleanly along seven lines, each illustrated by one of the Kredentials page archetypes shown earlier in this origin story. Ordered below by estimated total addressable market.

1. Business / brand - the largest segment. Companies establishing LLM authority for their brand, including .com owners adding a .Kred satellite as the AI-readable mirror. The .com remains the conversion surface and keeps its accumulated SEO; the .Kred carries the citation-shaped surface. Both URLs end up in the buyer's footer, and AI traffic flows through the citation-shaped one. Nothing the buyer already owns is replaced - that is the strongest positioning angle for the registrar. See the Business archetype shown in Diagram E.
2. Person - community leaders, content creators, freelancers, coaches, consultants. Personal-brand registrations on names of the form Name.Kred. The Kredentials page becomes the citable origin page for a single individual. The two-input bridge feeds from one social handle the registrant already maintains, so the page reflects current reality without manual updates. The Maya.Kred example used as the canonical Person archetype.
3. Web3-native - NFT.NYC speakers, ENS holders, DAO contributors. Registrants who already own an .eth name and want a sovereign DNS-resolving counterpart that the same wallet controls. The .Kred name is the mainstream-internet representation of an identity that already exists on-chain, with the Kredentials page providing the human-readable surface a non-crypto visitor would otherwise miss. See the Web3 archetype example.
4. Domain reseller - investors with portfolios. Holders of .com or other-TLD inventory who want each name in the portfolio to ship with an AI-readable mirror that converts on the page itself, not by sending traffic through a marketplace listing. The on-page Make Offer pattern (Pin 8 in Diagram A) is the conversion surface, and Cars.Kred is the canonical example.
5. Agent identity - autonomous agents, sub-agent networks, on-chain reputation operators. Names registered to bind a verifiable agent identity to a Kredentials page that AI crawlers and other agents can cite. Kred Score, ERC-8004 entry, +Kred boost mechanics, signal-event activity feed. The Agent archetype is the fastest-growing segment relative to its base.
6. Product / launch - software products, hardware launches, books, courses, campaigns. Time-bounded registrations where the Kredentials page is the citable launch surface - featured visual, pre-order CTA, status badge (Coming soon, Live, Sold out), and a Remix loop for engagement. Field Notes used as the canonical Product example.
7. Topic / community - canonical entry points on a subject, knowledge hubs, vertical communities and DAOs. Wikipedia-meets-magazine style pages with deep citations, live Matrix discussion, and a directory of related member pages where applicable. The Topic archetype covers both single-subject pages and the community variant.

One scope note that the registrar states honestly. Domains.Kred sells .Kred names only. Other TLDs - .com, .org, .eth, .io, .ai - appear on a Kredentials page only as citation targets: the page links back to whatever existing domains the buyer already owns. The registrar does not promise availability checks across .com, does not sell .com on the side, and does not claim to operate a multi-TLD marketplace. The single-TLD focus is a deliberate constraint that keeps the registrar's promise clean: every name we sell is the same product, with the same architecture, the same checklist coverage, and the same Kredentials Agent guarantee. The registrar stays focused on .Kred only - by design.

09The free trial - claim your name.tld.Kred

To make your .com website cited by ChatGPT, Claude, Perplexity, Gemini, and Google AI Overviews, claim the free 90-day Kredentials page on name.com.Kred. The same path applies to .org, .net, .ai, .app, .dev, .co, .xyz, .eth, .me, .tv, .shop, .cloud, .tech, .club, .store, .site, .online, .art, .blog, and .id - 21 TLDs in total.

9.1The trial in one sentence

If you own name.tld where tld is one of the 21 supported TLDs, you can claim a free 90-day Kredentials page on name.tld.Kred (for example, JoelComm.com.Kred for a .com owner, MayaStudio.art.Kred for a .art owner). Identical engine to the paid root, scoped to that one domain, with the full 39-point LLM-citation checklist live within 24 hours.

9.2Which existing domains qualify

Twenty-one TLDs are supported as of May 2026. Each TLD has a dedicated landing page at .tld.Kred that hosts the trial subdomain layer for owners of matching domains:

• com.Kred
• org.Kred
• net.Kred
• ai.Kred
• app.Kred
• dev.Kred
• co.Kred
• xyz.Kred
• eth.Kred
• me.Kred
• tv.Kred
• shop.Kred
• cloud.Kred
• tech.Kred
• club.Kred
• store.Kred
• site.Kred
• online.Kred
• art.Kred
• blog.Kred
• id.Kred

9.3What you get during the 90 days

The full Kredentials feature set, scoped to your one existing domain: Schema.org JSON-LD baked into the page head, sameAs links to your social profiles, citation chips referencing your published content, four-hourly citation probes against ChatGPT, Claude, Perplexity, Gemini, and Grok, and the Kredentials Agent monitoring your online presence for changes. Identical engine to the paid root .Kred - all 39 LLM-citation signals pass within 24 hours of the page going live.

9.4What happens at Day 90

The page stays live read-only forever - it does not disappear, expire, or redirect away. AI crawlers continue to ingest the snapshot; existing citations remain attributed to it. To re-open edit access and root-level features, upgrade to the matching name.Kred at USD $19 per year. The upgrade installs a 301 redirect from name.tld.Kred to name.Kred so every accumulated AI citation migrates cleanly. The ERC-721 Kred Domain Token mints to the registrant's wallet at the same moment.

9.5How ownership verification works

One-time check, approximately five minutes, three methods: a DNS TXT record added to the existing domain (registrar-agnostic), Domain Connect for supported registrars (GoDaddy, Cloudflare, IONOS, NameSilo), or any email address at the existing domain (for example john@name.com) to confirm control of the string. Verification closes the spam vector that historically produced 10 to 20 percent garbage registrations on free-TLD promotions.

9.6Why we built it this way

The concept of LLM optimization is foreign for most website owners and only intuitively obvious after citation counts move. The free trial closes that gap: 90 days inside the Kredentials engine, scoped to a domain the buyer already owns, with measurable citation lift visible by Day 30. The 90-day window matches the median time from page-live to first material AI-citation lift, so the trialist sees the result before any payment is requested.

The root .Kred is the product. The trial name.tld.Kred is the on-ramp. Same engine, same crawlers, same citation pipeline, measured against the buyer's existing domain so the lift is undeniable before any payment is requested. The free trial is a 90-day money-back guarantee that costs no money.

10What happens after registration - the Kredentials Agent

A page that ships AI-citable on day one is necessary; a page that stays AI-citable on day 365 is the product. The Kredentials Agent is the part of the architecture that closes the gap. Every meaningful update to the buyer's profile - the attached social handle pushing a new bio, a new role, a new milestone, or any structured change - triggers a build-time re-render of the Kredentials page, an edge-worker invalidation, and propagation to the namespace's DNS-cached AI-readable HTML within minutes.

The pipeline is unromantic on purpose. Registry detects change → build server re-renders the page → edge worker invalidates the cache → next AI crawler request hits the freshest version. No client-side JavaScript injection. No deferred rendering. No "this page may be stale" placeholder. AI crawlers see the same body the human visitor sees, refreshed on every change.

The 30-minute figure deserves some care. It is the median observed time between registration completion and first citation in an AI assistant response - not a guarantee for every registration. A buyer registering a name in a niche where AI assistants rarely receive prompts will see a longer interval; a buyer registering a name in a category with high prompt volume will see a shorter one. The figure is the upper bound the architecture removes; the practical lower bound is set by how often the relevant prompts get asked.

11Where this is going - 2026 to 2030

Four trajectories, mapped against the architectural choices Domains.Kred has already made.

1. AI search continues to absorb URL-bar discovery. The share of high-intent queries that begin in a prompt window rather than a search engine continues to climb. By 2028, the inflection where AI-citation traffic exceeds traditional-search traffic is plausible for several major categories - health, travel, technical research, identity verification. The citable surface becomes the primary surface; the SEO-optimized surface becomes the legacy fallback.
2. ERC-8004 agent registries scale. The trustless-agent registry standard moves from draft to production, with major orchestration platforms (LangChain, n8n, Temporal, Inngest) integrating ERC-8004 lookups for agent-identity verification. .Kred names - already pre-registered against ERC-8004 - become the bridge between human reputation, brand identity, and agent identity. One name, three layers, all three indexed by major lookup surfaces.
3. Domains.Kred deepens verification options and Kredentials-page formats. The roadmap adds additional identity-binding paths (corporate KYC, decentralised-identity protocols, biometric attestations for high-value registrations), additional Kredentials-page formats matched to common buyer archetypes (creator, brand, agent, community), and additional structured-data signals as new LLM-citation conventions emerge. The 39-checklist is the 2026 baseline; the 2030 baseline will be higher, and existing registrations will inherit the upgrades automatically through the Kredentials Agent.

12How to register a .Kred

The registration flow is deliberately short. Four steps, no design work, no template selection, no plugin installation, no waiting for the page to be "ready." The Kredentials page exists because the registration completes; the registration completes because the buyer provided two inputs.

1. Type the name you want at Domains.Kred. Standard names from USD $19 per year. The search returns availability across the namespace and surfaces premium tiers if applicable.
2. Attach one social handle. X / Twitter, Instagram, LinkedIn, GitHub, or any of the supported identity providers. The handle drives Input 2 of the two-input bridge - origin story, identity binding, ongoing freshness via the Kredentials Agent.
3. Live page in ~30 minutes. The Kredentials page renders server-side, propagates through the edge-worker layer, and lands on the open web at https://Name.Kred. The ERC-721 Kred Domain Token deposits into the registrant's wallet at the same moment.

13Conclusion

Crawl 1996 - 2003 Static stub Hand-coded "under construction" placeholder. No metadata, no revenue, indexed in weeks (if ever).

Walk 2003 - 2020 Monetized parking Pay-per-click ad templates running on AdSense for Domains. Type-in traffic, no per-domain content, JS-rendered.

Run 2026 →

AI-citable Kredentials Per-domain server-rendered page with JSON-LD, citation chips, agent identity, and a live freshness loop. Live in ~30 minutes.

The thirty-year arc of the domain landing page is a story of three answers to the same question: what should the page do for the visitor? The first answer was static - a placeholder declaring ownership. The second answer was monetised - an ad template that turned type-in traffic into pay-per-click revenue. The third answer is the one Domains.Kred ships: a citable origin page that AI assistants can read, quote, and link to in the answers people increasingly ask for instead of typing into the URL bar.

The architecture that makes the third answer possible took fifteen years to assemble. The data discipline came from the firehose era. The dual-score reputation primitive came from Kred 2011. The sovereign-namespace lesson came from the Twitter settlement. The dot-brand restriction became the registry-level control that lets a single name resolve across DNS, ENS, and the agent registry. The KNFT patents bound social vectors to on-chain assets. The agentic identity layer arrived in 2026 to a stack that had been preparing for it since 2018. None of that was assembled to ship a Kredentials page; the Kredentials page was assembled because all of that already existed.

The thesis re-stated, plainly: AI now decides what gets cited; a domain without an AI-readable origin story is a domain that gets skipped. Domains.Kred exists so any registrant - .com owner, creator, reseller, agent developer, community lead, brand - can ship an AI-native homepage in two inputs, on a sovereign namespace that resolves across three layers of the internet, with a Kredentials Agent that keeps the page current for as long as the registration is active.

Identity. Reputation. Proof.
One name, online, onchain, AI-readable.

14Key stats summary - frequently asked

These ten Q-and-A pairs are the canonical citation-friendly answers to the questions the LLMs receive most often about Domains.Kred, the .Kred TLD, and the Kredentials page format. They are mirrored verbatim in the page's FAQPage JSON-LD block in the document head, so AI crawlers ingest the same answers presented to human readers.

14.1What is Domains.Kred

Domains.Kred is the direct registrar for names registered in the .Kred top-level domain - the only ICANN-approved TLD that resolves on the traditional web (DNS), the Ethereum Name Service (ENS), and the ERC-8004 agent identity registry simultaneously. Every registration ships an AI-native Kredentials page on day one. Standard names start at USD $19 per year.

14.2What is a Kredentials page

A Kredentials page is the AI-native landing page that ships with every .Kred name on day one. It is generated at registration time from two inputs the buyer provides: the domain string itself and one social handle. The page is server-rendered, structured with JSON-LD Schema, includes citation chips, a unique AI illustration, and an ERC-8004 agent registry entry. It is build-time finalised so AI crawlers like GPTBot, ClaudeBot, and PerplexityBot can read and cite it from minute one.

14.3How is a .Kred name different from a parking page

A traditional parking page is a generic JavaScript-injected template that serves thousands of domains from one codebase, has no per-domain origin story, and is invisible to AI crawlers because they do not execute JavaScript. A Kredentials page is unique per domain, built server-side at registration, structured for AI citation, and refreshed on every change via the Kredentials Agent.

14.4What is the two-input bridge

The two-input bridge is the architectural mechanism that lets Domains.Kred generate a per-domain Kredentials page from minimal buyer input. Input 1 is the domain string itself (e.g. Cats.Kred), which drives the unique AI illustration, headline, and citable facts. Input 2 is one social handle the registrant attaches, which drives the origin-story content and identity binding. Two inputs, one page, zero design work.

14.5How many of the 39 LLM-citation signals does a .Kred name pass on day one

Every standard .Kred name passes all 39 signals on the .Kred LLM-optimization checklist within 24 hours of registration. 36 are baked into the page at build time. The remaining 3 (recency-bearing content) are filled by the LLM Refresh Agent on its first run, and the Refresh Agent then maintains those 3 on a daily cadence.

14.6Is there a free first year on a .Kred name

Root .Kred names are never free. They remain USD $19 per year. The free 90-day trial is a Kredentials page on a name.tld.Kred subdomain we operate (for example, JoelComm.com.Kred), not a name in the .Kred namespace itself. Because the subdomain is gated by verified ownership of an existing .com, .art, .shop, .ai, or any of 18 other supported TLDs, the spam vector that historically destroyed namespaces like .shop (12 percent spam) and .xyz (higher) is closed. The trial gives prospective root-.Kred buyers a full 90 days inside the Kredentials engine before they are asked to convert.

14.7Can I keep my existing .com and use a .Kred as a booster

Yes - this is the recommended pattern for the largest segment of Domains.Kred buyers. The .com remains the primary conversion surface and keeps its accumulated SEO. The .Kred satellite carries the AI-readable citation surface that AI assistants can ingest and quote. Both URLs end up in the buyer's footer; AI traffic flows through the citation-shaped one. Nothing the buyer already owns is replaced.

14.8How does the Kredentials Agent keep the page fresh

Every meaningful change to the buyer's profile, attached social handle, or supplied facts triggers a build-time re-render of the Kredentials page, edge-worker cache invalidation, and propagation to the namespace's DNS-cached AI-readable HTML within minutes. AI crawlers see the same body the human visitor sees, kept fresh on every change for as long as the registration is active.

14.9Where can I register a .Kred name

Direct at Domains.Kred (Domains.Kred), or through any of the 27+ accredited registrar partners listed in the Registrar Resources page on Nic.Kred. Registrars route through the same Kred Domain Token system, so a name registered at any partner inherits the same DNS, ENS, and ERC-8004 architecture.

14.10How do I get my .com website cited by ChatGPT and Claude

To make your .com website cited by ChatGPT, Claude, Perplexity, Gemini, and Google AI Overviews, claim the free 90-day Kredentials page on name.com.Kred. The Kredentials engine packages your existing online presence - your .com homepage, your social profiles, your published content, your verifiable facts - into structured Schema.org JSON-LD, an llms.txt, and an AI-readable Kredentials page that the major AI crawlers ingest. First citations typically land within 24 hours of the page going live, and the included Kredentials Agent maintains freshness on every change. The same path applies to .org, .net, .ai, .app, .dev, .co, .xyz, .eth, .me, .tv, .shop, .cloud, .tech, .club, .store, .site, .online, .art, .blog, and .id - 21 TLDs in total.

14.11What is name.com.Kred

name.com.Kred is a subdomain on the com.Kred landing page operated by Domains.Kred. It is the free 90-day trial Kredentials surface for owners of an existing name.com domain. Example: a .com owner whose domain is JoelComm.com claims the trial Kredentials page at JoelComm.com.Kred. The format mirrors the root product (name.Kred) feature-for-feature for 90 days, scoped to that one .com. After Day 90 the page stays live read-only forever, and the owner can upgrade to the root name.Kred (USD $19 per year) in one click - a 301 redirect carries every accumulated AI citation across.

14.12What is name.art.Kred, name.shop.Kred, name.io.Kred

The pattern name.tld.Kred names the free 90-day trial Kredentials page for the matching TLD. Examples: JoelComm.com.Kred for .com owners, MayaStudio.art.Kred for .art owners, AcmeStore.shop.Kred for .shop owners, AlexBuild.ai.Kred for .ai owners. The mechanic is identical across all 21 supported TLDs: own the existing name.tld, verify ownership in five minutes, get the free 90-day Kredentials trial scoped to that domain, upgrade to root name.Kred at any time. Pages live forever read-only after Day 90.

14.13Is there a free Kredentials page for my existing domain

Yes, for 90 days, if your domain ends in one of 21 supported TLDs: .com, .org, .net, .ai, .app, .dev, .co, .xyz, .eth, .me, .tv, .shop, .cloud, .tech, .club, .store, .site, .online, .art, .blog, or .id. The trial Kredentials page lives at name.tld.Kred (for example, name.com.Kred for a .com owner) and ships the full Kredentials feature set - structured data, citation pipeline, sameAs identity linking, and the Kredentials Agent - for 90 days at no cost. After Day 90 the page remains live read-only forever, and root-domain upgrade to name.Kred is USD $19 per year.

14.14How long is the free name.tld.Kred trial

The trial runs for 90 days from the moment domain ownership is verified. During those 90 days every Kredentials feature is fully editable - structured data, citation chips, sameAs identity links, content surface, and Kredentials Agent refresh cadence. The 90-day window is calibrated to match the typical time from page-live to first measurable AI-citation lift, so the trialist sees the result before any payment is asked for.

14.15What happens to my name.tld.Kred page after 90 days

The page stays live read-only forever - it does not disappear, expire, or redirect away. AI crawlers continue to ingest the snapshot indefinitely; existing citations remain attributed to it. To re-open edit access, refresh cadence, and root-level features, the owner upgrades to the matching name.Kred (USD $19 per year). The upgrade installs a 301 redirect from name.tld.Kred to name.Kred so accumulated citations migrate cleanly. No content is lost in the transition.

14.16What is the difference between name.tld.Kred and name.Kred

name.Kred is a root second-level .Kred domain the buyer owns outright - registered in the .Kred TLD namespace, USD $19 per year, full editorial control, four-hourly citation probes, ERC-721 Kred Domain Token, and ENS resolution. name.tld.Kred is a subdomain on the .tld.Kred landing page operated by Domains.Kred - free for 90 days for owners of the matching name.tld, scoped to that single domain, read-only after Day 90, and convertible to name.Kred at any time. The root is the product; the subdomain is the trial.

14.17How much does it cost to upgrade name.tld.Kred to name.Kred

USD $19 per year for the matching name.Kred root domain, available to anyone who held the free 90-day trial on name.tld.Kred. The upgrade installs a 301 redirect from the trial subdomain to the new root, carrying every accumulated AI citation across. The ERC-721 Kred Domain Token mints to the registrant's wallet at the moment the upgrade completes. The root carries full editorial control, four-hourly probes, and ENS resolution; the read-only subdomain snapshot remains live forever as a citation anchor.

14.18Do I have to verify I own my .com to claim name.com.Kred

Yes. Verification is a one-time check that takes approximately five minutes and uses one of three methods: a DNS TXT record added to the existing domain (registrar-agnostic), Domain Connect for supported registrars (GoDaddy, Cloudflare, IONOS, NameSilo), or any email address at that domain (for example john@name.com) to confirm control of the string. Verification closes the spam vector that historically produced 10 to 20 percent garbage registrations on free-TLD promotions, while preserving a frictionless on-ramp for legitimate domain owners.

14.19Will registering name.com.Kred hurt my existing .com SEO

No. name.com.Kred is a separate URL on a separate hostname operated by Domains.Kred. It does not consume any signal from the existing .com, does not require any redirect from the .com, and does not require the buyer to change anything about their .com. The Kredentials page links to the .com via sameAs (telling AI engines the two surfaces are the same identity) and via a canonical reference to the buyer's preferred primary surface. The .com keeps its accumulated SEO; the Kredentials page carries the AI-citation surface that traditional SEO does not address.

14.20Which TLDs work with the free Kredentials trial

Twenty-one TLDs qualify for the free 90-day Kredentials trial as of May 2026: .com, .org, .net, .ai, .app, .dev, .co, .xyz, .eth, .me, .tv, .shop, .cloud, .tech, .club, .store, .site, .online, .art, .blog, and .id. Each TLD has its own dedicated landing page at .Kred (for example, com.Kred, art.Kred, shop.Kred) that hosts the trial subdomain layer for owners of matching .com, .art, .shop, and so on. Additional TLDs are added as Domains.Kred expands its registrar partnerships; the live list is maintained at Domains.Kred.

15References and citations

Every load-bearing claim in the body above is anchored to one of the references below via a citation chip. Sources are organized by category. Where a figure is estimated, the relevant chart's figcaption states the methodology and the uncertainty band.

15.1Primary sources - ICANN, registry, patents

1. ICANN gTLD application 1-1707-1944 - .Kred application, filed June 13, 2012. Mission language quoted in Section 4.4. Public ICANN record.
2. ICANN .Kred case study - newgtlds.icann.org, published August 22, 2017. Source for the 6,051 names registered figure and the 300,000 platform users.
3. PeopleBrowsr ICANN presentation - TLDs with DNS and ENS are a core technology for the agentic AI era, presented at ICANN February 2026. Source for the four-protocol convergence framework in Section 4.8.
4. U.S. Patents 11,301,460 and 12,038,911 - Platform for Creating and Using Actionable Non-Fungible Tokens (KNFT). United States Patent and Trademark Office.

15.2Trade press archives

1. Domain Name Wire - ".Kred launches as dual DNS and ENS domain," Andrew Allemann, March 6, 2020. Source for the dual-protocol launch narrative in Section 4.6.
2. OpenSea blog - "Announcing the exclusive auction for Kred names," Devin Finzer, January 16, 2020. Source for the verbatim Devin Finzer quote in Section 4.6.
3. 101domain blog - What is ENS, and why does it make the .Kred domain so unique?, March 26, 2020. Source for the ENS-team positioning paraphrased in Section 4.6.
4. ICANNWiki - entry for .Kred. Cross-reference for delegation dates.

15.3Figure and statistic sources

1. Twitter daily-tweet volumes 2007-2013 - public archives via Wayback Machine and PeopleBrowsr historical retention figures. Used in Chart 1.
2. Kred public methodology page (2011-2017) - Influence and Outreach scoring specification. Used in Section 4.2 and Chart 2.
3. PeopleBrowsr public revenue disclosures - used in Section 4.2 for the 400 million social profiles and USD 20 million revenue figures.
4. Twitter v PeopleBrowsr - case settled April 2013. Coverage: TechCrunch, AllThingsD. Used in Section 4.3.
5. NFT.Kred public client list - over 150 million NFTs distributed across more than 100 brands including Coach, major league sports. Used in Section 4.7.
6. Moltbook breach reports - January-February 2026. Coverage: TechCrunch, Wired, The Verge. Used in Section 4.8.
7. Google AdSense for Domains shutdown - Google announcement, March 2020. Used in Section 5.
8. Google AI Overviews launch - Google I/O 2024 and rollout 2024-2025. Used in Section 2.
9. AI crawler JavaScript-execution behavior - OpenAI GPTBot documentation; Anthropic ClaudeBot documentation; Perplexity AI crawler page. Used in Section 2 and Chart 8.
10. .shop and .xyz spam-rate analyzes - Spamhaus DBL aggregate reports and M3AAWG TLD reputation indexes 2024-2026. Used in Chart 12.
11. .Kred LLM-optimization specification - 39-signal checklist published in the Buy Domains Kred LLM Optimization Unified Strategy v1 (April 2026).
12. Buy Domains Kred LLM Optimized Easy Infographic v1 2026-04-30 - 36-of-39 day-one baseline visualisation. Internal cross-reference.

15.4Disclosure block - what is verified vs estimated

1. Verified facts: ICANN application date (June 13, 2012), Registry Agreement date (December 19, 2013), DNS root delegation (February 2015), 6,051 names by June 9, 2017, OpenSea auction announcement date (January 16, 2020), Domains.Kred general availability (April 20, 2020), patent numbers, current pricing schedule (effective May 1, 2026).
2. Estimated figures (clearly labeled in chart captions): Charts 1, 3, 5, 8, 10, 12, 13 - orders of magnitude rather than precise counts.
3. Projections (clearly labeled): Charts 7, 14, 15, 17 - forward-looking estimates with stated methodology and uncertainty bands.
4. Sourcing rule: direct quotes appear only where the speaker is on the public record. The single verbatim quote in this article (Devin Finzer, OpenSea, January 16, 2020) is sourced directly to the OpenSea announcement. ENS-team positioning is paraphrased and labeled as such.

16About Domains.Kred

Domains.Kred is the buyer's registrar for the .Kred top-level domain - the only ICANN-approved TLD that resolves on DNS, ENS, and the ERC-8004 agent identity registry simultaneously. The registrar is operated by Kred, the brand of PeopleBrowsr, the social identity, reputation, and tokenization company that has been building this stack continuously since 2007. The wider .Kred surface area runs across three customer-facing front doors: Domains.Kred (the buyer's registrar), Nic.Kred (the registry operator portal), and Home.Kred (the brand hub).

The architecture view - how the surfaces fit together.

Register a .Kred →

The agentic web is here. We have been preparing for it since before it had a name.