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

# Socket stack

> The product layers behind Socket's routing, execution, and settlement infrastructure.

Socket is built in layers. Teams can start with a hosted interface, integrate directly with APIs, or build around Socket's routing and intent infrastructure for more custom money-movement flows.

## Stack layers

<div className="socket-stack-diagram not-prose">
  <a className="socket-stack-layer socket-stack-layer-top" href="/integrate/socket-widget">
    <span className="socket-stack-icon">
      <Icon icon="puzzle-piece" />
    </span>

    <span className="socket-stack-copy">
      <span className="socket-stack-title">Socket Widget</span>
      <span className="socket-stack-description">A production-ready swap and deposit interface that apps can embed quickly, with routing, quotes, approvals, execution, and status handled behind the UI.</span>
    </span>
  </a>

  <a className="socket-stack-layer" href="/integrate/introduction">
    <span className="socket-stack-icon">
      <Icon icon="code" />
    </span>

    <span className="socket-stack-copy">
      <span className="socket-stack-title">Socket API</span>
      <span className="socket-stack-description">Direct endpoints for teams that want to quote, execute, and track routes inside their own product flows.</span>
    </span>
  </a>

  <div className="socket-stack-layer">
    <span className="socket-stack-icon">
      <Icon icon="route" />
    </span>

    <span className="socket-stack-copy">
      <span className="socket-stack-title">Socket routing engine</span>
      <span className="socket-stack-description">The decisioning layer that compares routes across 10,000+ assets and 50+ chains, balancing output, speed, reliability, approvals, gas, and provider availability.</span>
    </span>
  </div>

  <div className="socket-stack-layer socket-stack-layer-base">
    <span className="socket-stack-icon">
      <Icon icon="sparkles" />
    </span>

    <span className="socket-stack-copy">
      <span className="socket-stack-title">Socket intents</span>
      <span className="socket-stack-description">Outcome-based execution infrastructure where users specify the result they want and Socket coordinates the route, liquidity, and settlement path.</span>
    </span>
  </div>
</div>

## How the layers work together

The widget and API are the integration surfaces. The routing engine powers route discovery and execution. Socket intents sit underneath higher-level flows where the product needs outcome-based execution instead of managing every transaction step directly.

Together, these layers let teams choose how much of the stack they want Socket to handle, from a fully embedded UI to a custom API integration.

<CardGroup cols={2}>
  <Card title="Start with the API" icon="rocket" href="/integrate/introduction">
    Build custom routing and execution flows with Socket endpoints.
  </Card>

  <Card title="Embed the widget" icon="puzzle-piece" href="/integrate/socket-widget">
    Add Socket's hosted swap and deposit experience to your product.
  </Card>
</CardGroup>