# Swap Integration

Expose Anqa’s meta-routing engine inside your own application through one of three integration layers:

* **API** – A stateless REST interface that returns deterministic quotes, optimal route breakdowns, and pre-signed Aptos transactions ready for broadcast. Ideal for server-side or mobile back ends that require full control over execution logic.
* **Widget** – A modular React component that bundles quoting, routing, and transaction signing behind a configurable UI. Drop it into any web front-end to enable best-rate swaps with minimal engineering overhead.
* **Iframe** – A sandboxed, zero-code embed for dashboards, analytics sites, and legacy stacks. Provides the same pricing logic and execution guarantees while isolating all blockchain interactions in a secure container.

Each integration surfaces identical pricing algorithms, drawing from 10 + liquidity sources across AMMs, CLAMMs, CLOBs, LSD pools, and peer aggregators, and supports slippage controls, gas estimation, and custom route constraints. Consult the method-specific reference for authentication, rate-limit policies, response schemas, and implementation examples.

{% content-ref url="/pages/UY94MTMqIK6r7UHlUdnm" %}
[API](/developer-guide/swap-integration/api.md)
{% endcontent-ref %}

{% content-ref url="/pages/FEBYDOYWBgoLaGnPnwbO" %}
[Widget](/developer-guide/swap-integration/widget.md)
{% endcontent-ref %}

{% content-ref url="/pages/9APUZjCkVpbTL8Dj20j2" %}
[Iframe](/developer-guide/swap-integration/iframe.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://dev.anqa.ag/developer-guide/swap-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
