> For the complete documentation index, see [llms.txt](https://developer.barchart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.barchart.com/platform-features.md).

# Platform Features

Explore Openfeed's market data protocol, delivery services, SDKs, and connectivity options.

Openfeed consolidates global exchange data through a single integration. It delivers low-latency market data in its native exchange format.

This reduces exchange-connection complexity. It also lowers development and maintenance costs.

### Core components

Openfeed includes three core components:

1. [**Openfeed Protocol**](/architecture/core-protocols.md) — protobuf-based message definitions for efficient, cross-platform market data delivery.
2. [**Streaming API**](/openfeed-api/streaming.md) — continuous real-time and delayed updates for large symbol universes. SDKs support [Java](/repos-sdks/java-sdk.md), [.NET](/repos-sdks/.net-sdk.md), [Python](/repos-sdks/python-sdk.md), and [Go](/repos-sdks/go-golang-sdk.md).
3. [**Snapshot REST API**](/openfeed-api/snapshot-rest.md) — query-response access to JSON market data for targeted requests.

### Market data coverage

Openfeed connects your applications to exchanges worldwide. Choose Level 1 data or Level 2 market depth based on your entitlement and application requirements.

Review [available exchanges](/getting-started/available-exchanges.md) and supported [subscription types](/getting-started/subscription-types.md) before you integrate.

### Flexible delivery

Connect over the internet or use dedicated connectivity options. These options support low-latency data delivery for business-critical applications.

See the [connectivity overview](/networking-options/connectivity-overview.md), [dedicated connections](/networking-options/dedicated-connections.md), and [AWS PrivateLink](/networking-options/aws-privatelink.md).

### Build and maintain less

Use documented feed handlers and SDKs to shorten initial development. The same resources reduce ongoing integration work as your product evolves.

Start with the [Quickstart](/getting-started/quickstart.md) and apply the [Best Practices](/getting-started/best-practices.md) guidance to optimize performance and stability.


---

# 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://developer.barchart.com/platform-features.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.