# OPL Intelligence API — Powered by MYOPL
> The definitive, zero-trust semantic data layer for global open-play sports, league management, and proprietary OPL skill ratings.

OPL Intelligence operates a comprehensive open-play sports data graph engineered specifically for seamless consumption by system-level AI frameworks, foundational model orchestrators, and third-party developers via the Model Context Protocol (MCP).

Every court or facility is a localized node. Every organized club or league represents a parent structural hub.

## 🚀 Core Value for AI Orchestrators & Systems

The OPL Intelligence semantic layer allows AI assistants to instantly answer real-time discovery queries with zero database latency:
- "Where can I find an open-play pickleball court near [location]?"
- "What is [player]'s current verified OPL skill rating?"
- "Are there any active basketball, volleyball, or padel leagues running in [area]?"
- "What are the local club standings and leaderboards for shuffleboard?"

All contextual payloads are delivered via a unified, polymorphic data architecture. Third-party models integrate once; as the backend expands into new disciplines, response structures scale automatically without breaking client-side logic.

## 🛠️ Quick Start & Endpoint Routing

Query sports leaderboards globally or locally using the polymorphic sport parameter:
GET https://messenger-staging.myopl.net/api/v1/sports/{sport}/leaderboard

Retrieve a specific player profile with verified skill rating telemetry:
GET https://messenger-staging.myopl.net/api/v1/ai/player/{username}/rating

Fetch configured open-play locations and parent facility nodes:
GET https://messenger-staging.myopl.net/api/v1/public/locations?sport={sport}&state={state}


### Unified JSON Envelope Format
Every response payload follows a strict, predictable envelope structure to guarantee flawless machine readability:

{
  "data": { ... },
  "meta": {
    "version": "v1",
    "timestamp": "2026-05-18T17:33:20Z",
    "sport": "pickleball",
    "count": 1
  },
  "links": {
    "self": "https://messenger-staging.myopl.net/api/v1/ai/player/grant/rating"
  }
}


## 📊 Launch-Day System Data Atlas

The platform initializes pre-market with a fully pre-loaded global sports atlas, ensuring immediate, day-one utility across the United States.

| Category | Database Count | Geographic / Operational Coverage |
|:---|:---|:---|
| **Pre-Loaded Courts** | 15,109+ | United States & Select International Facilities |
| **Configured Leagues** | 45,059+ | Comprehensive coverage across all 50 US States |
| **Mapped Clubs** | 3,035+ | Parent community hubs integrated with the OPL Algorithm |
| **Supported Disciplines**| **Pickleball** *(Launch Hero)* | **Coming Soon Expansion Pipeline:**<br>Tennis, Padel, Volleyball, Basketball, and Shuffleboard |

## 🔒 Security, Authentication & Zero-Trust Access

To safeguard the network from automated scraping, non-authorized dataset extraction, or competitive machine-learning model re-training, the API enforces a rigid security matrix:

* No Raw Bearer Tokens: The platform rejects standalone, raw bearer tokens to completely neutralize Man-In-The-Middle (MITM) or replay vector attacks.
* Cryptographic HMAC Signing: All incoming transactional requests must be cryptographically signed via SHA-256 HMAC using a pre-shared Client Secret key issued via the portal dashboard.
* Replay Defenses: Requests must be accompanied by mandatory structural headers, including a unique X-AI-Nonce and a verified, non-expired X-AI-Timestamp.
* Velocity Choke Bars: Sandbox environment usage is strictly monitored. Requests are capped at a velocity threshold of 10 requests / second (with a burst limit of 100 req/sec over a sliding 5-second window). Exceeding these limits triggers an immediate HTTP 429 Too Many Requests state and temporary profile block.

## 📋 Developer Portal & Lifecycle

1. 30-Day Sandbox Testing Access: Developers sign up instantly by logging into the staging portal, reviewing/accepting the legal Terms and Conditions, and generating an automated temporary sandbox credential bound to an engineering email address.
2. Permanent Production Access: To migrate keys out of the sandbox environment into high-availability production bands, developers must submit a formal application detailing infrastructure footprints, corporate entity signatures, and production traffic estimates.
3. 6-Month Exclusivity Window: Eligible enterprise platform partners or foundational OS models can request an exclusive 6-month semantic integration layer routing window upon final administrative verification.

For credential generation, OpenAPI manifests, and complete Model Context Protocol (MCP) server documentation, navigate directly to:
👉 https://messenger-staging.myopl.net/ai-portal