> For the complete documentation index, see [llms.txt](https://inoswap.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inoswap.gitbook.io/guide/partners-and-api-integration/integration-flow-and-architecture.md).

# Integration Flow & Architecture

Technical overview of the InoSwap integration flow and multichain routing architecture.

## How Integration Works

Integrating [InoSwap](https://inoswap.org/) follows a structured five-step process.

{% stepper %}
{% step %}
First, **your system sends a quote request** including the token pair, amount, and chain context. 
{% endstep %}

{% step %}
I evaluate available liquidity and **return optimised routing options** along with estimated output and pricing details.
{% endstep %}

{% step %}
Next, I generate execution-ready calldata. This transaction payload can be submitted directly through your platform. 
{% endstep %}

{% step %}
Then, I generate execution-ready calldata. <mark style="color:$danger;">This transaction payload can be submitted directly through your platform.</mark>&#x20;
{% endstep %}

{% step %}
The **user signs the transaction** in their wallet, and once confirmed on-chain, your interface can display the final execution status and output.
{% endstep %}
{% endstepper %}

This structure allows you to maintain full control over user interaction while leveraging my routing intelligence behind the scenes.

***

## Multichain Architecture

[InoSwap](https://inoswap.org/) is built with multichain scalability at its core.

<mark style="color:$danger;">The routing engine operates with unified aggregation logic while remaining chain-aware. This enables routing optimisation across different blockchain environments as integrations expand.</mark>

<mark style="color:$danger;">The architecture is modular. Additional DEX integrations on Cronos can be added without altering the core logic, and future blockchain deployments can extend routing capability without requiring a redesign of the system.</mark>

This means partners integrate once and scale progressively.

{% hint style="info" %}
Partner integration request form [**here**](https://docs.google.com/forms/d/e/1FAIpQLSeOIIL5KhCnDc7Di2OoRL1OgTy7CsocgEr5Byf1aFGbyEp3JA/viewform)
{% endhint %}