Where an endpoint accepts agent_uuid, the agent_uuidmust belong to the authenticated user (API key owner). Otherwise, the request fails (e.g., “Invalid agent UUID” / “Agent does not exist”).
Agent Check-in
Endpoint: /api/traceix/agent/checkin Request type: POST Content type: JSON
Headers:
X-Api-Key: YOUR_API_KEY
content-type: application/json
Body:
agent_uuid: string
Example request
Expected outputs
Success:
Failure (invalid agent UUID):
Get Agent Metadata
Endpoint: /api/traceix/agent/metadata Request type: POST Content type: JSON
Headers:
X-Api-Key: YOUR_API_KEY
content-type: application/json
Body:
agent_uuid: string
Example request
Expected outputs
Success:
Failure (not owned / not accessible / doesn’t exist):
Run Agent
Endpoint: /api/traceix/agent/run Request type: POST Content type: multipart/form-data
Headers:
X-Api-Key: YOUR_API_KEY
X-Agent-Id: AGENT_UUID
Body:
file: the file to submit (multipart form)
NOTE: This endpoint queues an analysis job and returns a uuid you will poll using /api/traceix/agent/status.
Example request
Expected outputs
Success (queued):
Failure (agent does not exist / not accessible):
Check Agent Run Status
Endpoint: /api/traceix/agent/status Request type: POST Content type: JSON
Headers:
X-Api-Key: YOUR_API_KEY
content-type: application/json
Body:
uuid: string (the job UUID returned from /api/traceix/agent/run)
agent_uuid: string (the agent UUID used to launch the job)
NOTE: You must provide bothuuid and agent_uuid.
Example request
Expected outputs
Success can return either a pending status or completed results.
Success (pending):
Success (completed example):
Failure example:
Submit Agent Alert
Endpoint: /api/traceix/agent/alert Request type: POST Content type: JSON