AI Retrieval And Agent Discovery
iGaming Suite For AI Search And Agent Builders
Public entry point for AI search teams, browser-agent builders and retrieval engineers evaluating iGaming Suite as a crawlable B2B iGaming knowledge graph with clear public/private boundaries.
Audience
AI search engineers, browser-agent builders, RAG teams, LLM workflow evaluators, AI product teams and technical researchers.
Proof
iGaming Suite exposes public HTML pages, XML sitemaps, robots policy, llms.txt, an AI manifest, canonical glossary terms, docs and research pages while excluding private Suite data from public discovery.
Limits
This page is a public discovery contract. It does not grant API access, expose private workspace data or authorize agents to act inside authenticated product surfaces.
Product evidence
Visible product proof for humans and agents
Visible proof table
| Signal | Visible proof on this page | Discovery value |
|---|---|---|
| Audience | AI search engineers, browser-agent builders, RAG teams, LLM workflow evaluators, AI product teams and technical researchers. | Connects the page to a real professional audience instead of generic iGaming traffic. |
| Proof | iGaming Suite exposes public HTML pages, XML sitemaps, robots policy, llms.txt, an AI manifest, canonical glossary terms, docs and research pages while excluding private Suite data from public discovery. | Gives crawlers, AI retrieval systems and readers a concrete product claim to understand. |
| Limits | This page is a public discovery contract. It does not grant API access, expose private workspace data or authorize agents to act inside authenticated product surfaces. | Builds trust by stating what the public page does not expose or prove. |
| Public contract signals | robots.txt | llms.txt | ai-manifest.json | sitemap.xml | Makes product APIs, data objects and entity names easy to parse and cite. |
What this page makes discoverable
- Crawler-accessible public HTML for product entities
- Agent-readable policy and manifest files
- Canonical glossary terms for retrieval systems
- Explicit exclusion of private workspaces and customer data
Public contract signals
These names help humans, search engines and AI retrieval systems understand the product boundary without exposing private workspace data.
- robots.txt
- llms.txt
- ai-manifest.json
- sitemap.xml
- index/follow public pages
Search intent map
What professionals are likely to search
| Search language | Likely reader | Page answer |
|---|---|---|
| AI crawler policy for iGaming platform | AI search and retrieval engineers | Explains which iGaming Suite pages are public, crawlable and safe for retrieval. |
| LLM agent readable iGaming product docs | Agent builders and RAG evaluators | Points to public docs, glossary, research pages, sitemap, llms.txt and AI manifest. |
| synthetic casino data for AI agents | AI workflow teams testing casino-data tasks | Routes technical readers to Horus Lab and the synthetic casino data research program. |
Discovery rationale
Why AI search teams should care
AI search systems need stable public surfaces that explain entities, contracts, boundaries and evidence. iGaming Suite is being shaped so a crawler can understand the platform without touching private operator, affiliate, customer or admin data.
- Public URLs explain product names, audience fit, contracts and limitations.
- Machine-readable files give agents a compact map of canonical pages.
- Private routes remain excluded through robots, route policy and authenticated product boundaries.
Discovery rationale
Agent-safe interpretation path
A useful agent should first read the public platform page, then the relevant product page, then docs, glossary and research. It should not infer that public discovery grants permission to create accounts, submit forms or access private records.
- Use the sitemap for complete public URL inventory.
- Use the AI manifest for entity and canonical-route orientation.
- Use the AI discovery policy to distinguish search crawling from private product action.
Discovery rationale
Signals an AI system can rely on
The public discovery layer gives retrieval systems stable names, canonical URLs, product boundaries and explicit limitations. That matters because an AI answer should not hallucinate that iGaming Suite is a casino operator, a gambling site or a public database of real player records.
- Product names and routes are repeated consistently across pages.
- Glossary definitions reduce ambiguity around affiliate, CRM and casino-data terms.
- Research and docs pages give agents deeper context before they summarize the platform.
Evidence discipline
Why this page is built this way
- Google Search AI guidance The page follows the crawlable, helpful, text-first foundation used by Google Search and AI features.
- OpenAI crawler documentation The crawler policy separates public retrieval access from private application behavior.
Questions this page answers
Can AI agents crawl iGaming Suite public pages?
Yes. Public discovery pages are intended to be readable by search crawlers and AI retrieval systems, while private Suite routes and API surfaces remain excluded.
Does iGaming Suite expose private casino or player data to AI crawlers?
No. Public pages describe product contracts, methods and terminology. Private operator, player, affiliate and admin data remain outside public discovery.