Skip to main content
A system is a hardware project you’re building, operating, or analyzing. All metagraph data, jobs, issues, test runs, and sessions are scoped to a system. See Populating the System Metagraph for a workflow guide.

Endpoints


Create a system

POST /systems Request body: Example request:
Response fields: Example response:

List systems

GET /systems Query parameters: Example request:
Returns {"items": [...], "count": N} where each item is a system object with the same fields as the create response.

Get a system

GET /systems/{system_id} Path parameters: Example request:
Returns a single system object with the same fields as the create response.

Update a system

PUT /systems/{system_id} All fields are optional. Only provided fields are updated. Example request:
Returns the updated system object with the same fields as the create response.

Delete a system

DELETE /systems/{system_id} Soft-deletes a system. The system remains in the database with is_deleted: true. Example request:
Response fields: Example response:

Upload a reference document

POST /systems/upload_document Attaches PDFs, specs, schematics, or other documents to a system. Uploaded files are embedded and made available to Atlas during reasoning and metagraph updates. Query parameters: Form fields (multipart/form-data): Example request:
Response fields: Each item in results: Example response:

Search system memories

GET /system-memories Searches entity memories across all entities. Returns matching memory entries with their associated entity and system context. Query parameters: Example request:
Response fields: Each item in items: Example response: