Emboss · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Getemboss Ai .well Known API

4 actions 4 updates phrasing extends openapi/getemboss-ai-well-known-api-openapi.yml

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

View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 4

$.info

$.paths['/.well-known/oauth-authorization-server'].get

$.paths['/.well-known/oauth-protected-resource/mcp'].get

$.paths['/.well-known/{_rest}'].options

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 Getemboss Ai .well Known API
  version: 1.0.0
extends: openapi/getemboss-ai-well-known-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['/.well-known/oauth-authorization-server'].get
  update:
    x-apievangelist-phrasing:
      intent: Get OAuth authorization server metadata
      effect: read
      questions:
      - Where are the OAuth authorization and token endpoints advertised?
      - Does the service publish RFC 8414 authorization server metadata?
      instructions:
      - text: Fetch the OAuth authorization server metadata.
      - text: Discover the authorization and token endpoints.
      method: generated
      generated: '2026-10-01'
- target: $.paths['/.well-known/oauth-protected-resource/mcp'].get
  update:
    x-apievangelist-phrasing:
      intent: Get protected resource metadata for the MCP server
      effect: read
      questions:
      - Which authorization server protects the MCP endpoint?
      - Is there protected resource metadata an MCP client can read before connecting?
      instructions:
      - text: Fetch the MCP protected resource metadata.
      - text: Find out which authorization server the MCP endpoint trusts.
      method: generated
      generated: '2026-10-01'
- target: $.paths['/.well-known/{_rest}'].options
  update:
    x-apievangelist-phrasing:
      intent: Answer CORS preflight for well-known files
      effect: read
      questions:
      - Can browser-based clients read the well-known discovery files cross-origin?
      - Do the well-known paths respond to CORS preflight?
      instructions:
      - text: Send a CORS preflight for well-known path {_rest}.
        slots:
          _rest: path._rest
      - text: Check cross-origin access to .well-known/{_rest}.
        slots:
          _rest: path._rest
      method: generated
      generated: '2026-10-01'