Bellator Schedule Intelligence Sandbox API

openapi: 3.2.0
info:
  title: Bellator Schedule Intelligence Sandbox API
  description: 'Bellator Schedule Intelligence APIs - Stateless Schedule Health APIs


    ## Features


    * **Schedule Analysis** - Comprehensive schedule health analysis

    * **Critical Path** - CPM-based critical path calculation

    * **Validation** - Schedule validation and quality checks

    * **Future: Resource Management** - Resource allocation and leveling

    * **Future: Simulation** - Monte Carlo and what-if analysis

    * **Future: AI Recommendations** - LLM-powered optimization suggestions


    ## Authentication


    API key authentication via `x-api-key` header or OAuth 2.0 Bearer token via `Authorization` header.


    ### API Key Authentication (Legacy)

    Include API key in `x-api-key` header.


    ### OAuth 2.0 / Azure AD Authentication (Recommended)

    Include Bearer token in `Authorization` header: `Authorization: Bearer `


    Tiers:

    - **Free**: 2,000 tasks, 100 req/min, 5MB payload

    - **Professional**: 5,000 tasks, 500 req/min, 25MB payload

    - **Enterprise**: 50,000 tasks, 2,000 req/min, 100MB payload

    - **Government**: 100,000+ tasks, 10,000 req/min, 500MB payload


    ## Usage Metering


    All API requests are metered and tracked for:

    - Request duration (milliseconds)

    - Task count processed

    - Token consumption (for LLM operations)

    - Estimated cost (USD)


    Metering events are emitted to logs and can be integrated with billing systems.


    ## Security


    * Tier-based task limits (500-100,000 tasks per request)

    * Tier-based payload limits (5-500 MB)

    * Input validation and sanitization

    * Tier-based rate limiting (100-10,000 requests per 60 seconds)'
  version: 0.4.0
tags:
- name: Sandbox
paths:
  /api/v1/sandbox/fixtures:
    get:
      tags:
      - Sandbox
      summary: List Sandbox Fixtures
      description: 'List all available sandbox fixtures.


        Returns the full fixture catalog with metadata. No authentication required.


        Use fixture names as the `schedule_fixture` value in any analysis request body

        to run the endpoint against pre-loaded data without supplying a `tasks` array.


        **Example request using a fixture:**

        ```json

        POST /api/v1/forensics/dcma-14-point

        {

        "schedule_fixture": "dcma_violations_sample",

        "options": { "threshold_percent": 10 }

        }

        ```


        **Sandbox policy:**

        - Fixture requests do not consume monthly quota or rate-limit credits

        - Fixture requests still require a valid API key

        - All endpoint options apply normally to fixture data

        - Fixture data is read-only and versioned with the API minor version'
      operationId: list_sandbox_fixtures_api_v1_sandbox_fixtures_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SandboxFixtureCatalog'
components:
  schemas:
    SandboxFixtureCatalog:
      properties:
        fixture_version:
          type: string
          title: Fixture Version
          description: Fixture data version (tied to API minor version)
        fixture_count:
          type: integer
          title: Fixture Count
          description: Number of loaded fixtures
        fixtures:
          items:
            additionalProperties: true
            type: object
          type: array
          title: Fixtures
          description: Full fixture catalog with metadata
      type: object
      required:
      - fixture_version
      - fixture_count
      - fixtures
      title: SandboxFixtureCatalog
      description: Response from GET /api/v1/sandbox/fixtures.
      example:
        fixture_count: 12
        fixture_version: 0.2.0
        fixtures:
        - description: Fully compliant 25-task schedule. No violations.
          domain: construction
          expected_outcomes:
            dcma_14_point:
              checks_failed: 0
              overall_pass: true
            health_score:
              grade: A
              score_range:
              - 88
              - 95
          name: clean_baseline_sample
          recommended_endpoints:
          - /api/v1/health/score
          - /api/v1/schedule/cpm
          - /api/v1/forensics/dcma-14-point
          task_count: 25
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key
      description: API key for authentication. Required when API_KEY is configured.
    OAuth2:
      type: oauth2
      flows:
        authorizationCode:
          authorizationUrl: https://login.microsoftonline.com/{tenant}/oauth2/v2.0/authorize
          tokenUrl: https://login.microsoftonline.com/{tenant}/oauth2/v2.0/token
          scopes:
            api.read: Read access to API
            api.write: Write access to API
      description: OAuth 2.0 / Azure AD authentication (recommended)
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: JWT Bearer token from OAuth 2.0 / Azure AD