> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dzap.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Product Stack

> Core, Fuse, and AI — what each does and when to use it.

## At a glance

| Product       | One-liner                     | Pattern                    |
| ------------- | ----------------------------- | -------------------------- |
| **DZap Core** | Swap + bridge aggregator      | Quote → approve → execute  |
| **DZap Fuse** | Single-click intent execution | Sign once → solver settles |
| **DZap AI**   | Natural-language driver       | Talk → tools → action      |

## When to use which

<CardGroup cols={2}>
  <Card title="Building a swap UI" icon="arrows-rotate" href="/products/dzap-core/swap">
    Use **Core**. Direct quote + execution flow with full price control.
  </Card>

  <Card title="One-click cross-chain LP entry" icon="bolt" href="/products/dzap-fuse/bundle">
    Use **Fuse**. Bundles bridge + swap + deposit into one signature.
  </Card>

  <Card title="An agent that can trade" icon="robot" href="/ai/overview">
    Use **AI**. Tool surface + ZapBot + MCP for any agent runtime.
  </Card>

  <Card title="Cross-chain settlement" icon="bridge" href="/products/dzap-core/bridge">
    Use **Core**. Best-route bridging across the major providers.
  </Card>
</CardGroup>

## Shared building blocks

Every product reads from the same routing engine:

* **Routing** — DZap pathfinder evaluates DEX + bridge candidates and ranks by net output.
* **Approvals** — `getAllowance` + `approve` / `sign` covers ERC20, Permit2, EIP-2612, and AutoPermit modes.
* **Contracts** — one DZap router per chain (DZapDiamond). See [Smart Contract Addresses](/products/contracts).
* **Status** — `/v1/status` polls cross-chain settlement.

## Naming note

In code, Fuse features are named `Zap*` (e.g. `getZapQuote`, `signGaslessDzapUserIntent`). The product is **Fuse** publicly; the rename is gradual.