Developer platform
The game data and competition engine Ascend runs on, opening as APIs one product at a time. One account and one console for keys, usage and billing. The Knowledge API is live today.
One account. A key per product. Each API priced on its own.
Knowledge API
Every number in the game, with its source.
kb_free_••••••••Freecurl -s -H "x-api-key: $KB_API_KEY" \
https://kb.play-ascend.com/api/valorant/entity/clove-ruse.json{
"name": "Ruse",
"resolved": [
{
"field": "ability.creds",
"value": 150,
"unit": "credits",
"tier": "official_ingame",
"source": "https://wiki.playvalorant.com/en-us/Ruse",
"evidence": "150"
},
"… 13 more"
]
}Competitions API
Tournaments, brackets and results from the platform. Not open yet; keys for it will live here.
Every product sits in one rail, live or not. A product that isn't open says so.
Each API has its own keys, in the same account, sent in the same header.
The live API answers with the value and where it was read from.
The APIs
The same data and engine Ascend runs on, opened one product at a time. Each has its own keys and its own plans, all in one console.
Damage, cooldowns, costs and patch changes as JSON, with the source of every value.
{ "value": 150, "unit": "credits",
"source": "https://wiki.playvalorant.com/en-us/Ruse" }14 games · 22,476 entities · 148,944 facts
The engine behind Ascend's matchmaking and tournaments, for your bot, site or event.
Illustration, not real data
The pro scene behind Ascend's Pros pages: players, teams and matches.
Illustration, not real data
The match and rank data behind Ascend's tracker and Companion.
Illustration, not real data
The platform
Learn the console, the key and the header once. A new API is a new key in the same place.
Keys, usage and billing for every API in one place, at console.play-ascend.com. Each API is priced and billed on its own.
Sign in with Google, GitHub or email. The same developer account holds every product you use.
Each API has its own keys, created in the console and sent in the x-api-key header. Never in the URL.
Each plan has a request limit per key. The console shows what each key has used against it.
The Knowledge API speaks MCP, so Claude, Cursor or any HTTP MCP client can call it with your key.
Data comes with where it was read from. A figure no source states is left out rather than filled in.
MCP endpoint
Knowledge APIhttps://kb.play-ascend.com/mcpSix tools: list games, search, read an entity or one fact, its patch history, and what a field means. Client setup
A value, with its receipt
Knowledge API{ "value": 150, "tier": "official_ingame",
"evidence": "150", "patchFrom": null }Source, the text it was parsed from, how well it's attested and the patch it held in.
Pricing
You pay for the APIs you use, each on its own plan, billed in the same console. The Knowledge API is the one with plans today.
| Feature | Free key Free One key per account. Enough to build a first integration and see the receipts; not enough to crawl. | Pro key $10 /month For a tool in production: room for an agent to answer all day, and the bulk files for a build step. |
|---|---|---|
| Requests every five minutes | 60 | 1,500 |
| Bulk files an hour, for a build step | 2 | |
| Every endpoint, and the MCP server | ||
| Source, evidence, tier and patch on every value | ||
| Games with non-commercial sources |
The free key covers every game, including the ones whose sources allow only non-commercial use; a Pro key is told to use the free key for those.
Setup
With Google, GitHub or email. One developer account holds the keys for every Ascend API.
A free key, shown once when it is made. When you need the room, Pro is billed from the same console.
Put it in x-api-key on every request. Keys never go in the URL.
Questions
Four, at different stages. The Knowledge API is live. The Competitions API is coming soon. An esports data API and a player data API are planned and not available yet.
The Knowledge API: damage, cooldowns, costs and patch changes as JSON, every value with the source it was read from. Create a key in the console, then send it with your first request.
One account and one console, with a key per product. Each API has its own keys, created in the same console and sent in the x-api-key header.
Each API has its own plans. For the Knowledge API, a free key gets 60 requests every five minutes, and Pro is $10 a month for 1,500 requests every five minutes and the bulk files. The other APIs will have their pricing when they launch.
Yes. Point any HTTP MCP client (Claude Code, Cursor, VS Code and others) at https://kb.play-ascend.com/mcp with your key in the x-api-key header.
For most games, yes. Overwatch 2, PUBG and Destiny 2 come from sources that allow only non-commercial use, so they are served to free keys only; a Pro key asking for one is told to use the free key.
There are no dates yet. Tell us what you would build through the contact form and we'll write when the one you need opens.
No. The Knowledge API reads public sources and cites them. No publisher runs, reviews or sponsors it.
Start with the Knowledge API today. Waiting on competitions, esports or player data? Tell us what you would build and we'll write when it opens.