> For the complete documentation index, see [llms.txt](https://xircus-developer.gitbook.io/developer-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xircus-developer.gitbook.io/developer-hub/terminologies/graphee/for-ton-chain.md).

# for TON Chain

This API schema is designed specifically for TON Chain smart contracts and requests. This will not work to any non-TVM chain due to wallet address and json-rpc method incompatibility.

We created this API to promote 

<table><thead><tr><th width="172">Schema Name</th><th width="411">Description</th><th>Used For</th></tr></thead><tbody><tr><td>Accounts</td><td>Contains account info and chain addresses</td><td>Studio, Designer</td></tr><tr><td>Auth</td><td>Authentication endpoint for verifying wallet address through message signing. Next implementation is with ton-proof</td><td>All</td></tr><tr><td>AppAccounts</td><td>Contains account info for apps, tagging accounts as creators, developers, designers or any category app owner wishes</td><td>App, Designer</td></tr><tr><td>Assets</td><td>Contains indexed contract data filtered as NFT, SBT and Tokens</td><td>All</td></tr><tr><td>Apps</td><td>Contains deployed app configurations for Telegram and TON Web</td><td>All</td></tr><tr><td>Listings</td><td>Indexed sale contract for listing in the app marketplace sections</td><td>All</td></tr><tr><td>Forms</td><td>Contains schema for rendering forms and collected user replies</td><td>Studio</td></tr><tr><td>Leaderboards</td><td>Contains leaderboard mechanics and record participant scores from games and activities</td><td>App</td></tr><tr><td>Games</td><td>Contains micro game mechanics for tapper, education, html5 or simple interactive micro games, scores and computation are stored on leaderboards</td><td>App</td></tr><tr><td>Skins</td><td>Contains info about app templates, published by Xircus and by designer ecosystem using Mini App or Web App Designer. <br><br>Mini App - contains Telegram functions</td><td>Studio, Designer</td></tr><tr><td>Projects</td><td>Stores app template configuration for future purposes</td><td>Designer</td></tr><tr><td>Teams</td><td>Contains team information and member delegates to manage apps</td><td></td></tr><tr><td>Oracles</td><td>Contains oracle requests feeding data from api for queue request and batch execution</td><td>Registry</td></tr><tr><td>Subscriptions</td><td>Contains indexed subscription contracts</td><td>Registry</td></tr><tr><td>Exchanges</td><td>Contains indexed exchange contracts</td><td>Registry</td></tr><tr><td>Bots</td><td>Contains Telegram bot details to broadcast message, create bot replies and more</td><td>App</td></tr><tr><td>Queue</td><td></td><td></td></tr></tbody></table>


---

# 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:

```
GET https://xircus-developer.gitbook.io/developer-hub/terminologies/graphee/for-ton-chain.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.