What the Assistant can do
- explain your current dashboard or endpoint status
- import OpenAPI specs
- create endpoint files from curl requests or natural language
- edit provider branding
- edit endpoint names, descriptions, tags, schemas, prices, and active flags
- configure API-level pricing and credit packs
- request upstream auth secrets through secure input fields
- validate workspace files
- publish active drafts when allowed
- explain distribution URLs, Bazaar status, and runtime failures
- route you to Endpoints, Files, or Payments
Safety model
Read-only actions can run immediately. Mutating actions require explicit approval before they change files or runtime state. Examples of mutating actions:- write or patch a file
- delete a file
- activate or deactivate endpoints
- change pricing or credit packs
- change distribution settings
- publish workspace changes
- affect payment or payout behavior
Secrets
The Assistant must never receive secret values as normal chat text. When an upstream bearer token or API key is needed, it asks for a secure inline input. Secret values are encrypted and stored separately. Workspace files store only asecretRef.