Public Docs
iGaming Suite Public Documentation
Public documentation hub for iGaming Suite discovery policy, Horus Lab Developer Sandbox, agent-readable manifests, crawler policy and safe public product contracts.
Audience
Developers, AI agents, search crawlers, partners, technical evaluators and implementation teams.
Proof
The public docs currently expose Horus Lab Developer Sandbox documentation and the AI discovery/crawler policy without exposing private Suite routes or customer data.
Limits
Public docs explain allowed contracts. Authenticated API calls, API-key-scoped data and private workspaces remain protected by Suite authorization.
Product evidence
Visible product proof for humans and agents
Visible proof table
| Signal | Visible proof on this page | Discovery value |
|---|---|---|
| Audience | Developers, AI agents, search crawlers, partners, technical evaluators and implementation teams. | Connects the page to a real professional audience instead of generic iGaming traffic. |
| Proof | The public docs currently expose Horus Lab Developer Sandbox documentation and the AI discovery/crawler policy without exposing private Suite routes or customer data. | Gives crawlers, AI retrieval systems and readers a concrete product claim to understand. |
| Limits | Public docs explain allowed contracts. Authenticated API calls, API-key-scoped data and private workspaces remain protected by Suite authorization. | Builds trust by stating what the public page does not expose or prove. |
| Public contract signals | docs/horus-lab-developer-sandbox | docs/ai-discovery-policy | llms.txt | ai-manifest.json | Makes product APIs, data objects and entity names easy to parse and cite. |
What this page makes discoverable
- Developer sandbox overview
- AI discovery and crawler policy
- Agent-readable manifests
- Private/public boundary documentation
Public contract signals
These names help humans, search engines and AI retrieval systems understand the product boundary without exposing private workspace data.
- docs/horus-lab-developer-sandbox
- docs/ai-discovery-policy
- llms.txt
- ai-manifest.json
Search intent map
What professionals are likely to search
| Search language | Likely reader | Page answer |
|---|---|---|
| Horus Lab API documentation | Developers and technical evaluators | Routes readers to the Developer Sandbox contract, scoped API key model, data package and proof package. |
| iGaming Suite AI crawler policy | Search engines, AI retrieval systems and partners | Explains which public pages are discoverable and which authenticated surfaces remain private. |
| agent-readable iGaming software docs | AI agents and integration teams | Connects semantic HTML pages, sitemap, llms.txt and ai-manifest.json as public navigation aids. |
Discovery rationale
Public docs are a contract layer, not a data leak
The docs hub should let developers, crawlers and agents understand what iGaming Suite exposes publicly without revealing private Suite state. It gives a stable reading path for product contracts, but credentials, sessions, generated run data and customer records remain behind authorization.
- Public: product definitions, endpoint names, authentication shape, response contract names and limitations.
- Private: API keys, sessions, customer rows, run payloads, admin controls and unreviewed directory data.
- Search-critical: public docs should remain static HTML, canonical, internally linked and readable without JavaScript execution.
Discovery rationale
Agent reading path
A human developer and an AI agent should be able to start at the docs hub, identify the sandbox, understand allowed crawler behavior, open the manifest files and then follow canonical product pages without guessing.
- Start with the docs hub for the product contract map.
- Open Horus Lab Developer Sandbox for API and data-package vocabulary.
- Open AI Discovery Policy for crawler, private-route and llms.txt limitations.
- Open glossary for canonical terms such as click_id, btag/VTag, NGR, postback and operator data batch.
Discovery rationale
Documentation as a trust surface
The docs hub is not only a navigation page. It is the public proof that iGaming Suite understands which contracts can be read by crawlers and which actions require authenticated product access.
- Developer docs explain Horus Lab sandbox behavior.
- AI discovery docs explain crawler and private-data policy.
- Machine files give search engines and agents a stable public map.
Evidence discipline
Why this page is built this way
- Google JavaScript SEO basics Supports shipping meaningful public content in initial HTML instead of relying only on the authenticated React workspace.
- Google sitemap guidance Supports canonical sitemap entries and robots.txt sitemap discovery for the public docs surface.
Questions this page answers
Can AI agents use these docs?
Yes. The docs are written to help human developers and AI agents understand public contracts, but actual data access still requires the correct credentials and authorization.
Are private API responses documented publicly?
No. Public docs can name contracts and boundaries, but they must not expose customer data, secrets, session data or private operator records.
Why are these docs separate from the Suite app?
The authenticated Suite app is a product workspace. Public docs need static, crawlable HTML so search engines and AI retrieval systems can understand the product without opening private routes.