> For the complete documentation index, see [llms.txt](https://docs.chainlife.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chainlife.xyz/chainlife-tech/backend/public-api.md). # Public API An API is required to calculate the traits (from all on-chain data), render images as the tokens mature, and generate the html for live-views of the tokens. Additionally, because the tokens together interact in the Chainlife world, levels of all tokens must be tracked. The API was coded by Drake and West Dev to Matto's specifications. It listens for events emitted from the smart contract and provides various endpoints for the project: * tokenURI: JSON data that marketplaces use to retrieve token data * tokens-level: an array of token objects with the specific information to calculate the Chainlife World view * generator: html and scripts to generate a playable Chainlife token * level: html and scripts to generate a playable Chainlfie level * esoterra: html and scripts to generate the experimental Chainlife Esoterra art --- # 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, and the optional `goal` query parameter: ``` GET https://docs.chainlife.xyz/chainlife-tech/backend/public-api.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.