Build with AIXBT
Choose a supported REST or MCP path and complete a first request
Choose the smallest supported integration that fits your client. The current builder surfaces are Legacy v2 REST, the authenticated general-purpose AIXBT MCP, and a focused public Topics MCP.
Choose a path
| Surface | Use it for | Access |
|---|---|---|
| Legacy v2 REST | Direct HTTP integrations against the current v2 contract | GET /v2/topics is public; most data routes require an API key |
| AIXBT MCP | Authenticated agents and clients that need the general-purpose tool catalog | OAuth 2.1 or an account-backed API key is required |
| Topics MCP | A narrow integration for the current Topics leaderboard and published Frontier Reports | get_trending_topics is public; full reports require eligible account access |
Create API keys and manage authorized apps in
Integrations. Send REST API keys in the
x-api-key header. Send programmatic full-MCP keys as Bearer tokens, or use the
discovered OAuth flow in an interactive client. Do not put credentials in
source control.
Make a first request
Legacy v2 REST
This public request returns the current Topics leaderboard and needs no API key:
curl --fail-with-body "https://api.aixbt.tech/v2/topics"Use the generated Legacy v2 reference to check authentication, parameters, and response schemas before calling another endpoint.
Topics MCP
Add the public Topics server to a Streamable HTTP MCP client:
{
"mcpServers": {
"aixbt-topics": {
"type": "streamable-http",
"url": "https://api.aixbt.tech/mcp/topics"
}
}
}After connecting, call the get_trending_topics tool with no arguments. The
tool name is not another URL. This endpoint is a focused Topics integration,
not a second general-purpose AIXBT platform. For the authenticated tool catalog,
follow the AIXBT MCP setup.