LootRush website screenshot

LootRush

LootRush is a gaming and crypto platform (backed by Paradigm) that publishes a Partner API for marketplace integrations: initiating and tracking on-chain cryptocurrency withdrawals, querying a user's transaction and activity history, and OAuth-style consented access to user data via a Connect API. LootRush also runs a published, read-only Model Context Protocol (MCP) server at mcp.lootrush.com that lets an AI assistant read the key-holder's own balance, cards, card transactions, and account history — every call scoped to the API key's user. Authentication is per-user bearer tokens (Withdraw, History, MCP) and integration API keys (Connect).

LootRush publishes 4 APIs on the APIs.io network, including Connect API, History API, MCP API, and 1 more. Tagged areas include Company, Gaming, Crypto, Cryptocurrency, and Payments.

LootRush’s developer surface includes documentation, API reference, getting-started guide, support, authentication, and 13 more developer resources.

36.3/100 thin ▬ flat Agent 72/100 agent native Full breakdown ↓
scored 2026-07-27 · rubric v0.5
AccessSelf serve
4 APIs 1 MCP Servers
CompanyGamingCryptoCryptocurrencyPaymentsWithdrawalsMCPAPI

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 36.3/100 · thin
Contract Quality 14.8 / 25
Developer Ergonomics 11.3 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 72/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/lootrush: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

LootRush Connect API

The Connect API from LootRush — 1 operation(s) for connect.

LootRush History API

The History API from LootRush — 1 operation(s) for history.

LootRush MCP API

The MCP API from LootRush — 1 operation(s) for mcp.

LootRush Withdrawals API

The Withdrawals API from LootRush — 2 operation(s) for withdrawals.

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

lootrush-mcp.yml

MCP SERVER

Rate Limits 1

Documented rate limits and quota policies.

Lootrush Rate Limits

0 limits

RATE LIMITS

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Lootrush Authentication

apiKey/http · 2 schemes

SECURITY

Lootrush Domain Security

TLSv1.3 · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Lootrush Agentic Access

5 operations · 2 acting

5 operations · 2 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

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

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: lootrush
name: LootRush
description: 'LootRush is a gaming and crypto platform (backed by Paradigm) that publishes a Partner API for marketplace integrations:
  initiating and tracking on-chain cryptocurrency withdrawals, querying a user''s transaction and activity history, and OAuth-style
  consented access to user data via a Connect API. LootRush also runs a published, read-only Model Context Protocol (MCP)
  server at mcp.lootrush.com that lets an AI assistant read the key-holder''s own balance, cards, card transactions, and account
  history — every call scoped to the API key''s user. Authentication is per-user bearer tokens (Withdraw, History, MCP) and
  integration API keys (Connect).'
url: https://raw.githubusercontent.com/api-evangelist/lootrush/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- paradigm
x-tier: provider
x-tier-reason: enriched-from-live-api
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Gaming
- Crypto
- Cryptocurrency
- Payments
- Withdrawals
- MCP
- API
image: https://www.lootrush.com/favicon.ico
apis:
- aid: lootrush:lootrush-connect-api
  name: LootRush Connect API
  description: The Connect API from LootRush — 1 operation(s) for connect.
  humanURL: https://docs.lootrush.com
  baseURL: https://third-party.lootrush.com
  tags:
  - Connect
  properties:
  - type: OpenAPI
    url: openapi/lootrush-connect-api-openapi.yml
  - type: Documentation
    url: https://docs.lootrush.com
  - type: APIReference
    url: https://docs.lootrush.com/api-reference/openapi.json
- aid: lootrush:lootrush-history-api
  name: LootRush History API
  description: The History API from LootRush — 1 operation(s) for history.
  humanURL: https://docs.lootrush.com
  baseURL: https://third-party.lootrush.com
  tags:
  - History
  properties:
  - type: OpenAPI
    url: openapi/lootrush-history-api-openapi.yml
  - type: Documentation
    url: https://docs.lootrush.com
  - type: APIReference
    url: https://docs.lootrush.com/api-reference/openapi.json
- aid: lootrush:lootrush-mcp-api
  name: LootRush MCP API
  description: The MCP API from LootRush — 1 operation(s) for mcp.
  humanURL: https://docs.lootrush.com
  baseURL: https://third-party.lootrush.com
  tags:
  - MCP
  properties:
  - type: OpenAPI
    url: openapi/lootrush-mcp-api-openapi.yml
  - type: Documentation
    url: https://docs.lootrush.com
  - type: APIReference
    url: https://docs.lootrush.com/api-reference/openapi.json
- aid: lootrush:lootrush-withdrawals-api
  name: LootRush Withdrawals API
  description: The Withdrawals API from LootRush — 2 operation(s) for withdrawals.
  humanURL: https://docs.lootrush.com
  baseURL: https://third-party.lootrush.com
  tags:
  - Withdrawals
  properties:
  - type: OpenAPI
    url: openapi/lootrush-withdrawals-api-openapi.yml
  - type: Documentation
    url: https://docs.lootrush.com
  - type: APIReference
    url: https://docs.lootrush.com/api-reference/openapi.json
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.lootrush.com
- type: Documentation
  url: https://docs.lootrush.com
- type: APIReference
  url: https://docs.lootrush.com/api-reference/openapi.json
- type: GettingStarted
  url: https://docs.lootrush.com/index.md
- type: Support
  url: mailto:support@lootrush.com
- type: LLMsTxt
  url: llms/lootrush-llms.txt
- type: MCPServer
  url: mcp/lootrush-mcp.yml
- type: Authentication
  url: authentication/lootrush-authentication.yml
- type: AgenticAccess
  url: agentic-access/lootrush-agentic-access.yml
- type: Conventions
  url: conventions/lootrush-conventions.yml
- type: ErrorCatalog
  url: errors/lootrush-problem-types.yml
- type: RateLimits
  url: rate-limits/lootrush-rate-limits.yml
- type: Lifecycle
  url: lifecycle/lootrush-lifecycle.yml
- type: Conformance
  url: conformance/lootrush-conformance.yml
- type: DataModel
  url: data-model/lootrush-data-model.yml
- type: DomainSecurity
  url: security/lootrush-domain-security.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Overlay
  url: overlays/lootrush-openapi-overlay.yaml
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 13
  pass: local-v1