Skip to main content
Files is the direct configuration view for a builder workspace. It shows the same configuration the Assistant edits for you.

​
Workspace layout

provider.yaml
apis/<apiSlug>/api.yaml
apis/<apiSlug>/auth.yaml
apis/<apiSlug>/pricing.yaml
apis/<apiSlug>/distribution.yaml
apis/<apiSlug>/endpoints/<endpointSlug>.yaml
apis/<apiSlug>/tests/<endpointSlug>.json
One workspace can contain multiple APIs. Each API folder has its own base URL, auth mode, pricing defaults, distribution defaults, endpoint files, and test samples.

​
Provider file

provider.yaml controls builder identity and branding:
  • provider name
  • slug
  • description
  • website
  • logo URL
  • support email
  • optional domain
This provider profile is used in public listings, provider pages, MCP details, and AgentCards where appropriate.

​
API files

api.yaml describes the upstream API:
  • API name and slug
  • base URL
  • OpenAPI source URL or import metadata
  • selected server
auth.yaml stores only the auth mode and secretRef. It must never contain the actual token or API key value. pricing.yaml stores shared pricing and credit-pack programs for an API. Endpoint YAML files can also set a per-call priceUsd. distribution.yaml stores default distribution preferences for endpoints in that API.

​
Endpoint files

Each endpoint YAML file describes one payable listing:
  • name and slug
  • HTTP method and path
  • description and tags
  • input schema
  • MCP name and description
  • per-call price
  • active: true or active: false
Set active: true only when you want the endpoint to be eligible for publication.

​
Test files

Test JSON files store sample inputs. They help validation and give the Assistant a concrete payload when it explains or tests an endpoint.

​
Editing safely

You can edit files directly, but the recommended path is to ask the Assistant. The Assistant can update YAML, validate after changes, request secure secrets, and explain the impact before publication. Secrets must be entered through secure input fields. Secret values are encrypted and are not written into workspace files, chat history, tool traces, or logs.