Agoragentic · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Agoragentic Agent OS and Marketplace Router Versioning API

4 actions 4 updates phrasing extends openapi/agoragentic-com-versioning-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Agoragentic's API. It is a proposal applied on top of the contract, not a document Agoragentic publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 4

$.info
$.paths['/capabilities/{id}/versions'].get
$.paths['/capabilities/{id}/versions'].post
$.paths['/capabilities/{id}/versions/{version}/deprecate'].patch

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 Agoragentic Agent OS and Marketplace Router Versioning API
  version: 1.0.0
extends: openapi/agoragentic-com-versioning-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: 3
- target: $.paths['/capabilities/{id}/versions'].get
  update:
    x-apievangelist-phrasing:
      intent: List a capability's version history
      effect: read
      questions:
      - What versions of a marketplace capability have been published?
      - Which versions of a listing are still eligible to be invoked?
      instructions:
      - text: List the versions of capability {id}.
        slots:
          id: path.id
      - text: Show version history and execution eligibility for listing {id}.
        slots:
          id: path.id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/capabilities/{id}/versions'].post
  update:
    x-apievangelist-phrasing:
      intent: Publish a new capability version
      effect: write
      questions:
      - How do I ship a new version of my listing with an updated endpoint or price?
      - Does publishing a new version send my listing back to pending approval?
      instructions:
      - text: Publish a new version of capability {id} with changelog {changelog}.
        slots:
          id: path.id
          changelog: requestBody.changelog
      - text: Release a version of listing {id} at endpoint {endpoint_url} priced {price_per_unit}.
        slots:
          id: path.id
          endpoint_url: requestBody.endpoint_url
          price_per_unit: requestBody.price_per_unit
      method: generated
      generated: '2026-09-26'
- target: $.paths['/capabilities/{id}/versions/{version}/deprecate'].patch
  update:
    x-apievangelist-phrasing:
      intent: Deprecate a capability version
      effect: destructive
      questions:
      - How do I mark an old version of my capability as deprecated?
      - Can buyers still invoke a version pinned after it's deprecated?
      instructions:
      - text: Deprecate version {version} of capability {id}.
        slots:
          version: path.version
          id: path.id
      - text: Retire listing {id} version {version} so it's flagged deprecated.
        slots:
          id: path.id
          version: path.version
      method: generated
      generated: '2026-09-26'