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

# SDKs

> Current Memorose SDK availability and server-side retrieval configuration.

# SDKs

Memorose provides thin official SDKs for the current `/v1` runtime.

## Available SDKs

| Language             | Package                               | Notes                              |
| -------------------- | ------------------------------------- | ---------------------------------- |
| Python               | `memorose`                            | Stream-scoped events and retrieval |
| Node.js / TypeScript | `memorose-client`                     | Typed client for `/v1` routes      |
| Go                   | `github.com/memorose/memorose-sdk/go` | Context-aware HTTP client          |
| Java                 | `dev.memorose.sdk:memorose-client`    | Java model classes and client      |

The SDKs mirror the documented REST API and send `x-api-key` when an API key is configured.

## Reranking and arbitration

Reranker mode is configured on the server, not in SDK constructors. To use internal model-based arbitrator mode, start the server with:

```bash theme={null}
MEMOROSE__RERANKER__TYPE=arbitrator
MEMOROSE__RERANKER__MODEL=gemini-3.1-flash-lite-preview
MEMOROSE__RERANKER__MAX_CANDIDATES=32
```

The per-request `enable_arbitration` field controls retrieval-time memory arbitration behavior exposed by the API. It does not select the server reranker implementation or model.

## Direct HTTP fallback

If an SDK does not expose a newly added route yet, use the REST API documented in this site directly. The SDKs are intentionally thin wrappers over the same HTTP surface.