Dynamic Feed · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Dynamicfeed Ai Weather API

4 actions 4 updates phrasing extends openapi/dynamicfeed-ai-weather-api-openapi.yml

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

View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 4

$.info

$.paths['/weather'].get

$.paths['/v1/openweather/current'].get

$.paths['/v1/openweather/forecast'].get

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 Dynamicfeed Ai Weather API
  version: 1.0.0
extends: openapi/dynamicfeed-ai-weather-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: 3
- target: $.paths['/weather'].get
  update:
    x-apievangelist-phrasing:
      intent: Get current weather for a place
      effect: read
      questions:
      - What is the weather like in Tokyo right now?
      - Can I get current temperature and wind by coordinates instead of a city name?
      instructions:
      - text: Get the current weather in {city}.
        slots:
          city: query.city
      - text: Show current conditions at {lat}, {lon}.
        slots:
          lat: query.lat
          lon: query.lon
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v1/openweather/current'].get
  update:
    x-apievangelist-phrasing:
      intent: Get current weather via the legacy alias
      effect: read
      questions:
      - Does the old openweather current-conditions path still work for existing integrations?
      - What does the legacy current weather alias return now?
      instructions:
      - text: Call the legacy openweather current alias for {city}.
        slots:
          city: query.city
      - text: Use the older current-weather alias path for {lat}, {lon}.
        slots:
          lat: query.lat
          lon: query.lon
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v1/openweather/forecast'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a forecast via the legacy alias
      effect: read
      questions:
      - Does the old openweather forecast path still return a forecast?
      - Is the legacy forecast alias still supported for my integration?
      instructions:
      - text: Call the legacy openweather forecast alias for {city} over {days} days.
        slots:
          city: query.city
          days: query.days
      - text: Use the older forecast alias path for {lat}, {lon}.
        slots:
          lat: query.lat
          lon: query.lon
      method: generated
      generated: '2026-10-01'