Context.dev · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Context Utility API

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

What the actions change

x-apievangelist-phrasing

Targets 4

$.info
$.paths['/brand/prefetch'].post
$.paths['/brand/prefetch-by-email'].post
$.paths['/utility/prefetch'].post

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 Context Utility API
  version: 1.0.0
extends: openapi/contextdev-utility-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-10-02'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 3
- target: $.paths['/brand/prefetch'].post
  update:
    x-apievangelist-phrasing:
      intent: Warm up brand data for a domain ahead of time
      effect: write
      questions:
      - Can I make brand lookups for a domain faster by prefetching them before I need them?
      - What's the dedicated endpoint for queuing a single domain for brand prefetch?
      instructions:
      - text: Prefetch brand data for the domain {domain} so the next lookup is fast.
        slots:
          domain: requestBody.domain
      - text: Queue {domain} for brand warm-up before the user opens their dashboard.
        slots:
          domain: requestBody.domain
      method: generated
      generated: '2026-10-02'
- target: $.paths['/brand/prefetch-by-email'].post
  update:
    x-apievangelist-phrasing:
      intent: Warm up brand data from a signup's email
      effect: write
      questions:
      - Can I prefetch a company's brand data from a new user's work email at signup?
      - Will prefetching by email reject free addresses like gmail.com?
      instructions:
      - text: Prefetch the brand for the company behind email {email}.
        slots:
          email: requestBody.email
      - text: Warm up brand data from the work email {email} of a new signup.
        slots:
          email: requestBody.email
      method: generated
      generated: '2026-10-02'
- target: $.paths['/utility/prefetch'].post
  update:
    x-apievangelist-phrasing:
      intent: Queue a prefetch by type and identifier
      effect: write
      questions:
      - Is there a general utility prefetch that takes a type and a domain-or-email identifier?
      - Which prefetch types does the utility prefetch endpoint support today?
      instructions:
      - text: Use the utility prefetch to queue a {type} prefetch for identifier {identifier}.
        slots:
          type: requestBody.type
          identifier: requestBody.identifier
      - text: Send a generic {type} prefetch with the identifier object {identifier}.
        slots:
          type: requestBody.type
          identifier: requestBody.identifier
      method: generated
      generated: '2026-10-02'