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

# SDKs & Widget

> Three ways to integrate beyond raw HTTP, from a typed client to a drop-in widget.

Three packages sit on top of the same [Integrator API](/api-reference/overview) covered
elsewhere in these docs. None of them own wallet connection or transaction building. RAVN's
`/api/v1` already returns exactly what to sign or send; these packages just save you the
boilerplate around it.

<Note>
  Not yet published to npm. These packages shipped alongside a wider audit and haven't been wired
  up with real workspace or publish tooling yet. The APIs below are final. Watch this page or
  [@ravnexchange](https://x.com/ravnexchange) for the npm release.
</Note>

## Pick one

| Package                      | For                                                                  | Handles                                                                                                                                                |
| ---------------------------- | -------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [`@ravn/sdk`](/sdks/core)    | Backend services, or any wallet calling the API directly             | A typed `RavnClient` for quote, execute, submit-signature, and status. Zero dependencies.                                                              |
| [`@ravn/react`](/sdks/react) | Dapps building their own swap UI                                     | Hooks on top of `@ravn/sdk` that manage quote-expiry and status-polling state. You still bring your own wallet.                                        |
| Widget                       | Anyone who wants a drop-in swap UI with zero wallet-connect friction | A hosted `<iframe>` plus [`@ravn/widget-connector`](/sdks/widget), the host-side bridge that lets the widget use your page's already-connected wallet. |

All three are convenience layers over the exact same [`/quote`](/api-reference/quote),
[`/execute`](/api-reference/execute), [`/submit-signature`](/api-reference/submit-signature), and
[`/status`](/api-reference/status) calls documented in the [Quickstart](/quickstart): same fields,
same fees, same DTOs. Nothing below unlocks pricing or routing you can't already get by calling
the REST API yourself.