overlay: 1.0.0
info:
  title: API Evangelist enhancements — Green Screens AI prediction-v2
  version: 1.0.0
extends: ../openapi/green-screens-ai-prediction-v2-api-openapi.yml
x-provenance:
  generated: '2026-09-12'
  method: generated
  source: Generated by API Evangelist over the verbatim provider OpenAPI harvested from https://connect.greenscreens.ai/prediction/v2/openapi.yaml.
    The original document is never mutated.
actions:
- target: $.info
  description: Record API Evangelist provenance and the runtime semantics the contract does not state.
  update:
    x-apievangelist:
      providerId: green-screens-ai
      provider: Green Screens AI (Triumph Intelligence)
      harvested: '2026-09-12'
      source: https://connect.greenscreens.ai/prediction/v2/openapi.yaml
      docs: https://connect.greenscreens.ai/
      errors: errors/green-screens-ai-problem-types.yml
      conventions: conventions/green-screens-ai-conventions.yml
      authentication: authentication/green-screens-ai-authentication.yml
      rate_limits: rate-limits/green-screens-ai-rate-limits.yml
- target: $
  description: Declare the runtime guarantees this API does NOT provide, so an agent does not assume them.
  update:
    x-idempotency:
      supported: false
      coverage: none
      header: null
      note: No Idempotency-Key, no client request id, and no replay-safety statement anywhere in the provider
        contract or help center.
    x-dry-run:
      supported: false
    x-rate-limit-signaling:
      status: 429
      code: too_many_requests
      headers: null
      retry_after: false
      note: Throttling is declared but no limit value and no runtime header is published. Back off with
        jitter.
    x-error-format:
      rfc9457: false
      media_type: application/json
      shape: '{ code, message, errors?: [{field, message, value}] }'
    x-request-id:
      supported: false
    x-domain-identifiers:
    - NMFTA SCAC
    - FMCSA MC number
    - USDOT number
- target: $.servers
  description: Note that connect.greenscreens.ai is the documentation host, not an API host.
  update:
  - x-note: Production calls go to api.greenscreens.ai (or intelligence.triumph.io); connect.greenscreens.ai
      serves documentation only.