API

Authentication

Create a key under Settings, API keys. It is shown once and stored hashed; up to ten keys can be active per organisation. Send it as a bearer token. Every endpoint is scoped to the organisation the key belongs to; no request may name another.

curl -H "Authorization: Bearer secai_..." https://secai.techsteps.ae/api/v1/agent/fleet/status

Endpoints

GET /api/v1/agent/fleet/status

Servers online and offline, open findings, latest audits: one summary.

GET /api/v1/agent/servers

Your servers with their live status.

GET /api/v1/agent/findings

Findings, filterable by severity and status; limit is capped.

GET /api/v1/agent/findings/{id}

One finding.

GET /api/v1/agent/indicators/recent

Recent indicators: web-shell hits, blocked addresses, vulnerabilities.

GET /api/v1/agent/vulnerabilities

Package vulnerabilities, filterable by severity; include_resolved=true to see closed ones.

GET /api/v1/agent/audit/latest

The most recent completed audit for the organisation, or for one server with ?server_id=.

Scope

Read-only. There is no endpoint that changes a server, approves an action or alters a setting; those stay in the dashboard, behind a signed-in person.