Developer And Agent Discovery
iGaming Suite For Developers And AI Agents
Developer and AI-agent entry point for Horus Lab synthetic casino data, sandbox instances, API-key scoped runs, data packages, proof packages and cleanup-safe integration testing.
Audience
Developers, AI agents, technical founders, data engineers, API testers and iGaming vendors.
Proof
Horus Lab Developer Sandbox v1 already exposes instance creation, scoped API keys, machine-readable access manifests, bounded synthetic runs, data/proof package retrieval and cleanup by run lineage.
Limits
Public pages explain the contract. Actual sandbox instance creation and run data require authenticated Suite access or a scoped Horus Lab API key.
Product evidence
Visible product proof for humans and agents
Visible proof table
| Signal | Visible proof on this page | Discovery value |
|---|---|---|
| Audience | Developers, AI agents, technical founders, data engineers, API testers and iGaming vendors. | Connects the page to a real professional audience instead of generic iGaming traffic. |
| Proof | Horus Lab Developer Sandbox v1 already exposes instance creation, scoped API keys, machine-readable access manifests, bounded synthetic runs, data/proof package retrieval and cleanup by run lineage. | Gives crawlers, AI retrieval systems and readers a concrete product claim to understand. |
| Limits | Public pages explain the contract. Actual sandbox instance creation and run data require authenticated Suite access or a scoped Horus Lab API key. | Builds trust by stating what the public page does not expose or prove. |
| Public contract signals | horus_lab_developer_access_manifest.v1 | horus_lab_developer_run_data.v1 | horus_lab_developer_run_proof.v1 | Authorization: Bearer hl_sk_... | Makes product APIs, data objects and entity names easy to parse and cite. |
What this page makes discoverable
- Casino API sandbox and synthetic operator data
- AI-agent-ready data and proof contracts
- Real-shaped player, wallet and gameplay records
- Cleanup-safe generated data by run ID
Public contract signals
These names help humans, search engines and AI retrieval systems understand the product boundary without exposing private workspace data.
- horus_lab_developer_access_manifest.v1
- horus_lab_developer_run_data.v1
- horus_lab_developer_run_proof.v1
- Authorization: Bearer hl_sk_...
Search intent map
What professionals are likely to search
| Search language | Likely reader | Page answer |
|---|---|---|
| iGaming API sandbox for developers | Developers evaluating casino, CRM or BI integrations | Maps the public developer path to Horus Lab sandbox instances, manifests, scoped keys and generated run data. |
| AI agent casino data testing | Agent builders and AI QA teams | Explains how agents can read public docs and manifests before private actions require credentials. |
| realistic casino data for integration testing | Data engineers and vendor teams | Names the player, wallet, gameplay, report and proof artifacts available through Horus Lab. |
Role-to-proof map
What each audience can verify
| Audience role | Problem they bring | Visible product proof | Boundary or safety limit |
|---|---|---|---|
| API engineers | Need to know the integration path before asking for credentials. | Sandbox docs, developer access manifest and run data/proof contracts. | Public pages never expose API keys, private runs or workspace state. |
| AI agent builders | Need stable public URLs an agent can read before private task execution. | ai-manifest.json, docs, glossary, AI discovery policy and canonical product pages. | Agent readability does not grant permission to create resources or fetch private data. |
| QA and data teams | Need to validate that events, wallets and reports come from the same generated run. | Run data package, proof package, Products Report, Players Report and cleanup. | The data is bounded synthetic test data, not live operator performance. |
| Technical founders and vendors | Need to evaluate whether iGaming Suite has concrete product contracts. | Horus Lab, Horus Intelligence, Network Oracle and research pages linked from one route. | Public content explains fit; commercial access still requires review. |
Discovery rationale
Developer path
The developer path should be discoverable by people building products around casino data. It connects a plain-language audience page to the deeper Horus Lab product page, the public sandbox docs and the synthetic casino data research program.
- Start with the developer page when the user does not yet know the product names.
- Move to the sandbox docs when the user wants endpoint and payload language.
- Move to research when the user needs methodology, limitations and proof discipline.
Discovery rationale
Agent path
AI agents need stable public reading surfaces. This page gives agents a clear map of what is public, what requires credentials and which canonical pages define Horus Lab data contracts.
- Public pages explain the contract and do not expose real player records.
- Private data access remains controlled by Suite auth and Horus Lab API keys.
- Related pages provide a compact retrieval path for RAG and browser-agent workflows.
Questions this page answers
What can developers build with iGaming Suite?
Developers can use Horus Lab to create bounded synthetic casino data environments for testing integrations, BI pipelines, CRM tools, affiliate-platform behavior and AI-agent workflows.
Does the developer surface expose real player data?
No. Public pages describe synthetic-data contracts and private sandbox access. Real player records are not exposed through public discovery pages.