> For the complete documentation index, see [llms.txt](https://docs.sedona.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sedona.fun/readme.md).

# Overview

[← Back to dashboard](https://www.sedona.fun/dashboard/api-keys)

The Sedona SDK provides a typed, provider-based interface for iMessage automation. Applications import the provider-free `openblue` client and the Sedona Fleet provider, `@sedonadotfun/openblue-fleet`.

The SDK is intentionally conservative:

* a successful send response means accepted, not delivered;
* mutations are never retried automatically;
* an ambiguous mutation becomes `outcome_unknown`;
* transport stays unknown until the provider reports an observation;
* unsupported features fail with typed errors instead of being silently ignored.

The initial `0.1.0` release is ESM-only and requires Node.js 20.10 or newer. Install the core and Fleet provider from npm:

```sh
npm install openblue @sedonadotfun/openblue-fleet
```

Start with the [read-only production quickstart](/getting-started.md), then read [Safety semantics](/safety-semantics.md) before enabling any mutation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.sedona.fun/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.