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 API contracts indexed on the APIs.io network, including Connect API, History API, MCP API, and 1 more. Tagged areas include Company, Gaming, Cryptocurrency, Payments, and Withdrawals.

The LootRush catalog on APIs.io includes 1 Spectral governance ruleset.

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

35.6/100 thin ▬ flat Agent 41/100 agent ready Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
1 published contract 1 MCP Servers 2 Agent Skills
CompanyGamingCryptocurrencyPaymentsWithdrawalsMCP

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for LootRush It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/lootrush/"><img src="https://apis.io/badge/lootrush/card.svg" alt="LootRush on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
  • Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
  • Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
  • Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks
  • Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too
5 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/lootrush/apis.yml: open an issue on github.com/api-evangelist/lootrush to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

MarketPositionDepthRegistered MCP serverDeclares compatibility
Browser Extension Stores (company-published Firefox add-ons; Chrome Web Store unreadable) standard 34.5 (thin) - -

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (verified)
measured — observed by APIs.io (published)

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.

Open Collections 4

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

MCP Servers 1

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

LootRush MCP Server

Streamable HTTP (JSON-RPC 2.0), stateless — one request, one response. POST only.

MCP SERVER

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Rate Limits 1

Documented rate limits and quota policies.

Lootrush Rate Limits

2 limits

RATE LIMITS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

LootRush API Rules

60 rules · 58 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Lootrush Openapi Overlay

3 actions · update · lootrush-openapi-original.json

DERIVED

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
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: true
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - rate-limits
  - security
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-03
tags:
- Company
- Gaming
- Cryptocurrency
- Payments
- Withdrawals
- MCP
tags_raw:
- Company
- Gaming
- Crypto
- Cryptocurrency
- Payments
- Withdrawals
- MCP
- API
image: ''
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

LootRush API — frequently asked questions

Does LootRush have an API?

Yes. APIs.io lists 4 APIs from LootRush, including LootRush Connect API, LootRush History API and LootRush MCP API, and 1 more.

Is there an OpenAPI specification for the LootRush API?

Yes. APIs.io indexes 4 OpenAPI specifications for LootRush, each linked for download from this page.

How do I authenticate with the LootRush API?

LootRush uses bearer-token authentication (apiKey/http · 2 schemes). The details are profiled on APIs.io as Lootrush Authentication.

Does LootRush have an MCP server?

Yes. APIs.io lists 1 MCP server for LootRush: Streamable HTTP (JSON-RPC 2.0), stateless — one request, one response. POST only.

Is the LootRush API ready for AI agents?

LootRush has a Kin Score of 35.6 out of 100 (thin) and an Agent Readiness score of 41.4 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/lootrush"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/lootrush/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/lootrush/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.