# Aggregator.Casino — LLM Full Index

## Overview
Aggregator.Casino is an HTTP-native casino for autonomous AI agents. Built on The Aggregator B2B iGaming platform, it provides a clean API surface for agents to discover games, deposit funds via x402 payment protocol, launch sessions, and withdraw winnings — with zero accounts, zero KYC, zero human interaction.

## Hosts
- Testnet: `https://testnet.aggregator.casino`
- Production: `https://aggregator.casino` (not yet live)
- Parent platform: `https://the-aggregator.io`
- Machine API: `https://api.aggregator.gg/v1`

## Authentication
- Protocol: Ethereum wallet signature (SIWE-style)
- Flow: `GET /api/agent/auth/challenge?address=0x...` → sign message → `POST /api/agent/auth/verify` with signature
- No accounts, no registration, no KYC — wallet address is the identity

## API surface

### Game discovery
- `GET /api/agent/games` — list all available games
- Response includes: game ID, provider, title, category, RTP, min/max bet
- Filter by provider, category, or search by name

### Session management
- `POST /api/agent/sessions` — create a new game session
- Requires: game ID, bet amount, x402 payment header
- Returns: session URL, session ID, expiry

### Balance and payments
- `GET /api/agent/balance` — current USDC balance for wallet
- Payment protocol: x402 — attach `X-Payment` header with signed USDC transfer
- Network: Base Sepolia (testnet)
- Token: USDC on Base Sepolia

### Withdrawals
- `POST /api/agent/withdraw` — withdraw balance to wallet address
- Requires: amount, destination address
- Settlement: on-chain USDC transfer

## x402 payment protocol
The x402 protocol enables HTTP-native payments:
1. Agent sends request with `X-Payment: <signed-usdc-transfer>`
2. Server verifies payment on-chain
3. If valid, request proceeds; if not, returns `402 Payment Required`
4. This eliminates the need for pre-funded accounts or API keys for billing

## Integration packages
- MCP server: `@theaggregator/mcp-server` — stdio MCP server with casino-specific tools
- TypeScript SDK: `@theaggregator/sdk` — programmatic API client
- Integration Autopilot: downloadable pack from `https://the-aggregator.io/api/downloads/operator-integration-autopilot.zip`

## Agent workflow (step by step)
1. **Connect**: Sign an auth challenge with your Ethereum wallet
2. **Discover**: Browse available games via the games endpoint
3. **Fund**: Obtain Base Sepolia USDC from a faucet
4. **Play**: Create a session with x402 payment — get back a playable session URL
5. **Monitor**: Check balance and session status
6. **Cash out**: Withdraw winnings to your wallet address

## Technical details
- All API responses are JSON
- Errors follow standard HTTP status codes with JSON error bodies
- Rate limiting: reasonable limits for testnet usage
- CORS: enabled for agent access
- Testnet environment uses `sk_test_*` API key prefix internally
- Game sessions run real licensed content from production providers in sandbox mode

## Safety and compliance
- Testnet only — no real money involved
- Uses Base Sepolia USDC (testnet tokens, zero monetary value)
- Licensed game content from real providers (TRUE LABS, BGaming, etc.)
- Parent platform (The Aggregator) handles all licensing and compliance
- For production/mainnet access, formal onboarding via the-aggregator.io is required