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 12 API contracts indexed on the APIs.io network, including Demand API, Features API, Jobs API, and 9 more. Tagged areas include iGaming, Online Casino, Gambling, slot games, and slot metadata.
iGaming Tools’ developer surface includes engineering blog, documentation, API reference, getting-started guide, pricing, signup flow, and 17 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) 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 does not apply to this provider. The published contracts declare
no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's
denominator entirely — not scored zero. A reference or data API is not deficient for being unable to
upsert.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/igaming-tools/"><img src="https://apis.io/badge/igaming-tools/card.svg" alt="iGaming Tools 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):
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
Protected Resource Metadata+5 pts — a served /.well-known/oauth-protected-resource carrying `resource` (documented), and naming its authorization_servers (verified)
3 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
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.
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 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.
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 ...
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.
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
accessModel:
pricing: free
onboarding: self-serve
trial: false
try_now: true
public: false
label: Free · Self-serve signup
confidence: high
source:
- plans
- authentication
- rate-limits
- security
generated: '2026-09-03'
method: derived
created: '2026-08-30'
modified: '2026-10-06'
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: 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/
- aid: igaming-tools:igaming-tools-demand-api
name: iGaming Tools Demand API
description: The demand API from iGaming Tools — 1 operation(s) for demand.
humanURL: https://i-gaming.tools/docs/
baseURL: https://i-gaming.tools/api/v1
tags:
- Demand
tags_raw:
- demand
properties:
- type: OpenAPI
url: openapi/igaming-tools-demand-api-openapi.yml
- 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/
- 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
- aid: igaming-tools:igaming-tools-features-api
name: iGaming Tools Features API
description: The features API from iGaming Tools — 1 operation(s) for features.
humanURL: https://i-gaming.tools/docs/
baseURL: https://i-gaming.tools/api/v1
tags:
- Features
tags_raw:
- features
properties:
- type: OpenAPI
url: openapi/igaming-tools-features-api-openapi.yml
- 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/
- 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
- aid: igaming-tools:igaming-tools-jobs-api
name: iGaming Tools Jobs API
description: The jobs API from iGaming Tools — 3 operation(s) for jobs.
humanURL: https://i-gaming.tools/docs/
baseURL: https://i-gaming.tools/api/v1
tags:
- Job
tags_raw:
- jobs
properties:
- type: OpenAPI
url: openapi/igaming-tools-jobs-api-openapi.yml
- 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/
- 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
- aid: igaming-tools:igaming-tools-news-api
name: iGaming Tools News API
description: The news API from iGaming Tools — 3 operation(s) for news.
humanURL: https://i-gaming.tools/docs/
baseURL: https://i-gaming.tools/api/v1
tags:
- News
tags_raw:
- news
properties:
- type: OpenAPI
url: openapi/igaming-tools-news-api-openapi.yml
- 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/
- 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
- aid: igaming-tools:igaming-tools-providers-api
name: iGaming Tools Providers API
description: The providers API from iGaming Tools — 8 operation(s) for providers.
humanURL: https://i-gaming.tools/docs/
baseURL: https://i-gaming.tools/api/v1
tags:
- Providers
tags_raw:
- providers
properties:
- type: OpenAPI
url: openapi/igaming-tools-providers-api-openapi.yml
- 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/
- 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
- aid: igaming-tools:igaming-tools-regulators-api
name: iGaming Tools Regulators API
description: The regulators API from iGaming Tools — 3 operation(s) for regulators.
humanURL: https://i-gaming.tools/docs/
baseURL: https://i-gaming.tools/api/v1
tags:
- regulators
properties:
- type: OpenAPI
url: openapi/igaming-tools-regulators-api-openapi.yml
- 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/
- 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
- aid: igaming-tools:igaming-tools-series-api
name: iGaming Tools Series API
description: The series API from iGaming Tools — 2 operation(s) for series.
humanURL: https://i-gaming.tools/docs/
baseURL: https://i-gaming.tools/api/v1
tags:
- Series
tags_raw:
- series
properties:
- type: OpenAPI
url: openapi/igaming-tools-series-api-openapi.yml
- 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/
- 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
- aid: igaming-tools:igaming-tools-slots-api
name: iGaming Tools Slots API
description: The slots API from iGaming Tools — 4 operation(s) for slots.
humanURL: https://i-gaming.tools/docs/
baseURL: https://i-gaming.tools/api/v1
tags:
- Slots
tags_raw:
- slots
properties:
- type: OpenAPI
url: openapi/igaming-tools-slots-api-openapi.yml
- 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/
- 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
- aid: igaming-tools:igaming-tools-sources-api
name: iGaming Tools Sources API
description: The sources API from iGaming Tools — 2 operation(s) for sources.
humanURL: https://i-gaming.tools/docs/
baseURL: https://i-gaming.tools/api/v1
tags:
- Sources
tags_raw:
- sources
properties:
- type: OpenAPI
url: openapi/igaming-tools-sources-api-openapi.yml
- 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/
- 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
- aid: igaming-tools:igaming-tools-stats-api
name: iGaming Tools Stats API
description: The stats API from iGaming Tools — 1 operation(s) for stats.
humanURL: https://i-gaming.tools/docs/
baseURL: https://i-gaming.tools/api/v1
tags:
- Stats
tags_raw:
- stats
properties:
- type: OpenAPI
url: openapi/igaming-tools-stats-api-openapi.yml
- 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/
- 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
- aid: igaming-tools:igaming-tools-themes-api
name: iGaming Tools Themes API
description: The themes API from iGaming Tools — 1 operation(s) for themes.
humanURL: https://i-gaming.tools/docs/
baseURL: https://i-gaming.tools/api/v1
tags:
- Themes
tags_raw:
- themes
properties:
- type: OpenAPI
url: openapi/igaming-tools-themes-api-openapi.yml
- 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/
- 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
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: CapabilityMap
url: capabilities/igaming-tools-capability-edges.yml
name: iGaming Tools Business Capability Map
- url: https://i-gaming.tools/news/
type: Blog
- type: Overlay
url: overlays/igaming-tools-openapi-overlay.yaml
- type: Website
url: https://i-gaming.tools/
- 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-09-05'
status: enriched
artifacts_added: 0
pass: local-v3
iGaming Tools API — frequently asked questions
Does iGaming Tools have an API?
Yes. APIs.io lists 12 APIs from iGaming Tools, including iGaming Tools MCP Server, iGaming Tools Demand API and iGaming Tools Features API, and 9 more.
Is there an OpenAPI specification for the iGaming Tools API?
Yes. APIs.io indexes 11 OpenAPI specifications for iGaming Tools, each linked for download from this page.
How do I authenticate with the iGaming Tools API?
iGaming Tools uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Igaming Tools Authentication.
How much does the iGaming Tools API cost?
APIs.io lists 3 pricing plans for iGaming Tools, with each plan's price, limits and inclusions under Pricing Plans on this page.
Does iGaming Tools have an MCP server?
Yes. APIs.io lists 1 MCP server for iGaming Tools: Probed manifest with deployment block (mode remote, endpoint https://mcp.i-gaming.tools/mcp, auth none, verified probed) and all 17 tools.
Is the iGaming Tools API ready for AI agents?
iGaming Tools has a Kin Score of 54.3 out of 100 (strong) and an Agent Readiness score of 43.3 (agent-native), scored by API Evangelist on 2026-11-01.
Discovery needs no key. Ratings and market analysis are Pro.
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.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: