> ## Documentation Index
> Fetch the complete documentation index at: https://ixoworld-mintlify-9a7944b6.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# IXO integrations

> Conceptual integration patterns for connecting external systems to IXO services.

<Tip>
  This page explains integration patterns at a system level. For exact SDK usage and API contracts, use the linked SDK and API reference pages.
</Tip>

## Integration surfaces

<CardGroup>
  <Card title="IXO MultiClient SDK" icon="plug">
    Unified application integration across protocol, data, and orchestration services.
  </Card>

  <Card title="IXO Matrix Client SDK" icon="database">
    Secure room-based data exchange and event communication.
  </Card>

  <Card title="Agentic Oracles ADK" icon="brain" href="/sdk-reference/agentic-oracles-adk">
    Verification and automation workflows driven by agent services (`@ixo/oracle-agent-sdk`).
  </Card>

  <Card title="IXO SignX SDK" icon="key">
    Signing and delegated authorization for user and service actions.
  </Card>
</CardGroup>

## Common integration patterns

<AccordionGroup>
  <Accordion title="Device and telemetry integration" icon="microchip">
    Connect external devices to domain workflows by capturing telemetry, validating it, and attaching verifiable evidence to claims.
  </Accordion>

  <Accordion title="Registry and system sync" icon="database">
    Synchronize trusted records from external registries into IXO domains with explicit mapping and provenance rules.
  </Accordion>

  <Accordion title="Data-sharing collaboration" icon="lock">
    Use encrypted room-based channels for partner collaboration, review, and governed access to shared records.
  </Accordion>

  <Accordion title="Payments and settlement flows" icon="money-bill">
    Trigger settlement logic from verified outcomes while preserving auditable state transitions.
  </Accordion>
</AccordionGroup>

## Design considerations

* Define source-of-truth boundaries before syncing data between systems.
* Treat identity and authorization as first-class integration concerns.
* Separate operational telemetry from evidence-grade records.
* Prefer idempotent event and claim-processing workflows.

## Go here next

<CardGroup>
  <Card title="Developer guides" icon="hand-pointer" href="/guides/dev/overview">
    Follow step-by-step implementation workflows.
  </Card>

  <Card title="SDK overview" icon="code" href="/sdk-reference/index">
    Choose the right SDK for your integration path.
  </Card>

  <Card title="API reference" icon="server" href="/api-reference/index">
    Use canonical API pages for exact request and response details.
  </Card>
</CardGroup>