The open codex for game item data.

LootVault is a self-hostable database for game items: stats, recipes, rarities, and lore, all exposed through one REST API that any wiki, build calculator, or companion app can call.

GET/api/items?rarity=legendary

No account needed to browse. Self-host on your own Convex deployment, MIT licensed.

~/lootvault.api
example
$ curl https://api/items/ak74-bp
{
  "id": "ak74-bp",
  "name": "AK-74 + Bullpup Kit",
  "rarity": "legendary",
  "category": "rifles",
  "stats": { "ergo": 48, "recoil": 162 }
}
200 OK
application/json

Already modeled for genres like

RPGsLooter ShootersMMOsSurvivalTCGsRoguelikes

Everything you need to ship an items API.

The schema, the endpoints, the search index, and the review queue are already built. You bring the items.

Try the search
Structured schema
Stats, requirements, recipes, rarities, and lore: every field a build, calculator, or wiki needs, defined per game.
REST API
Versioned endpoints with predictable JSON. Query by game, rarity, category, or tag.
Cross-game search
One search surface across every indexed game: fast, typo-tolerant, and faceted by rarity and category.
Self-hostable
Deploy on your own Convex backend. Your data, your infrastructure, your rules. MIT licensed.
Auth and API keys
Better-auth sessions plus scoped API keys for programmatic access.
Community submissions
Crowd-sourced data with a review queue, so the catalog stays accurate as games change.

Who runs their loot on LootVault.

Tool builders shipping calculators and planners.

Pull typed item data, with rarity and category, in a single request. Because the schema is validated on write, a build optimizer reads clean data instead of stitching together half a dozen wiki tables.

GET /api/items?category=helmets

Communities keeping one canonical catalog.

Contributors submit items through a review queue and reviewers approve them, so the wiki, the Discord bot, and the companion app all read the same source.

Studios that want an official item API.

Run it on your own Convex backend and own the data, the API keys, and the export, without building the infrastructure first.

Catalog your loot once, then serve it everywhere.