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.
The public docs currently expose Horus Lab Developer Sandbox documentation and the AI discovery/crawler policy without exposing private Suite routes or customer data.
Who it is for Developers, AI agents, search crawlers, partners, technical evaluators and implementation teams.
What it does
- Developer sandbox overview
- AI discovery and crawler policy
- Agent-readable manifests
- Private/public boundary documentation
Inside the Suite
A real product view
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.
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.
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.
Product surfaces
These are the product names, modules and data objects used inside iGaming Suite today.
- docs/horus-lab-developer-sandbox
- docs/ai-discovery-policy
- llms.txt
- ai-manifest.json
FAQ
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.