Projects
Create projects and list or fetch project metadata over HTTP.
Projects isolate traces, benchmarks, prompts, and datasets. Automation often starts by creating or selecting a project, then using its project key in the X-Project-Key header for all other calls.
Base path: /api/v1/projects. See HTTP authentication.
List projects
GET /api/v1/projects
Returns JSON with the projects available to the authenticated organization. Use this to discover ids and keys when building admin tools.
Create project
POST /api/v1/projects
- Body: JSON including at least a name and optional description fields as supported by your workspace.
- Returns: JSON for the new project, including identifiers you will use in URLs and the project key for headers.
Creation is idempotent only if you enforce uniqueness on the client; the server validates names and keys according to product rules.
Get project
GET /api/v1/projects/{id}
- Path:
idis the project document id returned from list or create responses. - Returns: JSON metadata for the project (name, description, key, and related fields exposed by the API).
There are no public PUT or DELETE routes under /api/v1/projects in the current HTTP surface; manage lifecycle changes from the dashboard or contact support for bulk operations.