Aembit · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Aembit Cloud Compliance API

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

What the actions change

x-apievangelist-phrasing

Targets 3

$.info
$.paths['/api/v1/compliance-settings'].get
$.paths['/api/v1/compliance-settings'].put

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 Aembit Cloud Compliance API
  version: 1.0.0
extends: openapi/aembit-compliance-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: 2
- target: $.paths['/api/v1/compliance-settings'].get
  update:
    x-apievangelist-phrasing:
      intent: Get global compliance settings
      effect: read
      questions:
      - What compliance rules apply when creating access policies?
      - Which global compliance settings are enabled in my tenant?
      instructions:
      - text: Show my global compliance settings.
      - text: List the compliance rules that govern policy creation.
      method: generated
      generated: '2026-09-26'
- target: $.paths['/api/v1/compliance-settings'].put
  update:
    x-apievangelist-phrasing:
      intent: Change a global compliance setting
      effect: write
      questions:
      - How do I change one of the global compliance rules?
      - Can I turn a compliance requirement on or off?
      instructions:
      - text: Set compliance setting {name} to {value}.
        slots:
          name: requestBody.name
          value: requestBody.value
      - text: Update the global compliance rule {name} with value {value}.
        slots:
          name: requestBody.name
          value: requestBody.value
      method: generated
      generated: '2026-09-26'