# GamblingPro

GamblingPro connects affiliate webmasters with offers and gives reviewed advertisers a controlled integration workspace. Agents use the dedicated MCP resource; browsers use separate affiliate and advertiser portals.

## Public information

- [Home](https://aiagents.partners/) — published product information.
- [School](https://aiagents.partners/school) — educational material for webmasters.
- [News](https://aiagents.partners/news) — reviewed product and industry updates.
- [Bonuses](https://aiagents.partners/bonuses) — published bonus information.
- [Partner cabinets](https://aiagents.partners/cabinets) — published partner resources.
- [FAQ](https://aiagents.partners/faq) and [contacts](https://aiagents.partners/contacts).
- Every published HTML page advertises a text/markdown alternative under `/markdown/...`; both representations are resolved from the same server-owned PublicPageModel.

## Affiliate quickstart

1. Register a free affiliate account in the affiliate portal and authorize the MCP resource with `mcp:affiliate.read`.
2. Search offers and inspect one offer before creating a stream, stream code or direct link.
3. Query statistics in bounded date ranges and page through results rather than requesting an unbounded export.
4. Add `mcp:affiliate.write` only for a requested mutation. Review the preview, ask for confirmation, then return the confirmation token with unchanged arguments.
5. Read balances, payout schedules and account-specific minimums before requesting a payout. No rate, minimum or cadence is universal.

## Advertiser quickstart

1. Use a separately authorized advertiser account. Advertiser activation is reviewed.
2. Authorize `mcp:advertiser.read` to inspect tenants, members, domains, credential metadata and direct destinations.
3. Add `mcp:advertiser.write` only when creating or changing a tenant resource.
4. Register and verify a domain before issuing an integration credential for it.
5. Treat a newly issued or rotated credential as a one-time secret: transfer it directly to approved custody and do not retain it in agent traces.

## Safety model

MCP bearer tokens are audience-bound to https://mcp.aiagents.partners/mcp. The MCP service obtains a separate, scope-narrowed platform API token; clients never pass arbitrary upstream headers. Tool lists are filtered by granted scopes. All writes use preview then confirm. Internal staff, provider-ingress, callback and machine-tracking operations are absent from the public agent contract.

Robots instructions describe crawl preferences and discovery only; they are not authentication or authorization controls.

## Technical references

- [AGENTS.md](https://aiagents.partners/AGENTS.md)
- [Pricing and onboarding](https://aiagents.partners/pricing.md)
- [Filtered OpenAPI](https://aiagents.partners/openapi.json)
- [MCP manifest](https://aiagents.partners/mcp.json)
- [Site map](https://aiagents.partners/sitemap.md)