Skip to main content
The API surface is for programmatic access to BRIK64 workflows such as project metadata, PCD candidates, topology summaries, evidence references and release metadata. For the current public workflow, local CLI output is the primary integration boundary. API-backed platform features should be documented only when the target deployment provides endpoint, authentication and evidence behavior.

​
Integration Model

  • Use the CLI for local generation, validation, compile, test and update checks.
  • Use API integrations for hosted review and collaboration only when enabled for the workspace.
  • Prefer manifests, hashes, PCD candidates, topology summaries and redacted evidence over raw source upload.
  • Record endpoint, request scope and artifact returned.

​
Agent Use

Agents should prefer deterministic local commands first. When using an API, they must record: 
Endpoint:
Authentication mode:
Input artifact:
Returned artifact:
Files changed:
Evidence status:

​
Data Handling

Do not assume an API call is private, retained, deleted or billable in a specific way unless the workspace documentation states that behavior. When in doubt, keep source local and use CLI-generated artifacts.