Skip to main content
These examples follow the canonical patterns from the @ixo/impactxclient-sdk and @ixo/matrixclient-sdk READMEs. Use them as starting templates — exact field shapes are generated from the chain proto definitions. For the step-by-step explanation behind each pattern, read Developer workflows first.

Setup

Digital twin: create an entity

Source an entity room (IXO Matrix)

Each entity has an associated encrypted Matrix room — its data room. Source it with the room bot, which creates the room if needed and invites the caller.
The ucanToken carries the caller’s capability to act on the entity. The optional accessToken is the user’s Matrix client-server access token, used only for the local join — never sent to the bot server. See Matrix authentication.

Upload telemetry into the data room

Read or set room state via the State Bot

Use the State Bot to attach structured profile or settings data to an entity room.
Always read state before overwriting. The State Bot does not merge — it replaces the value at the path you set.

Claim flow: submit, evaluate, mint

End-to-end flow for a digital MRV outcome:
The off-chain oracle call is your application code — see Agentic Oracles ADK and Build agentic oracles.

Agentic Oracle integration

The off-chain oracle service is built with the Agentic Oracles ADK and Personal Agent ADK. The on-chain side uses @ixo/impactxclient-sdk to record MsgEvaluateClaim. Wire the two together with whatever HTTP, MCP, or messaging layer your service exposes. The IXO Oracles ecosystem is private. To request access, see Build agentic oracles.

Next steps

API reference

REST, RPC, GraphQL, and service APIs.

IXO MultiClient SDK

Module-level features on protocol.

IXO Matrix Client SDK

Matrix data rooms and bot clients.

GitHub

Source code and reference implementations.