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

# TON: Choosing v2 or v3

> Compare TON API v2 vs v3: real-time node requests vs indexed data. Choose v2 for speed and freshness, v3 for stable processed data with Chainstack.

<Info>
  ### TON pricing is the same for full, archive, v2, v3

  There's no difference between a full node an archive node in data availability or pricing. All data is always available and all node requests are consumed as 1 request unit.
</Info>

Check out our [TON API reference](/reference/getting-started-ton), which has both v2 and v3 methods.

The question is—which one should you choose for your project?

As a reminder:

* TON API v2 endpoints serve real-time requests. TON API v2 requests serve off a node.
* TON API v3 endpoints serve indexed requests. TON API v3 requests serve off an indexer.

## Which one to choose

If speed and real-time freshness are crucial (for example, you need near-instant visibility of new transactions), go with v2.

If you need highly stable, processed, and precise data, and can tolerate a slight indexing delay—v3 is likely the better option.

Tip: If the data provided by v2 is sufficient for your use case, it should remain your best choice for simplicity and quick data access.

## Key differences detailed

### Indexing latency (data freshness)

**v2**: Delivers raw data more quickly, effectively providing the "freshest" data at any given moment. Feels more "native" because it uses the [ADNL protocol](https://docs.ton.org/v3/documentation/network/protocols/adnl/overview) directly, which often lets it react faster to blockchain changes. This native ADNL access is available on Chainstack dedicated nodes, enabling direct low-level network communication.

**v3**: Performs additional data processing and indexing. As a result, it may have a slight lag compared to raw data sources. Offers well-structured and cleaned data, which can be advantageous for complex queries. If ultra-fresh data is a priority (for instance, if you need to see changes at near real-time), use v2 tends to have the edge.

### Request latency

Our TON RPC node network is global and we strive to always have the shortest travel time for your requests based on our highly tuned infrastructure.

See also [Available clouds, regions, and locations](/docs/nodes-clouds-regions-and-locations).

<CardGroup>
  <Card title="Ake">
    <img src="https://mintcdn.com/chainstack/UN3rP7zhB69idvnC/images/docs/profile_images/1719912994363326464/8_Bi4fdM_400x400.jpg?fit=max&auto=format&n=UN3rP7zhB69idvnC&q=85&s=792a24ab1b4682406fa589c0ecd88e5d" alt="Ake" style={{width: '80px', height: '80px', borderRadius: '50%', objectFit: 'cover', display: 'block', margin: '0 auto'}} noZoom width="400" height="400" data-path="images/docs/profile_images/1719912994363326464/8_Bi4fdM_400x400.jpg" />

    <Icon icon="code" iconType="solid" /> Director of Developer Experience @ Chainstack
    <br /><Icon icon="screwdriver-wrench" iconType="solid" /> Talk to me all things Web3
    <br />20 years in technology | 8+ years in Web3 full time years experience

    <div style={{display: "flex", justifyContent: "center", gap: "12px"}}>
      <a href="https://github.com/akegaviar/" style={{textDecoration: "none", borderBottom: "none"}}>
        <Icon icon="github" iconType="brands" />
      </a>

      <a href="https://twitter.com/akegaviar" style={{textDecoration: "none", borderBottom: "none"}}>
        <Icon icon="twitter" iconType="brands" />
      </a>

      <a href="https://www.linkedin.com/in/ake/" style={{textDecoration: "none", borderBottom: "none"}}>
        <Icon icon="linkedin" iconType="brands" />
      </a>
    </div>
  </Card>
</CardGroup>