Treasure Data · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for llm-api Action API

3 actions 3 updates phrasing extends openapi/treasure-data-action-api-openapi.yml

Generated by API Evangelist Written by API Evangelist tooling for Treasure Data's API. It is a proposal applied on top of the contract, not a document Treasure Data publishes.

View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 3

$.info

$.paths['/api/actions'].get

$.paths['/api/actions/{id}/slack'].post

OpenAPI Overlay

# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for llm-api Action API
  version: 1.0.0
extends: openapi/treasure-data-action-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-10-01'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 2
- target: $.paths['/api/actions'].get
  update:
    x-apievangelist-phrasing:
      intent: List LLM actions
      effect: read
      questions:
      - Which actions are available to my LLM agents?
      - Can I filter actions by project, parent segment or service type?
      instructions:
      - text: List the LLM actions in my account.
      - text: List actions for project {project_id}, at most {limit}.
        slots:
          project_id: query.filter[project_id]
          limit: query.page[limit]
      - text: List actions of service type {service_type} for parent segment {parent_segment_id}.
        slots:
          service_type: query.filter[service_type]
          parent_segment_id: query.filter[parent_segment_id]
      method: generated
      generated: '2026-10-01'
- target: $.paths['/api/actions/{id}/slack'].post
  update:
    x-apievangelist-phrasing:
      intent: Run an action from a Slack command
      effect: write
      questions:
      - Can a Slack slash command trigger one of my LLM actions?
      - What does the Slack endpoint of an action need from the command payload?
      instructions:
      - text: Run action {id} for Slack command {command} with text {text}, replying to {response_url}.
        slots:
          id: path.id
          command: requestBody.command
          text: requestBody.text
          response_url: requestBody.response_url
      - text: Send Slack text {text} from command {command} to action {id}, posting the reply to {response_url}.
        slots:
          text: requestBody.text
          command: requestBody.command
          id: path.id
          response_url: requestBody.response_url
      method: generated
      generated: '2026-10-01'