iGaming Tools

iGaming Tools (i-gaming.tools) is an independent data provider that documents online casino slot games and the industry around them. Its own automated pipeline drives headless browsers against live provider demos to extract 45+ structured fields per slot — RTP and up to 30 variants, volatility, max win, reels, bet mechanic, full paytables with per-symbol payouts and hex colours, bonus rounds, and ~21 screenshots with WebP derivatives — alongside slot providers, game series, themes, features, licensing regulators, ingested industry news, iGaming job vacancies and a computed search-demand layer. Access is a token-authenticated, read-only REST API (OpenAPI 3.0.3, 29 GET operations, cursor pagination, ETag/304, ?updated_since incremental sync with tombstone reconcile) plus a free unauthenticated hosted MCP server exposing 17 read-only tools, and two llms.txt files. It is not a casino, operator or betting service.

iGaming Tools publishes 1 API on the APIs.io network: iGamingScraper REST API. Tagged areas include iGaming, Online Casino, Gambling, slot games, and slot metadata.

iGaming Tools’ developer surface includes documentation, API reference, getting-started guide, pricing, signup flow, and 14 more developer resources.

54.5/100 strong ▬ flat Agent 33/100 agent ready Full breakdown ↓
scored 2026-09-01 · rubric v0.17.2
2 APIs 2 MCP Servers
iGamingOnline CasinoGamblingslot gamesslot metadatagambling regulationIndustry NewsJobmarket demandAnalyticsREST APIOpenAPIMCP Serverllms-txtLLM Toolingslot RTPpaytable datasearch demandiGaming jobsagent-ready APIread-only API

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-01 · rubric v0.17.2
Composite quality — 54.5/100 · strong
Contract Quality 13.9 / 25
Developer Ergonomics 11.4 / 20
Access Clarity 15.3 / 20
Operational Transparency 4.1 / 13
Contract Governance 2.2 / 12
Discoverability 7.6 / 10
Agent readiness — 33/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 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
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Surface 0 / 5
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/igaming-tools: 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 2

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

iGamingScraper REST API

Token-authenticated REST API providing structured iGaming data: slot providers, slots, news articles, jobs, and regulatory entities. OpenAPI 3.0.3, cursor-paginated, ETag-friend...

iGaming Tools MCP Server

Free public hosted MCP server (Streamable HTTP, no API key, read-only, not metered) exposing the same iGaming dataset as 17 tools: provider search and profiles, slot search and ...

MCP Servers 2

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

iGaming Tools MCP Server

