> 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/getting-started.md).

# Getting started

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

Begin with a read-only Fleet inspection. It reports readiness, line counts, aggregate line states, and one capability result; it does not print line IDs, handles, credentials, or raw API payloads.

## Requirements

* Node.js 20.10 or newer
* an ESM application
* TypeScript `moduleResolution` set to `node16`, `nodenext`, or `bundler`
* a named-user Fleet API key with access to at least one line

The normal developer key is revealed once in the form `fleet_sk_<64 lowercase hex>`. Store it in a secret manager and expose it to the process as `FLEET_API_KEY`. The SDK sends it as:

```http
Authorization: Bearer <FLEET_API_KEY>
```

Do not use or distribute the Fleet bootstrap administrator credential as a developer key.

## Install

Install the provider-independent core and Sedona Fleet provider:

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

`FLEET_BASE_URL` is the origin only. Do not append `/v0`; the provider adds versioned route paths.

## Read-only client

```ts
import { createClient } from "openblue";
import { fleet } from "@sedonadotfun/openblue-fleet";

const client = createClient(
  fleet({
    baseUrl: process.env.FLEET_BASE_URL!,
    apiKey: () => process.env.FLEET_API_KEY!,
  }),
  { timeoutMs: 30_000 },
);

try {
  const connection = await client.connection.get();
  const lines = await client.lines.list();
  console.log({ ready: connection.ready, lineCount: lines.items.length });
} finally {
  await client.close();
}
```

Process readiness does not prove that a particular line can send. Check the selected line immediately before a mutation.

Next, [configure the Fleet provider](/fleet-configuration.md) or review [Safety semantics](/safety-semantics.md).


---

# 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/getting-started.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.