IXO Protocol records the parts of real-world work that coordination depends on: who is involved, what exists in the model, what is claimed, what evidence supports assertions, how important state changes over time, and which actions are valid under the rules. It is how you move from “messages and documents about a program” to inspectable, permissioned state that agents and partners can rely on—then extend with IXO Matrix, IXO Blocksync, and Agentic Oracles for full workflows.Documentation Index
Fetch the complete documentation index at: https://docs.ixo.world/llms.txt
Use this file to discover all available pages before exploring further.
Conceptual scope
Protocol primitives
Protocol primitives
IXO Protocol provides modules for identity-bound entities, claims workflows, and programmable coordination.
Network deployment
Network deployment
Impact Hub Network is the primary public deployment used by applications and services in the IXO ecosystem.
Cross-service role
Cross-service role
IXO Matrix, IXO Blocksync, and Agentic Oracles integrate with IXO Protocol to execute end-to-end workflows.
Why it matters
- Anchors identities and rights in verifiable records.
- Supports claims and attestations that drive downstream workflows.
- Provides the shared state foundation for tokenized and governed coordination.
Go here next
Developer guides
Follow task-oriented implementation guides.
API reference
Use canonical API pages for exact interface details.
IXO Blocksync
Understand the indexed query layer that sits above protocol state.