> For the complete documentation index, see [llms.txt](https://docs.ston.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ston.fi/developer-section/omniston/environments.md).

# Environments and endpoints

Omniston sandbox and production environments and their service endpoints.

## Environments

Omniston has two environments: sandbox and production.

### Sandbox

Use sandbox for early integration with new protocol versions and additional assets. Updates become available here before production, giving you time to prepare your integration for upcoming releases.

### Production

Use production for live integrations serving your users. Protocol updates and support for additional assets are rolled out here after they become available in sandbox.

## Endpoints

### Sandbox

| Service       | Transport               | Endpoint                        |
| ------------- | ----------------------- | ------------------------------- |
| Trading / RFQ | JSON-RPC over WebSocket | `wss://omni-ws-sandbox.ston.fi` |
| Trading / RFQ | gRPC with TLS           | `omni-grpc-sandbox.ston.fi:443` |

### Production

| Service       | Transport               | Endpoint                                |
| ------------- | ----------------------- | --------------------------------------- |
| Trading / RFQ | JSON-RPC over WebSocket | `wss://omni-ws.ston.fi`                 |
| Trading / RFQ | gRPC with TLS           | `omni-grpc.ston.fi:443`                 |
| History       | JSON-RPC over WebSocket | `wss://omni-history-ws.ston.fi`         |
| History       | JSON-RPC over HTTP      | `https://omni-history.ston.fi/json-rpc` |
| History       | gRPC with TLS           | `omni-history-grpc.ston.fi:443`         |

All gRPC endpoints listed above use TLS. Configure your gRPC client with the `host:port` target and TLS enabled.

See [Direct API integration](https://docs.ston.fi/developer-section/omniston/swap.md) for the trading methods and [History API](https://docs.ston.fi/developer-section/omniston/history.md) for finalized-order queries.

## Example applications

Try Omniston through the deployed example applications. Each application connects to its corresponding environment:

* Sandbox: [omniston-sandbox.ston.fi](https://omniston-sandbox.ston.fi)
* Production: [omniston.ston.fi](https://omniston.ston.fi)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ston.fi/developer-section/omniston/environments.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