Probed manifest with deployment block (mode remote, endpoint https://mcp.i-gaming.tools/mcp, auth none, verified probed) and all 17 tools.

MCP SERVER

iGaming Tools MCP Server

LIVE remote MCP endpoint, 17 read-only tools, no credential. Requires the MCP initialize handshake for a session id — a bare tools/list returns 400, which reads as broken but is...

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Igaming Tools Rate Limits

3 limits

RATE LIMITS

Security Posture 2

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

Igaming Tools Authentication

apiKey · 1 scheme

SECURITY

Igaming Tools Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 4

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 3

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Source (apis.yml)

apis.yml Raw ↑
name: iGaming Tools
aid: igaming-tools
description: iGaming Tools (i-gaming.tools) is an independent data provider that documents online casino slot games and the
  industry around them. Its own automated pipeline drives headless browsers against live provider demos to extract 45+ structured
  fields per slot — RTP and up to 30 variants, volatility, max win, reels, bet mechanic, full paytables with per-symbol payouts
  and hex colours, bonus rounds, and ~21 screenshots with WebP derivatives — alongside slot providers, game series, themes,
  features, licensing regulators, ingested industry news, iGaming job vacancies and a computed search-demand layer. Access
  is a token-authenticated, read-only REST API (OpenAPI 3.0.3, 29 GET operations, cursor pagination, ETag/304, ?updated_since
  incremental sync with tombstone reconcile) plus a free unauthenticated hosted MCP server exposing 17 read-only tools, and
  two llms.txt files. It is not a casino, operator or betting service.
url: https://raw.githubusercontent.com/api-evangelist/igaming-tools/refs/heads/main/apis.yml
created: '2026-08-30'
modified: '2026-08-30'
specificationVersion: '0.21'
tags:
- iGaming
- Online Casino
- Gambling
- slot games
- slot metadata
- gambling regulation
- Industry News
- Job
- market demand
- Analytics
- REST API
- OpenAPI
- MCP Server
- llms-txt
- LLM Tooling
- slot RTP
- paytable data
- search demand
- iGaming jobs
- agent-ready API
- read-only API
tags_raw:
- iGaming
- online casino
- gambling
- slot games
- slot metadata
- gambling regulation
- industry news
- jobs
- market demand
- analytics
- REST API
- OpenAPI
- MCP server
- llms.txt
- LLM tooling
- slot RTP
- paytable data
- search demand
- iGaming jobs
- agent-ready API
- read-only API
apis:
- name: iGamingScraper REST API
  description: 'Token-authenticated REST API providing structured iGaming data: slot providers, slots, news articles, jobs,
    and regulatory entities. OpenAPI 3.0.3, cursor-paginated, ETag-friendly, with incremental sync support.'
  humanURL: https://i-gaming.tools/docs/
  baseURL: https://i-gaming.tools/api/v1
  tags:
  - iGaming
  - Online Casino
  - Gambling
  - slot games
  - slot metadata
  - gambling regulation
  - Industry News
  - Job
  - market demand
  - Analytics
  - REST API
  - OpenAPI
  - MCP Server
  - llms-txt
  - LLM Tooling
  tags_raw:
  - iGaming
  - online casino
  - gambling
  - slot games
  - slot metadata
  - gambling regulation
  - industry news
  - jobs
  - market demand
  - analytics
  - REST API
  - OpenAPI
  - MCP server
  - llms.txt
  - LLM tooling
  properties:
  - type: OpenAPI
    url: openapi/igaming-tools-openapi.json
    description: Verbatim capture 2026-08-30 of the provider OpenAPI 3.0.3. 29 GET operations, 59 schemas, 9 reusable error
      responses, 6 reusable headers.
  - type: OpenAPI
    url: https://i-gaming.tools/docs/openapi.json
  - type: OpenAPI
    url: https://i-gaming.tools/api/schema/?format=json
    description: Byte-identical to /docs/openapi.json; served as application/vnd.oai.openapi+json. YAML at /api/schema/.
  - type: Overlay
    url: overlays/igaming-tools-openapi-overlay.yaml
  - type: Authentication
    url: authentication/igaming-tools-authentication.yml
  - type: ErrorCatalog
    url: errors/igaming-tools-problem-types.yml
  - type: DataModel
    url: data-model/igaming-tools-data-model.yml
  - type: Conventions
    url: conventions/igaming-tools-conventions.yml
  - type: RateLimits
    url: rate-limits/igaming-tools-rate-limits.yml
  - type: Documentation
    url: https://i-gaming.tools/docs/
  - type: APIReference
    url: https://i-gaming.tools/api/docs/
    description: Interactive Swagger explorer.
  - type: GettingStarted
    url: https://i-gaming.tools/docs/quickstart/
  - type: LLMsTxt
    url: https://i-gaming.tools/llms.txt
  - type: LLMsTxt
    url: https://i-gaming.tools/docs/llms.txt
- name: iGaming Tools MCP Server
  description: 'Free public hosted MCP server (Streamable HTTP, no API key, read-only, not metered) exposing the same iGaming
    dataset as 17 tools: provider search and profiles, slot search and full spec sheets, series, themes, features, per-slot
    and per-provider search demand, market demand cuts, regulators, industry news, jobs and news sources. Live handshake on
    2026-08-30 returned protocolVersion 2025-06-18 and serverInfo iGaming Tools MCP 3.4.7. Documented for Claude, ChatGPT,
    Cursor, VS Code/Copilot, Claude Code, Gemini CLI, Codex CLI, Windsurf and Zed.'
  humanURL: https://i-gaming.tools/docs/
  baseURL: https://mcp.i-gaming.tools/mcp
  tags:
  - iGaming
  - Online Casino
  - Gambling
  - slot games
  - slot metadata
  - gambling regulation
  - Industry News
  - Job
  - market demand
  - Analytics
  - REST API
  - OpenAPI
  - MCP Server
  - llms-txt
  - LLM Tooling
  tags_raw:
  - iGaming
  - online casino
  - gambling
  - slot games
  - slot metadata
  - gambling regulation
  - industry news
  - jobs
  - market demand
  - analytics
  - REST API
  - OpenAPI
  - MCP server
  - llms.txt
  - LLM tooling
  properties:
  - type: MCPServer
    url: mcp/igaming-tools-mcp.yml
    description: Probed manifest with deployment block (mode remote, endpoint https://mcp.i-gaming.tools/mcp, auth none, verified
      probed) and all 17 tools.
  - type: MCPServer
    url: https://mcp.i-gaming.tools/mcp
    description: LIVE remote MCP endpoint, 17 read-only tools, no credential. Requires the MCP initialize handshake for a
      session id — a bare tools/list returns 400, which reads as broken but is correct protocol. Verified 2026-08-30.
  - type: ToolCrosswalk
    url: mcp/igaming-tools-tool-crosswalk.yml
  - type: Documentation
    url: https://i-gaming.tools/docs/mcp/
maintainers:
- FN: iGaming Tools
  url: https://i-gaming.tools
  email: support@i-gaming.tools
generated:
  by: apis.io/add
  model: claude-opus-4-8
  confidence: 96
  at: '2026-08-30T06:25:46.277Z'
common:
- type: DeveloperPortal
  url: https://i-gaming.tools/docs/
- type: Documentation
  url: https://i-gaming.tools/docs/
- type: APIReference
  url: https://i-gaming.tools/api/docs/
- type: GettingStarted
  url: https://i-gaming.tools/docs/quickstart/
- type: Pricing
  url: https://i-gaming.tools/pricing/
- type: SignUp
  url: https://i-gaming.tools/register/
- type: Login
  url: https://i-gaming.tools/login/
- type: TermsOfService
  url: https://i-gaming.tools/terms/
- type: PrivacyPolicy
  url: https://i-gaming.tools/privacy/
- type: LLMsTxt
  url: llms/igaming-tools-llms.txt
  description: Verbatim capture of https://i-gaming.tools/llms.txt (text/markdown, 200).
- type: LLMsTxt
  url: llms/igaming-tools-docs-llms.txt
  description: Verbatim capture of https://i-gaming.tools/docs/llms.txt (text/markdown, 200).
- type: Plans
  url: plans/igaming-tools-plans-pricing.yml
- type: RateLimits
  url: rate-limits/igaming-tools-rate-limits.yml
- type: Conventions
  url: conventions/igaming-tools-conventions.yml
- type: Lifecycle
  url: lifecycle/igaming-tools-lifecycle.yml
- type: Conformance
  url: conformance/igaming-tools-conformance.yml
- type: DomainSecurity
  url: security/igaming-tools-domain-security.yml
- type: Packages
  url: packages/igaming-tools-packages.yml
  description: Honest zero — no first-party SDK, CLI or client package exists in any registry. No SDKs pointer is emitted.
- type: AgentSkill
  url: skills/_index.yml
  description: 'Four generated Agent Skills grounded in verified operationIds: incremental sync, slot research, demand analysis,
    provider brief.'
image: https://i-gaming.tools/media/site_assets/apple_touch_icon/2026/06/5-9b0bb4a0cfe6f9a7.png
x-enrichment:
  date: '2026-08-30'
  status: enriched
  artifacts_added: 23
  pass: local-v1

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/igaming-tools"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/igaming-tools/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/igaming-tools/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

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