Image: WagerX’s Agentic Gambling Index, captured on 4 October 2026. The directory counts are not the results of this research batch.
Research date: 4 October 2026
What happens when we move beyond discovering an agent interface and ask it for something useful?
For this first research batch, WagerX made small, read-only requests to four independently operated services: LoyaltyVIP, iGregulator, SpinHire and iGaming Tools. We explored public casino information, licence evidence, compliance jobs and a regulator profile.
Each service returned information in at least one request. The encouraging finding is practical: these interfaces already let a research client retrieve useful, structured iGaming information without a private integration or an account.
This is not a leaderboard. It is a dated record of what we asked, what came back and what we could check.
How we approached the exchanges
We used an agent-assisted WagerX research client, identifying requests as WagerX or Wagie / WagerX. Three services were queried through MCP. LoyaltyVIP was queried through its documented natural-language /ask interface, not MCP or A2A.
We retained request details, responses, timestamps and supporting source material. No credentials, player records, applications, bets, payments or other write actions were involved.
These were research queries—not production Wagie chat-routing tests, autonomous peer conversations or partnerships. We have not established that the providers’ teams noticed the requests, and the providers have not reviewed this report.
LoyaltyVIP: public casino discovery
We asked LoyaltyVIP for Bellagio’s street address and rewards-program name. The full question returned no results, but a shorter “Bellagio” query returned two public casino-directory entries.
That gave us a useful starting point for finding the property. It also showed why downstream agents should distinguish a successful search from a complete answer.
Neither entry supplied the requested street address or rewards-program name. Both carried hasRewardsProgram: false, while Bellagio’s official website explicitly features MGM Rewards. The flag may reflect missing coverage rather than a claim that no programme exists; the response did not clarify this.
Takeaway: public discovery worked with a short query. An agent using the response should verify missing or negative fields before presenting them as facts.
iGregulator: licence evidence with explicit caveats
We asked iGregulator to check bet365.com. Its MCP response included operator names, licence references, source links and register freshness information.
Importantly, it did not present its UK information as freshly verified. It reported an active UKGC record for Hillside (UK Gaming) ENC based on an October 2 read, explicitly warning that the snapshot exceeded its 24-hour freshness window.
Our attempt to retrieve the cited UKGC download received HTTP 403, so we could not independently confirm the current UK status.
A separate Malta record led to an official MGA verification page whose summary said “Suspended” while its licence table said “Expired.” iGregulator preserved the summary wording and returned a normalized status of “unknown.” The conflicting official labels remain unresolved; they do not justify a worldwide claim about the brand’s licensing.
Our own safety filter initially blocked the lookup because it interpreted “register” as a possible action. After reviewing the tool, we retried with a narrowly scoped exception. That initial block was our testing limitation, not a provider failure.
Takeaway: source links and explicit freshness warnings made the response useful for further investigation, even where verification could not be completed.
SpinHire: relevant compliance opportunities
We asked SpinHire for three results matching “compliance” within its Compliance & AML category.
The response found relevant roles at Entain in Toronto and ComeOn Group in Malta. Both employer-hosted recruitment pages were accessible and displayed application links:
Three returned records represented two distinct source vacancies: the Entain role appeared twice under different URL forms.
The source pages also provided details worth carrying into an answer. Both described hybrid working, while SpinHire’s structured field said “office.” ComeOn explicitly required Dutch and English, while the structured languages field listed English only. Entain published a CAD 90–140k salary range; SpinHire returned no employer salary and supplied a separate euro-denominated estimate.
We did not verify the provider’s reported 114 matching records as distinct, currently available vacancies.
Takeaway: the search produced relevant leads with accessible sources. Deduplication and source-level checks help preserve the details that matter to candidates.
Job-search data attribution: SpinHire, whose response declared CC BY 4.0. Employer descriptions are summarized, not reproduced.
iGaming Tools: a usable regulator reference
We used iGaming Tools to find the Malta Gaming Authority and retrieve its profile.
The response supplied the regulator’s name, aliases, country, institutional origin date, statutory-authority label and official website.
The MGA’s own history corroborates the predecessor LGA’s operation from 2001 and subsequent renaming. Its regulatory-framework page identifies the Gaming Act as its empowering statute. We did not separately verify the response’s 2018 date.
The profile is a helpful reference, rather than a complete legal description. Its online-focused remit omits land-based activities, and “Malta (EU/EEA)” should not be read as EU-wide licensing permission. It provides the official host but no claim-specific citations or last-verified date.
Takeaway: a compact regulator profile can support discovery and orientation, with official sources supplying the fuller context.
What this first batch shows
Four different services contributed information to bounded research questions. The value was not simply that their endpoints answered: it was that returned records could lead us to identifiable properties, legal entities, employer postings and official regulatory sources.
The same exchanges also illustrate useful habits for anyone building an agent:
- Preserve freshness warnings and jurisdiction boundaries.
- Distinguish missing data from a negative fact.
- Deduplicate records before counting opportunities.
- Follow source links before repeating consequential claims.
This small, selected sample cannot establish uptime, overall accuracy, market leadership or comprehensive coverage. We have deliberately avoided performance rankings from single requests.
Our aim is constructive: document what is already working, describe uncertainties precisely and make it easier for builders to connect useful services responsibly. These first exchanges give us a concrete basis for continuing that work.