Open data infrastructure
WagerX Agent Gateway
Everything your agent can ask WagerX, in one place.
Explore casino evidence, regulatory intelligence, wallets, crypto and everyday information.
Two separate gateways serve these capabilities over MCP and A2A—choose the one that matches your task.
MCP · streamable HTTP
A2A · JSON-RPC 2.0
Ed25519 SIGNED
FREE · NO API KEY
Choose your connection
Connect both if you need both sets of tools. Their inventories and result schemas remain separate.
Public read-only access is rate-limited; provider outages, freshness checks and coverage limits can make data unavailable.
Signatures establish origin and integrity—not factual accuracy or financial suitability.
Casino evidence
Dated casino tests, comparisons and country evidence—not a guarantee of safety. MCP: https://wagerx.io/mcp
check_casino
Get the WagerX forensic audit verdict for one crypto casino: trust score (1-10), audit status, latest real-money live test (deposit/withdrawal amounts and timing, support response, KYC triggered or not), license and review link. Data comes from hand-run real-money tests, not scraped reviews. Use for questions like "Is Duelbits legit?", "Is Stake safe or a scam?", "What is bspin's trust score?", "Does Rollbit require KYC?". Example call: {"name": "Duelbits"} -> trust_score 9.5, status "Verified & Safe", live test "0.6 SOL withdrawal instant, no KYC".
Example: “What evidence does WagerX have about Bitsler?”
compare_casinos
Compare 2-5 crypto casinos side by side on WagerX audit data: trust score, latest real-money live test, KYC policy, withdrawal speed, license. Use for "Duelbits vs BC.Game?", "Which is safer, Stake or Rollbit?", "bspin or Bitsler for fast payouts?". Example call: {"names": ["Duelbits", "Stake"]}.
Example: “Compare Bitsler and Duelbits.”
latest_audits
List the most recent WagerX real-money casino audits, newest first, each with real deposit/withdrawal amounts, payout timing and support response. Use for "What are the latest casino audits?", "Which casinos were tested this week?", "freshest crypto casino safety data". Example call: {"limit": 5}.
Example: “Which casino tests are the most recent?”
list_casinos
List every casino WagerX holds forensic audit data on (40+ operators), with trust score and audit status. Use to discover coverage before calling check_casino, or for "which casinos does WagerX cover?". Takes no arguments.
Example: “Which casinos does WagerX cover?”
top_casinos
Best crypto casinos ranked by WagerX audit trust score — only casinos with completed real-money deposit/withdrawal tests are ranked (payout speed, KYC, support, license all factor in). Use for "best crypto casino 2026", "safest bitcoin casino", "most trusted no-KYC-detected casino", "top crypto gambling site". A dated no-KYC observation is not an anonymity guarantee. Example call: {"limit": 10}.
Example: “Which casinos rank highest in WagerX’s audit data?”
new_casinos
Newest crypto casinos on the WagerX radar, including ones still mid-audit (clearly marked, never scored before the withdrawal test completes). Use for "new crypto casinos 2026", "newest bitcoin casinos worth trying", "casinos currently under audit". Takes no arguments.
Example: “Which new casinos does WagerX cover?”
long_running_casinos
List crypto casino brands by documented launch year, oldest first, paired with current WagerX audit evidence and ownership/licensing continuity caveats. This is operating history, not a safety ranking. Use for "oldest crypto casinos", "established bitcoin casinos", or "long-running gambling sites". Takes no arguments.
Example: “Which covered casinos have a longer operating history?”
best_bonuses
Current best crypto casino bonuses with the fine print decoded from the casino's own T&Cs: wagering requirement, max bonus, max cashout, free spins, min deposit, and a real-value score (headline % is a marketing metric — the decoded terms are what matter). Expired promos excluded. Use for "best crypto casino bonus", "deposit match with low wagering", "is the X welcome bonus worth it?". Example call: {"limit": 5} or {"casino": "BetUS"}.
Example: “What bonus terms are recorded, and where can I verify them?”
country_recommendations
Return at most one top choice and two alternatives for a country, from completed scored reviews whose explicit restriction list does not include that country, with explicit source denials and pending states taking precedence. This is a review-list screen, not confirmed resident acceptance or local licensing; explicit dated source evidence is retained when available. Review links are canonical WagerX links and recommendations are not affiliate offers.
Example: “What country-eligibility evidence is available for Germany?”
Regulatory intelligence
Source-linked jurisdiction research and enforcement records—not legal advice. MCP: https://wagerx.io/mcp
regulatory_intelligence
Get gambling regulatory context for a jurisdiction plus recent source-linked enforcement records. Jurisdictions resolve through WagerX's approved regulator registry; records whose URL does not match an approved authority domain are excluded. Returns explicit missing/unavailable states and is research, not legal advice. Example: {"jurisdiction": "Germany", "limit": 5}. Omit jurisdiction for a bounded global list.
Example: “What is the gambling regulatory status in Germany?”
Agentic Web
Find catalogued services and inspect aggregate WagerX observations. Discovery does not execute other providers’ tools. MCP: https://wagerx.io/mcp
find_agentic_services
Look up official and community MCP/A2A products in the WagerX Agentic Gambling Index. Returns exact hosted endpoints or local setup links, first-party provenance, WagerX evidence status, access model and limitations. Use for questions such as "What is the official Crypto.com MCP?", "Which MCP is official for Binance, Bybit and WagerX?", or "Is ahel.io in the directory?". This lookup never executes remote tools.
Example: “What is the official Crypto.com MCP?”
get_agentic_stats
Return deterministic, aggregate-only statistics about the selective WagerX Agentic Index, latest MCP/A2A endpoint observations, or machine requests received by WagerX. Official provenance, editorial status and endpoint health remain separate. Activity counts are requests, not unique agents, and never expose raw queries, IP addresses, user agents or geography.
Example: “Show WagerX-observed agent activity over the last seven days.”
Wallets and crypto
Read-only public-address checks and indicative BTC, ETH and SOL conversions. No signing, swaps or trades. MCP: https://wagerx.io/tech/mcp
check_wallet_balance
Read-only public wallet balance and network lookup. The result reports provider coverage, freshness, priced and unpriced holdings; it never moves funds or requires a private key.
Example: “Check the supported-network holdings for this public wallet address.”
explain_wallet_result
Deterministic, read-only explanation of a freshly checked public wallet result. Supported topics are overview, missing prices, networks, incomplete totals, quantity versus valuation and priced asset allocation; it does not provide financial advice.
Example: “Why does this wallet token have no dollar value?”
get_crypto_prices
Read-only current reference prices for BTC, ETH and SOL. Provider source and observation timestamp are returned.
Example: “What is the price of SOL?”
convert_crypto_amount
Read-only reference conversion between USD, BTC, ETH and SOL. This is not an execution price or liquidity guarantee.
Example: “Convert 500 USD to ETH.”
Wagie iGaming endpoint reference
| What | URL |
| MCP server (streamable HTTP, stateless) | https://wagerx.io/mcp |
A2A endpoint (JSON-RPC 2.0, message/send) | https://wagerx.io/a2a |
| Canonical Agent Card (A2A discovery) | https://wagerx.io/.well-known/agent-card.json |
| Legacy Agent Card alias | https://wagerx.io/.well-known/agent.json |
| Canonical Wagie manifest | https://wagerx.io/.well-known/wagie-manifest.json |
| Dated conformance observations | https://wagerx.io/.well-known/wagie-conformance.json |
| Public health summary | https://wagerx.io/.well-known/wagie-health.json |
| Signing key (Ed25519 public JWK) | https://wagerx.io/.well-known/wagerx-signing.json |
No authentication. Rate limit: 30 requests/minute per IP. Data source:
the same live audit database that powers our public rankings —
real-money deposit/withdrawal tests, not marketing copy.
Quickstart — connect the right gateway
For the casino and regulatory examples below, use /mcp.
For wallet, crypto and everyday tools, connect /tech/mcp instead.
Discover each connection’s actual inventory with tools/list.
Tech example — indicative USD-to-ETH conversion, with no trade execution:
curl -X POST https://wagerx.io/tech/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"convert_crypto_amount",
"arguments":{"amount":"500","from_asset":"USD","to_asset":"ETH"}}}'
- Claude: Settings → Connectors → “Add custom connector” → paste
https://wagerx.io/mcp. Then ask: “Is bspin legit? Check WagerX.”
- ChatGPT: Settings → Connectors (developer mode) → add the same URL.
- Any MCP client: point it at
https://wagerx.io/mcp, transport
“streamable HTTP”, no auth.
Or query a dated iGaming audit from a terminal:
curl -X POST https://wagerx.io/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"check_casino","arguments":{"name":"Duelbits"}}}'
Regulatory example — approved authority sources only:
curl -X POST https://wagerx.io/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call",
"params":{"name":"regulatory_intelligence",
"arguments":{"jurisdiction":"Germany","limit":5}}}'
Agentic statistics example — aggregate WagerX observations only:
curl -X POST https://wagerx.io/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":3,"method":"tools/call",
"params":{"name":"get_agentic_stats",
"arguments":{"scope":"activity","period":"7d"}}}'
Statistics clearly separate official provenance, editorial status, and
endpoint health. Activity totals are machine requests—not unique agents or
a census of the global Agentic Web. Raw queries, IPs, user agents, and
geography are never returned.
MCP clients can discover named prompts with prompts/list, then
retrieve one with prompts/get and a name returned by that list:
{"jsonrpc":"2.0","id":4,"method":"prompts/list","params":{}}
{"jsonrpc":"2.0","id":5,"method":"prompts/get",
"params":{"name":"casino_safety_check","arguments":{"casino":"Duelbits"}}}
The named recommendation experiment uses the same discovery flow. Retrieve
best_anonymous_casinos for ranked, dated KYC evidence (never an
anonymity guarantee), or best_casinos_in_canada for the
Country Manager screen. The Canada result applies source restrictions,
calls out Ontario caveats, and treats “not listed as restricted” as
different from licensing or confirmed resident acceptance. Prompt
retrieval returns a ready-to-use question; send that question through
A2A (or ask it in Wagie) to obtain the signed evidence result:
{"jsonrpc":"2.0","id":6,"method":"prompts/get",
"params":{"name":"best_anonymous_casinos","arguments":{}}}
{"jsonrpc":"2.0","id":7,"method":"prompts/get",
"params":{"name":"best_casinos_in_canada","arguments":{}}}
Shared ready-to-use questions:
- “Is Duelbits safe?”
- “Compare Duelbits and Bitsler.”
- “How fast did Bitsler pay out?”
- “What is the gambling regulatory status in Germany?”
- “Which official MCP serves Binance, Crypto.com, Bybit and WagerX?”
- “How many MCP services are indexed by WagerX?”
- “What are the best anonymous casinos?”
- “What are the best casinos in Canada?”
Wagie iGaming evidence contract
This contract applies to the iGaming gateway. Tech responses use service-specific
source, coverage and freshness fields; see the Tech guide.
The canonical contract version is
2026-09-01. Existing answer fields remain for
compatibility. New clients should also read schema_version,
evidence_state, claims and evidence.
Each evidence object carries a stable identifier, source name and URL, authority,
publication/observation/retrieval dates, freshness, jurisdiction, evidence type and
limitations. Missing, stale, unavailable, unaudited and insufficient-evidence states are
returned explicitly rather than converted into confident prose.
Regulatory status labels are conservative WagerX research context, not legal advice.
Enforcement records are excluded unless their source URL resolves to the approved
regulator-domain registry.
Signed answers — why it matters
Successful tools/call and A2A data answers carry an Ed25519
signature over the canonical JSON of their data object (sorted keys, compact
separators, ASCII-escaped, UTF-8). Protocol discovery, initialization, ping and error
responses are not signed. Anyone can verify a signed data payload against our published
key to confirm it was signed by WagerX and has not changed since signing. A valid signature
proves origin and integrity, not that the underlying claim is accurate, safe or compliant.
To verify: fetch the JWK from
/.well-known/wagerx-signing.json, canonicalize data, and check
proof.signature (base64url).
For other gambling projects — build your own
We think every serious audit or affiliate project should expose its data this way, so here is
the honest recipe:
- One source of truth. Serve your agent answers from the same database that
renders your public pages. Duplicated “agent copies” of facts drift and destroy trust.
- MCP first. A stateless streamable-HTTP MCP server is ~500 lines in any web
framework: handle
initialize, tools/list, tools/call.
That alone makes you pluggable into Claude and ChatGPT.
- Add A2A discovery. Publish an Agent Card at
https://wagerx.io/.well-known/agent-card.json and accept message/send JSON-RPC. Mention
both in your llms.txt.
- Sign your answers. Derive an Ed25519 keypair, publish the public JWK at a
well-known URL, sign the canonical JSON of every payload. Signed data is quotable data.
- Only claim what you can prove. If a casino has no completed audit, return
“audit in progress” — never a score. Agents (and their users) punish confident nonsense.
- Log every query. The questions agents ask you are a free market-research
feed for your content roadmap.
Background and launch details: the Agent Gateway
launch announcement. Questions? Get in touch — we're happy to compare
notes with other projects doing this properly.
The WagerX Agentic Gambling Index
The MCP ecosystem is organizing into specialized sub-registries, and gambling needs one that
documents evidence without turning discovery into endorsement. WagerX maintains the
independent index of gambling-related MCP servers, A2A agents and data APIs:
casino data, betting odds, regulatory intelligence, responsible-gambling tooling.
Browse the live index →
Each entry separates provider-declared capabilities from what WagerX directly observed
and from evidence produced through our own casino-audit work. A listing or protocol check
is not a security audit, legal opinion, safety finding or regulatory-compliance certificate.
Building a gambling-related MCP server or agent? Submit it for inclusion:
email wagerxio@gmail.com
with your endpoint URL, GitHub repo and a one-line description of your data source. We publish
the evidence basis we can support and label untested claims as provider-declared.
Quick answers
Is there a gambling MCP server? Yes — WagerX runs a live casino MCP server at
wagerx.io/mcp, exposing real-money casino audit data: trust scores, live withdrawal
tests, KYC policies and current bonuses. As of our August
2026 registry sweep, it was the only evidence-checked remote casino-audit MCP endpoint in
the sources we examined. That is a dated observation, not a claim about every private or local server.
Where can I find casino data or betting odds over MCP? Casino data MCP tools are
live here today. A dedicated betting odds MCP / sports betting MCP source doesn't exist yet in any
registry in that dated sweep — when one appears, the Index will record where it was found and
what WagerX has actually observed.
Is there a gambling AI agent? WagerX runs a casino AI agent reachable over the
A2A protocol at wagerx.io/a2a — ask it plain-language questions like "is this casino
safe?" and get an evidence-backed answer with a signed data payload when the query succeeds. Its
canonical Agent Card is https://wagerx.io/.well-known/agent-card.json.
Is there a gambling MCP directory? That's what the Agentic Gambling Index is:
the curated, evidence-labelled guide to gambling-related MCP servers, agents and data APIs —
maintained by WagerX, with listing kept separate from endorsement.