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

# Sauce SDK

> Programmable routing with live onchain state reads and atomic runtime execution. The Sauce SDK is @eco-incorp/sauce, which compiles SauceScript for the Sauce EVM and Solana runtimes, resolves protocol contracts and tokens, and builds the calls and Eco intents that execute your program.

<Note>
  Sauce v1 is **closed access**. [Contact Eco](mailto:partners@eco.com) to integrate.
</Note>

**Sauce** is Eco's runtime for the EVM and Solana. The **Sauce SDK** is how you access it: write transaction logic in SauceScript, a TypeScript subset, compile it to bytecode, and execute it atomically against live state in one transaction, on its own or as the destination of an [Eco intent](/concepts/intents). Use it to build [Programmable Transactions](/programmable-transactions/overview). For transfers and predefined destination calls, start with the [Routes API](/platform/routes-api).

## Packages

| Package | Version | What it is |
| - | - | - |
| `@eco-incorp/sauce` | 0.99.4 | The SDK. Route syntax and intent builders (`Base(body, options).reward(...)`), token and protocol registries, `token`, `swap` and `deposit` builders, release addresses, the Solana Kitchen client, settlement verification, and the compiler as a dependency. Node 24 or later. |
| `@eco-incorp/sauce-compiler` | 2.3.0 | The SauceScript compiler as WebAssembly, with Node and browser builds. Installed with the SDK; also available separately for Node and browser compilation. |

This documentation uses SDK 0.99.4 and compiler 2.3.0. On a `0.x` SDK version a breaking change is a minor bump, so pin exactly. The SDK bundles its own Markdown manual and checked examples under `docs/`, readable on [unpkg](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/README.md) or in `node_modules` after installation.

## Start building

Use [Getting started with Sauce](/programmable-transactions/sauce/getting-started) to install the pinned SDK, compile a program, prepare a Pot and read the execution fee. The guide covers EVM intent execution, direct EVM execution and the Solana Kitchen client.

For API details, use the [SDK reference](/sdk-reference/sauce/overview). For complete program examples, use the [Sauce cookbook](/cookbook/sauce/small-programs).

## Next steps

<CardGroup cols={2}>
  <Card title="Getting started" icon="play" href="/programmable-transactions/sauce/getting-started">
    Install, build an intent, prepare the Pot and fee, fund, compile standalone, Solana.
  </Card>

  <Card title="Programs as intents" icon="route" href="/programmable-transactions/sauce/programs-as-intents">
    Intent options, token and protocol globals, builders, nested intents, submission and inspection.
  </Card>

  <Card title="SauceScript reference" icon="code" href="/programmable-transactions/sauce/saucescript">
    The TypeScript subset: program structure, types, control flow, contract calls, builtins.
  </Card>

  <Card title="Architecture and deployments" icon="sitemap" href="/programmable-transactions/sauce/architecture-and-deployments">
    Compiler, engines, Kitchen, Pot, Router, fees, and the release addresses per chain.
  </Card>

  <Card title="SDK reference" icon="book" href="/sdk-reference/sauce/overview">
    SDK namespaces and compiler options, based on the published type declarations.
  </Card>

  <Card title="Cookbook" icon="book-open" href="/cookbook/overview">
    Complete programs shipped in the packages: best-pool swap, order split, settle, CCTP split.
  </Card>
</CardGroup>