Tray.ai · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Tray Ai Connectors API

7 actions 7 updates phrasing extends openapi/tray-ai-connectors-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Tray.ai's API. It is a proposal applied on top of the contract, not a document Tray.ai publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 7

$.info
$.paths['/connectors'].get
$.paths['/connectors/{connectorName}/versions/{connectorVersion}'].get
$.paths['/connectors/{connectorName}/versions/{connectorVersion}/call'].post
$.paths['/core/v1/connectors'].get
$.paths['/core/v1/connectors/{connector-name}/versions/{connector-version}/operations'].get
$.paths['/core/v1/connectors/{connector-name}/versions/{connector-version}/call'].post

OpenAPI Overlay

Raw ↑
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Tray Ai Connectors API
  version: 1.0.0
extends: openapi/tray-ai-connectors-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 6
- target: $.paths['/connectors'].get
  update:
    x-apievangelist-phrasing:
      intent: List connectors in the library (unversioned)
      effect: read
      questions:
      - Which third-party connectors are available in the Tray.ai connector library?
      - Can I browse every connector on the unversioned /connectors endpoint?
      instructions:
      - text: List all connectors from the unversioned connectors endpoint.
      - text: Show me the whole connector library.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/connectors/{connectorName}/versions/{connectorVersion}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a connector version's operations and schemas
      effect: read
      questions:
      - What operations and input schemas does a particular connector version expose?
      - Can I see the output schema of every operation in one connector version?
      instructions:
      - text: Get details for connector {connector} version {version}, including input and output schemas.
        slots:
          connector: path.connectorName
          version: path.connectorVersion
      - text: Describe connector version {version} of {connector}.
        slots:
          connector: path.connectorName
          version: path.connectorVersion
      method: generated
      generated: '2026-09-26'
- target: $.paths['/connectors/{connectorName}/versions/{connectorVersion}/call'].post
  update:
    x-apievangelist-phrasing:
      intent: Execute a connector operation (unversioned)
      effect: write
      questions:
      - Is calling a connector operation billable?
      - Must my input match the operation's input schema when I execute a connector on the unversioned endpoint?
      instructions:
      - text: Execute operation {operation} on connector {connector} version {version} with auth {auth}.
        slots:
          operation: requestBody.operation
          connector: path.connectorName
          version: path.connectorVersion
          auth: requestBody.authId
      - text: Run {operation} on {connector} {version} with input {input} via the unversioned call endpoint.
        slots:
          operation: requestBody.operation
          connector: path.connectorName
          version: path.connectorVersion
          input: requestBody.input
      method: generated
      generated: '2026-09-26'
- target: $.paths['/core/v1/connectors'].get
  update:
    x-apievangelist-phrasing:
      intent: List connectors with core v1
      effect: read
      questions:
      - What connectors does the core v1 API list?
      - Where can I get the core v1 catalog of connector names and versions?
      instructions:
      - text: List connectors through the core v1 API.
      - text: Get the core v1 connector catalog.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/core/v1/connectors/{connector-name}/versions/{connector-version}/operations'].get
  update:
    x-apievangelist-phrasing:
      intent: List a connector version's operations
      effect: read
      questions:
      - Which operations can I call on a given connector version?
      - How do I find the operation names to pass when calling a connector?
      instructions:
      - text: List the operations of connector {connector} version {version} via core v1.
        slots:
          connector: path.connector-name
          version: path.connector-version
      - text: Show callable operation names for {connector} at version {version}.
        slots:
          connector: path.connector-name
          version: path.connector-version
      method: generated
      generated: '2026-09-26'
- target: $.paths['/core/v1/connectors/{connector-name}/versions/{connector-version}/call'].post
  update:
    x-apievangelist-phrasing:
      intent: Call a connector operation with core v1
      effect: write
      questions:
      - Can the core v1 call-connector endpoint also return the operation's output schema?
      - How do I run a connector operation through the core v1 API?
      instructions:
      - text: Using core v1, call {operation} on connector {connector} version {version} with input {input}.
        slots:
          operation: requestBody.operation
          connector: path.connector-name
          version: path.connector-version
          input: requestBody.input
      - text: 'Core v1: run {operation} on {connector} {version} with auth {auth}, input {input}, returning the output schema.'
        slots:
          operation: requestBody.operation
          connector: path.connector-name
          version: path.connector-version
          auth: requestBody.authId
          input: requestBody.input
      method: generated
      generated: '2026-09-26'