Parallel · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Parallel Memory API

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

What the actions change

x-apievangelist-phrasing

Targets 4

$.info
$.paths['/v1beta/memory/clear'].post
$.paths['/v1beta/memory/evict'].post
$.paths['/v1beta/memory/retrieve'].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 Parallel Memory API
  version: 1.0.0
extends: openapi/parallel-memory-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['/v1beta/memory/clear'].post
  update:
    x-apievangelist-phrasing:
      intent: Clear all entries from a memory scope
      effect: destructive
      questions:
      - How do I wipe everything stored in my Parallel memory?
      - Does clearing memory also delete my underlying tasks, monitors or FindAll runs?
      - Can I clear a shared memory scope rather than my personal memory?
      instructions:
      - text: Clear all entries from my personal memory.
      - text: Wipe every entry in memory scope {memory_scope_key}.
        slots:
          memory_scope_key: requestBody.memory_scope_key
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v1beta/memory/evict'].post
  update:
    x-apievangelist-phrasing:
      intent: Remove one run or monitor from memory
      effect: destructive
      questions:
      - Can I remove a single task run from memory without deleting the run itself?
      - What kinds of sources can be evicted from memory individually?
      - Is it possible to drop just one monitor's results out of a memory scope?
      instructions:
      - text: Evict the {kind} with ID {id} from my memory.
        slots:
          kind: requestBody.kind
          id: requestBody.id
      - text: Remove {kind} {id} from memory scope {memory_scope_key}.
        slots:
          kind: requestBody.kind
          id: requestBody.id
          memory_scope_key: requestBody.memory_scope_key
      method: generated
      generated: '2026-10-01'
- target: $.paths['/v1beta/memory/retrieve'].post
  update:
    x-apievangelist-phrasing:
      intent: Look up relevant or recent memories
      effect: read
      questions:
      - How can I find past research runs in memory that relate to a topic?
      - What comes back from memory if I don't provide a query?
      - Can I filter memories to only FindAll runs completed after a certain date?
      instructions:
      - text: Find memories related to {query}.
        slots:
          query: requestBody.query
      - text: Show my {limit} most recent memories.
        slots:
          limit: requestBody.limit
      - text: Retrieve {kind} memories completed since {since}.
        slots:
          kind: requestBody.kind
          since: requestBody.since
      method: generated
      generated: '2026-10-01'