Optimizely · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Optimizely Agent Decide API

2 actions 2 updates phrasing extends openapi/optimizely-decide-api-openapi.yml

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

View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 2

$.info

$.paths['/v1/decide'].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 Optimizely Agent Decide API
  version: 1.0.0
extends: openapi/optimizely-decide-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: 1
- target: $.paths['/v1/decide'].post
  update:
    x-apievangelist-phrasing:
      intent: Decide feature flag variations for a user
      effect: read
      questions:
      - How do I find out which feature flag variations a user should get from Optimizely?
      - If I don't pass any flag keys, will I get decisions for every flag?
      - Can I pass user attributes so audience targeting applies to the decision?
      instructions:
      - text: Decide flags {keys} for user {userId}.
        slots:
          keys: query.keys
          userId: requestBody.userId
      - text: Get decisions on all flags for user {userId} with attributes {userAttributes}.
        slots:
          userId: requestBody.userId
          userAttributes: requestBody.userAttributes
      - text: Decide flags for user {userId} applying forced decisions {forcedDecisions}.
        slots:
          userId: requestBody.userId
          forcedDecisions: requestBody.forcedDecisions
      method: generated
      generated: '2026-09-26'