Loot Rush Games
LootRush (Loot Rush Games) is a San Francisco company, backed by a16z, Paradigm and Y Combinator, that operates a crypto-native "global operating account" — wallets, cards, cryptocurrency withdrawals and transaction history for gamers and marketplaces. It began as a Steam-like platform for blockchain games with NFT rentals and has grown into a consumer crypto account and card product. For developers, LootRush publishes a Partner API (OpenAPI 3.1) exposing Withdraw, History and Connect (OAuth-style, consent-based user data) APIs, plus an official hosted, read-only Model Context Protocol (MCP) server that gives AI assistants scoped access to a user's own balances, cards, card transactions and account history.
Loot Rush Games publishes 4 APIs on the APIs.io network, including Connect API, History API, MCP API, and 1 more. Tagged areas include Company, Cryptocurrency, Blockchain, Gaming, and Fintech.
Loot Rush Games’ developer surface includes documentation, API reference, getting-started guide, authentication, support, and 13 more developer resources.
Kin Score
APIs 4
Individual APIs this provider publishes, each with its own machine-readable definition.
Loot Rush Games Connect API
The Connect API from Loot Rush Games — 1 operation(s) for connect.
Loot Rush Games History API
The History API from Loot Rush Games — 1 operation(s) for history.
Loot Rush Games MCP API
The MCP API from Loot Rush Games — 1 operation(s) for mcp.
Loot Rush Games Withdrawals API
The Withdrawals API from Loot Rush Games — 2 operation(s) for withdrawals.
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
loot-rush-games-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Company 1
The organization behind the API