docs.chainbase.com

# Chainbase Docs ## Docs - [Json Web Token(JWT)](https://docs.chainbase.com/api-reference/jtw.md) - [Overview](https://docs.chainbase.com/api-reference/overview.md) - [Data Cloud SQL Query (Classic)](https://docs.chainbase.com/api-reference/sql-api/data-cloud-sql-query.md) - [Execute Queries (Alpha)](https://docs.chainbase.com/api-reference/sql-api/execute-queries.md): Limit of 100,000 results - [Get Query Results (Alpha)](https://docs.chainbase.com/api-reference/sql-api/get-query-results.md) - [Get Query Status (Alpha)](https://docs.chainbase.com/api-reference/sql-api/get-query-status.md) - [API Status Code](https://docs.chainbase.com/api-reference/status-code.md) - [get posts for a topic](https://docs.chainbase.com/api-reference/tops-api/tool/get-posts-for-a-topic.md): Retrieves posts associated with a topic. Output should be a list of posts sorted by time or relevance with text, author, timestamp, permalink, and engagement metrics (if available). - [get topic detail](https://docs.chainbase.com/api-reference/tops-api/tool/get-topic-detail.md): Fetches structured details for one topic so an LLM can quickly understand what it is about. Input is topic_id (from trending or search). Output should include a topic description/definition, core keywords, representative post summaries (post ids/links/authors/timestamps), and metadata. - [list trending topics](https://docs.chainbase.com/api-reference/tops-api/tool/list-trending-topics.md): Returns a ranked list of currently trending crypto narratives/topics. Use it for ideation and trend scanning. language selects the locale/language (affects tokenization and trend definition). Output should include topic_id, title/keywords, and a score/rank summary. - [search narrative candidate topics by keyword](https://docs.chainbase.com/api-reference/tops-api/tool/search-narrative-candidate-topics-by-keyword.md): Reverse-searches topic candidates from a human keyword to map a fuzzy narrative into the platform's topic taxonomy. Input i