> 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/core-client/fleet-provider.md).

# Fleet provider reference

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

`fleet(config)` adapts the canonical client to Sedona Fleet production API v0. The base URL is:

```
https://fleet-api-production-fleet-api.up.railway.app
```

Pass the origin only; the adapter adds `/v0`.

## Implemented operations

Fleet implements:

* connection and capability inspection;
* line list and get;
* direct-chat create, list, and get;
* message send, list, edit, and unsend;
* reaction add and remove;
* typing start and stop;
* message-targeted read receipts;
* contact-card sharing;
* advisory address reachability;
* event list and replayable long-poll stream;
* webhook verification, parsing, and administrator subscription CRUD;
* authenticated raw requests.

Fleet does not expose generic group mutation, generic attachment upload, locations, polls, or a generic message-get route. Background wire dispatch is kept as an experimental Fleet extension and is not documented as a visible user feature.

## Fleet extensions

The provider declares typed wrappers for:

* process liveness;
* line profile status;
* current reaction state;
* experimental background dispatch;
* administrator line re-registration;
* administrator line cooldown;
* webhook delivery metadata.

Operational extensions can change production line state and are intentionally absent from the quickstart. Authorization to send does not imply authorization to run them.

## Wire and error behavior

All versioned API routes use bearer authentication. User keys are restricted to their line grants; administrator-only routes return authorization errors for ordinary users. Fleet maps relevant HTTP status, provider error code, retry guidance, and redacted raw payload into the SDK error model. Fleet does not provide a stable request ID.

Finite line and webhook lists return complete arrays. Event positions are durable sequence cursors. Resource identifiers are opaque and provider-bound; message mutation targets carry both chat and message scope.


---

# 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/core-client/fleet-provider.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.