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.
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.
Who it is for Developers, AI agents, technical founders, data engineers, API testers and iGaming vendors.
What it does
- 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
Inside the Suite
A real product view
Developer path
The developer path is for 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.
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.
Product surfaces
These are the product names, modules and data objects used inside iGaming Suite today.
- horus_lab_developer_access_manifest.v1
- horus_lab_developer_run_data.v1
- horus_lab_developer_run_proof.v1
- Authorization: Bearer hl_sk_...
FAQ
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.