Agent workflows

Agent integration

Use the Purveyors CLI as a stable interface for AI agents, coding assistants, and external automation.

The CLI is the preferred documented automation surface for most non-visual workflows. It gives agents stable command names, explicit auth requirements, predictable output modes, and a machine-readable manifest when needed.

The Purveyors web app and CLI both consume Parchment API contracts, keeping browser, terminal, and agent behavior aligned without runtime package coupling.

How the web app and CLI stay aligned

  • The app uses a session-authenticated @purveyors/sdk client to forward Parchment-owned Cherry Runtime streams without buffering. The CLI remains a separate Parchment API client and terminal surface; neither runtime imports the other.
  • All Coffee-app product data and AI orchestration now cross Parchment contracts; Supabase is limited to browser identity and session plumbing.
  • Cherry read and proposal tools execute inside Parchment. Writes stay user-confirmed through proposal cards and constrained execution routes.
  • This API-first architecture keeps terminal, browser, and agent workflows aligned on the same contracts without runtime package coupling.
Agent bootstrap sequence
purvey auth login --headless
purvey manifest --pretty
purvey catalog search --origin "Ethiopia" --json

Related links