Universal Data Exchange Standard

121XML: Vendor-neutral, self-describing data format that enables perfect portability across all AI platforms, protocols, and schemas

Why 121XML?

78%
Token Savings
0%
Information Loss
Vendor Support
100%
Data Sovereignty

🔄 Universal Protocol Support

Works with REST, gRPC, GraphQL, WebSocket, SOAP, and unlimited custom protocols. One codebase, all protocols.

📊 Schema Agnostic

Supports JSON Schema, XSD, Protobuf, GraphQL, and custom formats. Lossless translation between any schemas.

🎯 Content Addressing

Immutable SHA256-based addressing enables perfect caching, cross-platform references, and token efficiency.

🔐 User Sovereignty

Data stays encrypted with user-held keys. Only references shared. Instant revocation. Complete audit trails.

🚀 Vendor Portability

Export agents as 121XML profiles. Work on Claude, GPT, Gemini, Llama without modification.

⚙️ Plugin Extensibility

Add protocols and schemas via plugins. Plugin framework with sandboxing ensures safety and isolation.

Core Concepts

Three Axioms: Foundation for Universal Code Generation

A1: Composition over Inheritance

No class hierarchies. All structure via nested maps. Enables representation in Rust, Go, C++, Python, JS, Java without inheritance mechanisms.

A2: Explicit Type Tags

Polymorphic fields MUST have explicit type markers. Enables schema-free parsing at receiver (no schema fetch needed).

A3: Homogeneous Sequences

All array elements MUST be same type. Enables pre-allocation without knowing content.

Four Rules: Integrity, Immutability, Schema Discovery

R4: Keys Sorted Alphabetically

All map keys sorted by Unicode code point → Deterministic byte order → Stable SHA256 hashing

R5: Null is Explicit

Three states: value (set), null (known but empty), absent (key never set) → No ambiguity

R6: Profile URI

All objects declare schema via URI (urn:121xml:type/1.0) → Schema discovered at receiver

R7: SHA256 Hash

Immutable address: data://sha256:ABC123:type → Tamper detection and content addressing

Sovereign Data Architecture

Data lives where the user decides, secured by the user. Three-layer model:

Layer 1: User Decision

User EXPLICITLY decides: "Grant Claude access to my data" + Set expiration + Choose permission type

Layer 2: Permission Grants

Before ANY access: Check permission_grant (valid? not expired? not revoked?) → ALLOWED or DENIED + Log access

Layer 3: Encrypted Storage

Raw data encrypted with user-held keys. Only references (data://sha256:...) leave this layer. User chooses location (local/AWS/Azure/GCP)

Content Addressing & Immutability

Every 121XML object gets an immutable address based on its content:

data://sha256:3a4f2b5c8e9d1f7a2b4c6e8f0a1b3c5d:definition

Key Benefits:

  • ✓ Immutable references that never change
  • ✓ Perfect caching (address = cache key)
  • ✓ Tamper detection (modified data = different address)
  • ✓ Distributed sharing without copying
  • ✓ Garbage collection via reference counting

Documentation & Resources

📋

Core Principles

Axioms, Rules, and Definitions

🏗️

Architecture

System design and components

🔐

Data Sovereignty

User control and encryption

🚀

Cross-Platform

Vendor portability explained

🌍

Ecosystem

Complete platform overview

⚙️

Agentic OS

AI operating system

Quick Start: Define Your First 121XML Object

<?xml version="1.0" encoding="UTF-8"?> <map profile="urn:121xml:my-first-object/1.0" version="1.0"> <str name="object_id">my_object_001</str> <str name="object_name">My First 121XML Object</str> <str name="description">A simple example</str> <map name="metadata"> <str name="created">2026-08-06T13:00:00Z</str> <str name="creator">Your Name</str> </map> <seq name="features" of="str"> <str>Vendor-neutral</str> <str>Self-describing</str> <str>Content-addressed</str> </seq> </map>

This simple structure combines all three axioms and four rules. The profile URI tells any receiver how to interpret this object. The content address (SHA256) is immutable and unique.

121XML Agentic Operating System

Build AI agents that work across any protocol, any schema, any platform.

Ask the Community

Feature Suggestions & Community Ideas

Feature Suggestion System

Help shape the future of 121XML. Vote on features, suggest improvements, and help prioritize development.

Community & Contribution

GitHub

Contribute to the 121XML standard, SDK, and implementation. Star the repository and join development.

View Repository

Documentation

Complete guides, API references, and implementation examples for building with 121XML.

Read Docs

Discussions

Join conversations about features, architecture decisions, and use cases.

Start Discussion