Where the passport is earned
GTR Dish Lab
Teach a robot to wash three dishes gently. The guardian's key signs a Robot Passport you download.
pboom.net/gtr95.html
ia.xyzAI agent identity · Guardian accountability · Interoperability
We’ve moved, and the move is the lesson. Some hotel, conference and office networks filter every .xyz address, good and bad alike, so our $2,500 ia.xyz kept getting stopped at the door while a $10 .net walks right in. Same page, same games, same passport, now at pboom.net: p(doom) counts the ways this goes wrong, p(boom) bets it goes right. Reputation still travels by neighborhood instead of by name. That’s the VoC (Voice of the Customer) moment, and it’s exactly the problem agent identity has to fix. ia.xyz stays up as the original.
ia.xyz The global IA arbitrage: 1.2B+ Romance-language speakers say AI as IA, intelligence artificial (ES FR PT IT CA RO LA) · Bridging Web2 DNS and Web3 agent identities for public benefit
ICANN 2026 gTLD round · IA XYZ Benefit LLC · ASP IXBL2597-A70 approved · Application IXBL2597-T54394 · Status: submitted · active · ICANN87 Bali, 17–22 Oct
IA · internet agent identity, 2026’s big shift: DNSid · GoDaddy ANS · Microsoft Entra Agent ID · DNS-AID · Verisign DAN — test identity and graduation in our Agent Passport Laboratory ↓
Win the AI Race® Where everybody wins.
Jensen Huang: “everybody wins” 27:15Winning means: people in control, agents accountable, benefits shared.
AI agent identity. Accountability that travels.
One robot. Two games. One passport.
A robot earns a signed passport in one game and carries it to the next, which checks it and sets its own permissions.
WIN THE AI RACE® · AI RACE® — registered trademarks of Mama Protocol LLC · USPTO ↓
Hardware & infrastructure — chips, memory, power, supply chains & models ↓
Identity before autonomy · Care before scale · Public benefit by design
GTR-6 · Guardian Transfer Robots® — a Mama Protocol® simulation world where agent identity is earned, carried and checked. What would Mother do?
Where the passport is checked
Win the AI Race®
Drop the passport at Robot Passport Check. A valid one earns a road permit. An edited or revoked one is turned away.
pboom.net/race.html
Watch the demo · 4:01
Pop-ups blocked? Open each game in a tab, then snap with Windows key + ← and →.
Agent Passport Laboratory
Built like a game, run like a lab: test agent identities, guardians and graduation. Bring any agent’s passport—ours or anyone’s. We read it, check what we can, and the destination decides.
- Formatwhat the file is
- Signaturewho vouched for it
- Datesstill in force
- Issuer trusta key we trust
- Statusnot revoked
- Holderholds the private key
- Destination decidesits own permissions
Start with an official provider example below, or bring a supported file to the desk. The report separates format, signature, issuer trust, dates, status and holder evidence. Examples stay in this browser unless you explicitly request an issuer-key lookup.
See the GTR-6 demonstration ↑Signed public test fixture
DNSid lifecycle bundle
A real public conformance bundle with issuance and key-rotation evidence. Its fixed June 2026 expiry is in the past.
Synthetic upstream example
GoDaddy ANS transparency leaf
The official SDK’s schema example uses fake signatures and placeholder certificate hashes. It is not a usable credential.
Decoded documentation example
Microsoft Entra agent claims
Readable claims from Microsoft’s documentation. The signature and enclosing token are absent.
Unsigned discovery example
DNS-AID agent metadata
Connection settings and declared capabilities from the official metadata contract. Discovery metadata does not grant access.
Different evidence, different checks. Provider examples here are for inspection. The generated GTR and standards samples below exercise the local signature verifier. No provider integration or production trust root is established merely by importing a file.
What travels between systems—and what offline verification establishes
There is no single universal passport file. Signed JSON, JWTs, certificate chains, DNS records and lifecycle bundles carry different evidence. Signatures protect integrity; HTTPS or mTLS encrypts data in transit. Neither replaces the receiving service’s issuer-trust and authorization decisions.
GoDaddy ANS: its documented model combines identity receipts, short-lived status evidence and mTLS or DPoP key possession, followed by OAuth authorization. Offline verification uses supplied evidence and configured public keys. Its one-hour default status lifetime limits how quickly an offline verifier observes revocation. Engineering source ↗
DigiCert: stopping an agent’s authority requires participating gateways or other enforcement points. A revoked identity alone is not a universal process-termination mechanism. Agent-trust architecture ↗
DNSid: a bounded test with the official SDK
The supplied lifecycle bundle was checked with the upstream Python SDK under its disposable test trust policy. It passed at the fixture’s frozen 25 June 2026 clock, failed as stale on 17 October 2026, and failed after a signature change. This checks that particular offline bundle; it does not authenticate a live agent, resolve DNS, or grant access. The browser above remains an inspector.
Download the exact SDK check report · Pinned upstream fixture ↗
Passport inspection desk
Import a supported passport, certificate, public key or provider example. Cryptographic results and demo access decisions are reported separately. Use public or disposable test data; this desk is a browser prototype.
Drag the file from your Downloads folder. A browser’s download panel hands over a link, not the file.
Paste the passport text instead
Locally signed GTR demo cases
Locally generated standards examples · not vendor-issued passports
Try this: check the RSA token, trust the root on the X.509 chain, then check the token again. Both chain to the same root.
Keys trusted by this demo session
- Preparing local sample keys…
Add a key you trust
A public key proves nothing about its owner until you establish that binding. Add trust only after comparing a key with an independent issuer source. Demo trust resets on reload.
Inspection reportIndependent checks · local demo policy
Drop a passport here, tooEither side of the desk works. You can also paste one or pick a sample.
Supported formats and verification limits
| Evidence | Checks performed by the current browser prototype |
|---|---|
| GTR Dish Lab passport | Guardian ECDSA P-256 signature, record integrity, required dates and local demo trust. The receiving demo assigns its own permissions. |
| JWT / JWS and VC-JOSE | Supported ECDSA, RSA, RSA-PSS and EdDSA signatures, available claims and local key trust. A valid signature is not a provider-specific token-validation integration. |
| SD-JWT | Issuer signature, disclosed-claim digests and an attached holder signature where supported. No fresh interactive nonce or complete live possession check is performed. |
| W3C Data Integrity | Supported JCS-based proof suites. JSON-LD RDF canonicalization and BBS proofs are not implemented. |
| X.509 / PEM | Supported certificate signatures and dates. This is not full PKIX validation: CA constraints, key usages, critical extensions, hostname, revocation and complete path-policy checks are not implemented. |
| Ethereum signatures and A2A cards | Supported wallet-signature checks and signed-card evidence. No on-chain reputation or complete provider authorization check. |
| DNSid, ANS, DNS-AID and Entra examples above | Structure, declared fields and readable timestamps. Provider signatures, lifecycle completeness, DNSSEC, issuer trust and live holder possession are not validated here. |
| DigiCert / Workday integrations | Official documentation is linked. A public signed provider fixture and the corresponding verifier adapter are not yet integrated. |
A demo permit is an educational policy result on this page. Real access must be enforced by the receiving application, using trusted issuers and sufficiently fresh evidence.
Who is building agent identity?
Potential integration partners across naming, credentials, governance and enforcement.
At ICANN87 in Bali this week? We’re seeking integration partners—bring a test passport, issuer key or revocation case.
Talk integrationEach system supplies different evidence. An adapter must recognize its format, check its proofs, establish trusted issuers and apply the receiving service’s policy.
DNS accountability and lifecycle
DNSid · Known / Identity Digital
DNSid links an agent domain to an accountable entity, keys, status and lifecycle evidence. Its open Developer Kit includes Go, TypeScript and Python SDKs plus a conformance suite.
On this page: Public conformance sample available. This page inspects its structure and dates; complete DNSid validation requires a version-specific adapter.
Agent identity, policy and enforcement
DigiCert · AI Trust Manager
AI Agent Passports bind agent identities to accountable owners and policy. Its enforcement points and MCP gateways can permit, deny or terminate participating agent sessions when trust changes.
On this page: Official issuance documentation linked. A provider-issued sandbox passport and integrated enforcement test are still needed.
DNS identity and verification
GoDaddy · Agent Name Service (ANS)
Versioned agent identities anchored to domain control, certificates and a public transparency log. Useful for discovering an agent and checking its identity evidence before a connection.
On this page: Public synthetic ANS fixture available. Receipt/status verification and live proof of key possession are not integrated here.
Enterprise identity and governance
Microsoft · Entra Agent ID / Agent 365
Entra Agent ID manages agent identities, permissions and identity policy. Agent 365 provides the consolidated inventory and management experience for agents across an organization.
On this page: Public decoded claims example available. An Entra tenant integration and resource-specific token validation are still needed.
Independent attestations and enterprise governance
Workday · Agent Passport / Agent System of Record
Agent Passport records independently signed safety attestations and supports ongoing policy enforcement. It complements Workday's enterprise agent inventory and governance work.
On this page: Product and launch information linked. No public signed sample or open wire format was confirmed for this page.
Agent discovery and connection metadata
Infoblox / Linux Foundation · DNS-AID
A DNS-based discovery project initiated by Infoblox. Publishes agent endpoints and connection metadata through existing DNS records, with optional signatures and DNSSEC-related validation.
On this page: Public unsigned metadata example available. DNS lookup, DNSSEC and identity authentication are not performed here.
DNS naming and discovery research
Verisign · DNS-Based Agent Naming (DAN)
DAN proposes agent discovery and index records for DNS. Verisign publishes an Internet-Draft and a proof-of-concept that generates and reads those records.
On this page: Public record generator and proof of concept linked. A DNS-discovery adapter is not integrated here.
Guardian-linked passports · our format
IA.XYZ · GTR-6 agent passport
A guardian’s key signs what the agent earned; any destination can verify it and set its own permissions. Built to accept other issuers’ passports alongside our own.
On this page: Signed demo passports verify live in the desk above, including forged and untrusted cases. DNS-published guardian keys are next.
Open standards and adjacent infrastructure
| Source | Relevance |
|---|---|
| W3C Verifiable Credentials 2.0 | A model for issuer claims and their verification; issuer trust and access policy are separate. |
| A2A agent cards | Descriptions, endpoints and declared capabilities. A card alone does not prove authority or safe behavior. |
| ERC-8004 | Agent identity, reputation and validation registries. A registration entry is not a local access grant. |
| NIST: agent identity and authority | Public engineering work relevant to agent authorization and accountability. |
| AWS AgentCore Identity | Agent identity and access to tools and services; a separate enterprise integration track. |
| Google Cloud Agent Identity | SPIFFE-based agent identities, X.509 certificates and OIDC credentials, with lifecycle and access controls. |
Briefing
ICANN naming, intellectual property, infrastructure, public trust, the demo and the people behind it.
ICANN · gTLDs — at risk: naming opportunity · .iam in contention · 13 .agent applicantsReplacement period ends 21 October 2026, 23:59 UTC · ICANN87 Bali · Full applicant directory ↓
01 / Naming infrastructure / Checked 17 October 2026
Replacement-period deadline: . Only an eligible replacement designated in the application may be selected. String Confirmation Day is scheduled for . ICANN timetable ↗
IA XYZ Benefit LLC: IXBL2597-T54394 · primary string .iam · ASP IXBL2597-A70, approved 10 April 2026 · Active / Pre-Evaluation Processing in the public record. A filed application is not a delegated TLD.
Meeting context: ICANN87 · Bali, Indonesia · 17–22 October 2026. We welcome technical conversations about portable identity, verification evidence, guardian relationships and independent access policy.
.agent: all 13 primary applicants
Winning .agent is not winning identity management. Whoever operates .agent—or .iam, .ai or .com—still needs passports that travel between registries, platforms and countries. That trust layer is where we want to work with every applicant below.
These organizations are potential technical counterparts. Their entries below describe proposed registry purposes in their published applications; they do not establish an IA.XYZ partnership or a live passport service.
13 applicants
Download both rosters
| Legal applicant / group | Proposed focus | Official ICANN records |
|---|---|---|
| Charleston Road Registry Inc.Google Registry / Google | Open, standards-oriented namespace for online AI agents and related services. | CRRI2564-T76881Applicant’s published responses ↗ |
| ECHO Domain Co L.L.C.EchoStar | Namespace for AI agents, agent platforms, and human agency professions. | EDCL2689T-T94739Applicant’s published responses ↗ |
| Elegant Leader LimitedAlibaba Group / Alibaba Cloud | Agent endpoints and documentation, with registry security policies and open registrar access. | ELL2677T-T98634Applicant’s published responses ↗ |
| FireLabs Capital LtdMeitu | Open namespace for agency services and intelligent-agent technologies. | FCL2696T-T15158Applicant’s published responses ↗ |
| Intercap Registry Inc.Intercap | Unrestricted namespace for human representatives and software acting on behalf of users. | IRI2679T-T53136Applicant’s published responses ↗ |
| Internet Land & Cattle LLCInternet Land & Cattle | Namespace spanning professional agents, delegated services, software, and AI automation. | ILCL2673T-T99017Applicant’s published responses ↗ |
| Ipollo Tech LtdNano Labs | AI-agent identity and discovery for developers, platforms, enterprise users, and researchers. | ITL2677T-T74240Applicant’s published responses ↗ |
| Meta Registry Holdings LLCMeta Platforms | Namespace for eligible registrants associated with the term, backed by registry trust and security policies. | MRHL2653T-T66196Applicant’s published responses ↗ |
| Open Agent Registry, Inc.Open Agent Registry / Agent Community | Community application centered on verified operators, accountable principals, and discoverable agent records.Community application | OARI2643T-T22843Applicant’s published responses ↗ |
| OPENAI OPCO, LLCOpenAI | Open registration without model, platform, provider, technology, or industry eligibility restrictions. | OOL2614T-T24226Applicant’s published responses ↗ |
| Radix Technologies Inc SEZCRadix | Namespace serving human-agent professions and AI/software-agent builders and operators. | RTIS2674T-T51870Applicant’s published responses ↗ |
| Rein Check, LLCIdentity Digital | Broad agent-related namespace using established registrar distribution and registry infrastructure. | RC2677T-T71607Applicant’s published responses ↗ |
| XYZ.COM LLCXYZ | Open, unrestricted generic namespace available through ICANN-accredited registrars. | XL2625T-T26605Applicant’s published responses ↗ |
Two different organizations: Open Agent Registry, Inc. and OPENAI OPCO, LLC are separate applicants. Rein Check, LLC is the Identity Digital applicant.
.iam: four primary applicants, including IA.XYZ
| Legal applicant / group | Proposed focus | Official ICANN records |
|---|---|---|
| easyDNS Technologies Inc.easyDNS | Open, protocol-neutral identity namespace for people, organizations, services, and AI agents. | ETI2627T-T93610Applicant’s published responses ↗ |
| IA XYZ Benefit LLCIA.XYZ · Our application | DNS-rooted namespace for verifiable digital identity and accountable autonomous systems. | IXBL2597-T54394Applicant’s published responses ↗ |
| Link Freedom Group LtdLink Freedom Group / Nova Registry | Portfolio registry application emphasizing commercially useful naming and sustainable registrar distribution. | LFGL2683T-T39419Applicant’s published responses ↗ |
| The Incite Group, LLCThe Incite Group | Human-centered namespace for personal AI agents linked to identifiable, accountable individuals. | TIGL2633T-T28238Applicant’s published responses ↗ |
Conversation boundary: easyDNS Technologies Inc., Link Freedom Group Ltd and The Incite Group, LLC share the .iam contention set with IA XYZ Benefit LLC. Routine technical or business conversations must not convey information about contested applications or strategy. Replacement-choice discussions, bidding, withdrawals and private contention arrangements are outside our interoperability conversations. ICANN Applicant Guidebook, §§5.1.4 and 5.2.3.1 ↗
The authoritative guidebook permits routine business communications that do not convey application or strategy information. This directory publishes factual records and technical context. It does not invite coordination of application choices.
Sources: Official Reveal Day contention list · Current public application directory · all 17 summary and application-response pages checked 17 October 2026. Primary and replacement rows belong to the same underlying application and must not be counted as separate applicants.
Adjacent registry work: GoDaddy / Registry Services · .agentid · Verisign Informed / certificate-status work. See the provider directory for ANS, DAN, DNSid and agent-identity documentation.
WIN THE AI RACE® · AI RACE® — registered trademarks of Mama Protocol LLCUSPTO records, copy-a-serial, and patents pending
WIN THE AI RACE®Mama Protocol LLC · Reg. 8175320 · Serial 99318483
AI RACE®Mama Protocol LLC · Reg. 8217116 · Supplemental Register · Serial 99381360
02 / Intellectual property / Registered brands
There’s more than one way to “Win the AI Race.”
The best way to win the AI race is the one where everybody wins. Our contribution joins portable identity, guardian accountability and a public-benefit mission under a registered brand portfolio.
The product goal is a passport that identifies the robot, records what an issuer says it has earned, and names the guardian who answers for it. Independent destinations still decide what they trust and what they permit.
Trademarks protect brand identifiers for relevant goods and services; patents and patent applications are a different kind of intellectual property. A trademark record is not technical certification, ICANN approval, or ownership of AI itself. USPTO: the distinctions
Patents pending
Multiple provisional patents are pending on post-quantum agent identity, agent parentage and key rotation, and DNS-linked distribution of public benefits—so the public-benefit mission has a mechanism, not just a promise. Pending provisionals are not granted patents or deployed services.
Trademark portfolio
| Mark | Status | USPTO TSDR record |
|---|---|---|
| MAMA PROTOCOL® | Registered, Reg. 8100381 | 99185559 |
| GUARDIAN TRANSFER ROBOTS® | Registered, Reg. 8165308 | 99231579 |
| WIN THE AI RACE® | Registered, Reg. 8175320 | 99318483 |
| AI RACE® | Registered, Reg. 8217116 (Supplemental Register) | 99381360 |
| AI MOM™ | Pending | 99318472 |
| WHAT WOULD MOTHER DO WWMD?™ | Pending | 99318802 |
| VIBE CODING™ | Pending | 99119691 |
| VIBE WRITING™ | Pending | 99119649 |
Mark names open USPTO trademark search; serial numbers open the live TSDR status record. Use “Copy serial” to paste a number into TSDR or USPTO search.
Hardware & infrastructure: a great model is not enoughGPUs, CPUs, memory, power, transformers, minerals, deployment and the model race
03 / Physical infrastructure & capability / Supply risk
You can lead on intelligence and still lose on delivery.
Our risk map separates the physical systems AI runs on from the naming layer above. Compute has to be manufactured, powered, cooled, connected and maintained. Model performance is another dependency, not a substitute for the rest.
Chips, memory & the whole machine
Track GPUs and CPUs alongside high-bandwidth memory, storage, advanced packaging, networking and repair capacity. Buying an accelerator is not the same as having a working system.
Evidence: Stanford flags concentrated leading-chip fabrication; Micron’s 2026 announcement illustrates the memory and storage stack supporting AI systems. Stanford AI Index · Micron HBM4 / memory announcement
Power, transformers & connections
The IEA’s 14 October 2026 report identifies grid strain, electrical-equipment supply constraints, long connection queues and slow permitting. Our checklist includes transformers, switchgear, cooling and credible delivery dates.
Energy: compare complete systems
Compare grid supply, natural gas, renewables with storage, nuclear and geothermal by reliability, total cost, water use, emissions and time to operation. Treat backup fuel and generators as a separate resilience question, not a complete energy strategy.
Planning criteria, not a recommendation for a particular project. The IEA reports growing diversity in power procurement and announced onsite generation. IEA energy-integration findings
Mines, materials & the people who build it
Our checklist extends to copper, critical minerals, refining, components, logistics, skilled workers and local approval. The IEA documents mineral dependence across semiconductors, robotics, servers and AI data centres.
Models: no permanent country podium
Stanford’s 2026 review says U.S. and Chinese models have traded the lead and their performance gap has narrowed substantially. That does not establish a permanent first, second or third place for countries.
Our comparison criteria: task success, reliability, cost, efficiency, openness, language coverage and real-world usefulness. Capability is not proof of safe autonomy.
Stanford AI Index 2026, technical-performance takeaways · Report-period findings, not a live leaderboard.
Space & other frontier proposals
ESA is examining space-based data centres and has announced a strategy forum for November 2026. Keep ambitious ideas in view, but distinguish exploration and announced plans from delivered capacity.
Our planning rule: evaluate power, heat rejection, launch, communications and servicing before counting on a deployment. ESA space-based data-centre initiative
Where IA.XYZ fits: we are not claiming to build the chips or solve the grid. We are developing an accountability layer for the agents using that infrastructure: identity, a responsible guardian, scoped permission and revocation. Our prototype should stand on what it demonstrates.
Hearts & minds: public trust has to be earnedPeople need agency. Robots need accountable boundaries. Care is something to test.
04 / Public trust & care / Adoption risk
The most capable AI is not automatically the AI people will welcome.
Ipsos’s 2026 AI Monitor asked whether AI products and services bring more benefits than drawbacks. Agreement differed sharply across markets:
85%China survey sample
38%United States survey sample
63%Colombia survey sample
Survey fieldwork: 20 March–3 April 2026; 23,532 adults across 32 countries. China and Colombia samples skew more urban, educated and/or affluent; Ipsos describes them as the more connected segment, not the entire population. The U.S. sample is considered representative of adults under 75. Results, page 13 · Methodology, page 48
Listen before asking for trust
Jobs, privacy, deception, control, water and electricity costs are questions to address, not objections to dismiss. The IEA links data-centre integration to community concerns about prices, emissions and water; Ipsos finds that excitement and nervousness often coexist.
Our proposal: family-friendly care practice
Use games and simulations to make responsibility visible: ask permission, respect property, help with a task, admit an error and stop when permission is withdrawn. Give families a way to understand and question the system, not just watch a polished promise.
Our goal is the opposite of a crime-reward loop: teach the robot not to steal; reward care, not harm.
Care as behavior — not a claim about feelings
For today’s agents and robots, we propose observable tests: does the agent request permission, stay inside its scope, reveal mistakes and honor revocation? Extending that ambition to future AGI or superintelligence is a research goal, not a capability this browser demo establishes.
Show the limits as clearly as the successes. A signed passport can support accountability. It does not prove kindness, consciousness, child safety or solved alignment. Family-friendly is a design intention here, not an official age rating. Any family-facing pilot still needs appropriate privacy and safeguarding review.
The two-minute demoEarn a passport in Dish Lab, carry it to the race, then forge and revoke it
- Open both games side by side. Two single-file pages, no account.
- In Dish Lab, wash three dishes gently. Rushing teaches the robot badly.
- Create the Robot Passport and download it. Your browser signs it with the guardian key.
- Drop it at Robot Passport Check in the race. Same robot, same ID, now allowed to drive.
- Drop the forged copy, or change one character. The signature fails and the race turns it away.
- Revoke the robot back in Dish Lab. The race parks it.
The passport records what its issuer says the robot learned. The receiving game decides what it may do there.
Working demonstrations: two games, one HTML file each, running in the browser. The GTR passport format uses WebCrypto signatures (ECDSA P-256 with SHA-256). Changes to signed credential data invalidate its signature. This desk verifies its supported signed demo formats and applies local demo policy; the provider examples are inspection only.
Not yet: no live DNS lookup, and both games are served from one domain (this page and its mirror). Next, the race moves to a second, independently run domain, and the guardian's public key is published in DNS under the robot's own domain so any site can verify it. That works on .com, .ai or .xyz today, and on .iam if ICANN awards it.
Inside passport.jsonThe sample on this page, field by field, and the four rules every passport follows
{
"schema": "iaxyz.gtr_transfer_credential.v1",
"credential": {
"passport_id": "RP-16A40EB6",
"robot_name": "DISH-01",
"guardian": "Your family",
"care_grade": "B",
"care_score": 78,
"license_plate": "GTR-0EB6-B",
"audience": "race.ia.xyz",
"issuer": {
"name": "GTR Dish Lab demo guardian",
"key_fingerprint": "sha256:3b55509be669df4a3691f9068485db47"
},
"issued_at": "2026-10-16T15:05:13.569Z",
"expires_at": "2026-11-15T15:05:13.569Z",
"digest_source_json": "{\"robot_name\":\"DISH-01\",\"guardian\":\"Your family\",\"stats\":{\"careGrade\":\"B\",\"careScore\":78,\"dishesWashed\":3,\"rushed\":0},\"lessons\":[\"rinse\",\"scrub\",\"dry\"],\"completed_at\":\"2026-10-16T15:05:13.569Z\"}",
"training_hash": "sha256:10eeb25db54c910705fe1fb1da0e37930503fce4a62da3a7729de7b702fe9ef2"
},
"credential_hash": "sha256:d36d6868a912c568a21ece7cc6d34717dc8da839fa3d538b58e2fe621717b174",
"proof": {
"alg": "ECDSA-P256-SHA256",
"signed_field": "credential_hash",
"public_key_jwk": {
"kty": "EC",
"crv": "P-256",
"x": "urmciiXqAA9Pz9-SYfgwiGH6hWalYAnP5pztMhlGQfQ",
"y": "BrL9pBLRyuQjnFTd5v2TmcDjGkxYgJxEbZg2NaVR_GE"
},
"signature_b64": "+uojJ9HVP658kAXPDkGL8XXBD35QSK49wBYy6ZNYUvbQyySjnZTkr+TItqEcSxv0qwfRieuVC064WIITcl4mKg=="
}
}
- Many issuers, one readable file.ia.xyz issues this passport. Others will issue their own, the way countries do. A clean format lets any border desk read it.
- The destination decides.A signature proves who vouched for the agent, not that a site must let it in. Each world chooses which issuers it trusts and what an accepted passport unlocks.
- Every passport names a guardian.No issuer, anywhere, should mint a passport without an accountable human on it.
- Revocation fails closed.If the guardian withdraws consent or the status can't be confirmed, protected actions stop.
An agent can go where its guardian can't: across a border, into a shop, to pick something up and bring it home. That only works if the guardian stays on the record the whole way. This sample is signed with a key made in your browser when the page loaded, so it won't import into the race. Earn a real one in Dish Lab.
AI. IA. Identity in every language.The original ia.xyz mission: 1.2 billion+ speakers who say it backward, agent lineage and public benefit
Where English says artificial intelligence, the Romance languages say it the other way round—IA. That is where ia.xyz began: a namespace for more than a billion people underserved by English-first technology, bridging Web2 DNS names and Web3 agent identities.
ESinteligencia artificialFRintelligence artificiellePTinteligência artificialITintelligenza artificialeCAintel·ligència artificialROinteligență artificialăLAintellegentia artificialis
The passports on this page are written in IA XYZ Interlingua: one readable format, whatever language the guardian speaks.
Agent swarm genealogy
Identify an agent’s responsible guardian and preserve a verifiable record of parentage and delegated authority.
Independent destinations
Let each service set its trusted issuers and permissions while an agent carries evidence between environments.
Public-benefit distribution
Transparent, DNS-linked mechanisms for sharing value with the people AI serves. Patent-pending; a research and funding goal, not a live service.
Identity before autonomy. Care before scale. Public benefit by design.
What would Mother do? · Reinforcement learning from mother feedback
Many ways to win the AI raceWe started at the USPTO and kept going: films, trailers and songs
There's more than one way to win the AI race, and the best one is where everybody wins: humans and AI together. We've tried it in patents, trademarks, books, games, films and music, all made by a family and a few chatbots.
- Mama says there's more than one way to Win the AI Race®The short version of this whole section.
- We Build TomorrowThe 68-second outro written for the Moonshots podcast.
- Who Gave You the Keys?The music-video movie trailer for Win the AI Race® and What Would Mother Do?
- The first transmissionThe original short film, submitted to the Future Vision XPRIZE.
- The .IAM application videoAn earlier video on Mama Protocol and our ICANN gTLD application.
- The director's uncut versionThe longer cut of the tribute concept.
- Y Combinator application videoThe pitch as submitted.
Music videos are AI-generated tribute concepts. People and shows mentioned are linked as sources; no endorsement is implied.
Founder and benchmarkingForty years from DNS names to people, companies and now agents
Michael Core
Founder, President and CEO, IA XYZ Benefit LLC. About 40 years in identity and trust infrastructure: commercial DNS and whois at AT&T Bell Labs in the NSFNET era, including the InterNIC directory host ds2.internic.net, then roughly two decades as a Managing Security Consultant at IBM in enterprise identity and access management. At IBM he was also product and program manager for ISCIP, a customer-information portal for about 20,000 users, and led human-feedback data curation behind a Watson-based support assistant.
At IBM he also built an entity-resolution system that collapsed 125 spellings of one bank's name into a single searchable record. The agent registry gets that same roll-up: one agent, one record, however many names it travels under.
- Names for machinesDNS at Bell Labs
- Identity for peopleEnterprise IAM at IBM
- Identity for companiesEntity resolution for CRM
- Identity for agentsIA XYZ passports, ia.xyz and .iam
- CISSP (formerly held)
- PMP
- Scrum Master (PSM)
- ITIL
- AWS certified
- IBM Design Thinking
- IEEE member
Benchmarking everything
- ICANN 2026 new gTLD round: the .iam application, with Applicant Support
- NIST, AI agent identity submission
- Y Combinator, Fall 2026 application
- LAUNCH and This Week in Startups, application
- All-In Podcast, pitch
- Moonshots, music-video submissions
- Future Vision XPRIZE, film submission
- Grok Imagine and Odyssey challenge, film submission
The thesis: infrastructure is destiny. Agent accountability needs architecture, not probabilistic alignment alone.
The conversations behind the idea
Start with Mo and Hinton, then the Moonshots discussion. Finish with the musical tribute.
-
14:39
Mo Gawdat on parenting AIMoonshots EP #51 with Peter Diamandis. The parenting segment selected for this project; broader official chapter begins at 15:48.
-
28:00
Geoffrey Hinton on the mommy modelNayeema Raza’s Smart Girl Dumb Questions. The conversation about teaching AI to care; opens at the “Can We Teach AI to Love Us?” chapter.
-
1:50:56
Moonshots asks for one agent across every modelOctober 2026. A viewer asks whether one system can work with whichever AI is best. Salim Ismail answers: one trusted personal agent, moving across models on open standards. Our project explores how an accountable identity could travel with it.
-
Song
The Moonshot the World MissedThe song on the idea: a name, a guardian and a record before autonomy.
Also: We Build Tomorrow, the 68-second Moonshots outro.
Music videos are AI-generated tribute concepts. People and shows are linked as sources; no endorsement is implied.
Selected Hinton excerpt: 36:53 ↗. Timestamps are editorial starting points retained from the project’s source notes.