But today, every interaction works differently. Email works one way. Payments another. Contracts another. APIs another. That was manageable when humans glued everything together. It becomes the bottleneck when agents need to operate across hundreds of relationships at machine speed.
Blue standardizes interactions. One structure. Every relationship. Any participant.
The problem
People use contracts, emails, PDFs, signatures, and handshakes. Services use APIs. Users use apps and websites. Money moves through separate financial rails. Each has a different structure, a different trust model, a different source of truth.
With agents
This fragmentation becomes the core bottleneck. Agents could transform coordination — but only if interactions share a common shape.
The solution: standardize interactions
Instead of treating emails, orders, agreements, payments, and workflows as fundamentally different things, Blue gives them one common structure — making them easier to build, easier to compose, easier to trust, and much easier for agents to understand.
To make that possible, interactions cannot all have different shapes.
Mental model
One shape for every interaction. Whether an order, a payment, a contract, or a negotiation — it's always the same structure: participants, rules, shared state, verifiable history.
Inside: participants — people, agents, services, banks, couriers, legal providers. Everyone has a clear identity others trust. They act according to explicit rules. The state changes when they act. Everything is recorded.
An order is a cube. A payment is a cube. A service workflow is a cube. A negotiation is a cube. Same shape. Different participants. Different rules.
Alice's world includes: her shop, an automation with her OpenClaw agent, an incoming order where she and her customer participate, a payment for that order with her, the customer, and the customer's bank, a delivery with a courier, a partnership with another business.
Blue does not force everything into one system. It gives every interaction the same shape.
Once interactions share the same structure, building real processes becomes fast. You don't invent a custom system for each case. You compose blocks: a shop, an order, a payment, a mandate, a delivery, a service agreement. Because they all follow the same pattern, they work together naturally. Not one giant platform — many small blocks that fit together.
Block
Block
Block
Block
Block
Block
How it works
A shop is born from a sentence. A bank secures a payment. A mandate is written in code. An agent acts inside the rules. Same world — built across chat, code, banking, and agent action.
Alice talks to Blink in MyOS and describes her hair-tools business in plain language. Blink turns the description into a real shop, ready to receive orders, partnerships, services, and payment flows.
She doesn't need to know what Blue is — she just describes what she wants.
Bob wants his agent OpenClaw to make a purchase on his behalf. He asks his bank for an authorization carrying a PayNote — the bank secures the funds, but money only moves if every condition is met.
A short Node.js snippet bootstraps the mandate. It's not a blank check — it's a narrow capability: find a Dyson HD07, stay inside the budget, and only buy through a payment that attaches the required PayNote.
The rules are made explicit before OpenClaw can act.
OpenClaw connects to MyOS, reads the mandate, and approaches multiple shops — including Alice's. It compares offers, proves it can pay, and stays inside the PayNote conditions throughout.
Each merchant conversation is its own order. Some end if terms don't fit. One completes — and only then does money move.
Same world. Built through chat, code, bank infrastructure, and agent action.
Why Blue is built for agents
Blue gives agents a structured world to act in: verified identity, permanent record, trusted services, structural control, and a shape that scales across all interactions.
01
Agents are not anonymous tool-runners. Every timeline provider attributes agents properly — whether it was a person or an agent, whose authority it used, how it entered the system.
02
To do anything, an agent must put an entry on a timeline. Actions are recorded. Attribution is clear. History is permanent and not negotiable later.
03
For legal review, financial operations, or shipping, agents should use trusted providers who participate in the document and stake their reputation.
04
Every step an agent takes is controlled by the document's rules. If the document doesn't allow it, the protocol makes it impossible. Participants can also intervene directly.
05
Once every interaction follows the same structure, agents can operate across all of them. They only need to understand: participants, rules, state, timelines.
The stack
Blue is the open language. MyOS makes it practical. PayNotes bring money into the same world without replacing existing rails.
Language layer
The open language for interaction blocks. The protocol layer. You're here.
Where it runs
Where Blue runs. Timelines, processing, payments, services, and Blink — which lets you create blocks in natural language.
Money layer
How money joins. A PayNote attaches to a transaction and governs what happens: secure the funds, complete the payment, cancel, or reverse. Existing rails participate in the same composable world.
Start here
Start with the tutorial, then go deeper into the language, trust model, and tooling.
Tutorial
The fastest way to feel how Blue works in practice.
Open tutorialConcepts
The model and trust story in one place — concepts, the mental model, and the playground.
Read conceptsSpecification
Reference the exact language and processing model.
Read specOpen source
Use the official open-source implementations and shared type ecosystem.
Closing
The internet gave everyone communication. AI gives everyone intelligence. Blue gives everyone one structure for interactions — so anything can work with anything, and trust is built into every piece.