Skip to content

Analysis and findings

15 endpoints. Every path below is served by trilocore-backend behind the gateway at https://api.trilocore.ai.

DELETE /api/v1/bevm/analysis-jobs/{job_id}

Property Value
Authentication Authorization: Bearer (jns_ key or SSO session)
Idempotency-Key not required
Success 200
Upstream trilocore-backend 
curl -X DELETE https://api.trilocore.ai/api/v1/bevm/analysis-jobs/{job_id} \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

GET /api/v1/bevm/analysis-jobs/{job_id}

Property Value
Authentication Authorization: Bearer (jns_ key or SSO session)
Idempotency-Key not required
Success 200
Upstream trilocore-backend 
curl -X GET https://api.trilocore.ai/api/v1/bevm/analysis-jobs/{job_id} \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

GET /api/v1/bevm/analysis-jobs/{job_id}/events

Property Value
Authentication Authorization: Bearer (jns_ key or SSO session)
Idempotency-Key not required
Success 200
Upstream trilocore-backend

Query parameters

Parameter Type Required Constraints Description
after integer no — — 
curl -X GET https://api.trilocore.ai/api/v1/bevm/analysis-jobs/{job_id}/events \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

GET /api/v1/bevm/asset-flow/health

Property Value
Authentication Authorization: Bearer (jns_ key or SSO session)
Idempotency-Key not required
Success 200
Upstream trilocore-backend 
curl -X GET https://api.trilocore.ai/api/v1/bevm/asset-flow/health \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

▶ Run this example in the sandbox

POST /api/v1/bevm/asset-flow/routes

Property Value
Authentication Authorization: Bearer (jns_ key or SSO session)
Idempotency-Key not required
Success 200
Upstream trilocore-backend

Request body

Field Type Required Constraints
backend string no —
budget one of no —
from_scanner boolean no —
numeraire string yes —
pools array of ToolsPoolBody no —
prices one of no —
scanner_results one of no — 
curl -X POST https://api.trilocore.ai/api/v1/bevm/asset-flow/routes \
  -H "Authorization: Bearer $TRILOCORE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"numeraire": "…"}'

GET /api/v1/bevm/jobs

Property Value
Authentication Authorization: Bearer (jns_ key or SSO session)
Idempotency-Key not required
Success 200
Upstream trilocore-backend 
curl -X GET https://api.trilocore.ai/api/v1/bevm/jobs \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

▶ Run this example in the sandbox

POST /api/v1/bevm/jobs/{job_id}:cancel

Property Value
Authentication Authorization: Bearer (jns_ key or SSO session)
Idempotency-Key not required
Success 200
Upstream trilocore-backend

This operation takes no request body.

curl -X POST https://api.trilocore.ai/api/v1/bevm/jobs/{job_id}:cancel \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST /api/v1/bevm/jobs/{job_id}:pause

Property Value
Authentication Authorization: Bearer (jns_ key or SSO session)
Idempotency-Key not required
Success 200
Upstream trilocore-backend

This operation takes no request body.

curl -X POST https://api.trilocore.ai/api/v1/bevm/jobs/{job_id}:pause \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST /api/v1/bevm/jobs/{job_id}:resume

Property Value
Authentication Authorization: Bearer (jns_ key or SSO session)
Idempotency-Key not required
Success 200
Upstream trilocore-backend

This operation takes no request body.

curl -X POST https://api.trilocore.ai/api/v1/bevm/jobs/{job_id}:resume \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST /api/v1/bevm/scans

The resource id is a per-caller slot id, derived from the caller and their session tag — not a per-instance id. It is reused: deleting and recreating returns the same id, and so does acting on a different target. current is accepted in its place. Another caller's id answers 404.

Property Value
Authentication Authorization: Bearer (jns_ key or SSO session)
Idempotency-Key not required
Success 201 + Location
Upstream trilocore-backend

Query parameters

Parameter Type Required Constraints Description
mode string no one of active, passive —

Request body

Field Type Required Constraints
stop_on_first_finding boolean no — 
curl -X POST https://api.trilocore.ai/api/v1/bevm/scans \
  -H "Authorization: Bearer $TRILOCORE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"stop_on_first_finding": false}'

DELETE /api/v1/bevm/scans/{uid}

Property Value
Authentication Authorization: Bearer (jns_ key or SSO session)
Idempotency-Key not required
Success 200
Upstream trilocore-backend 
curl -X DELETE https://api.trilocore.ai/api/v1/bevm/scans/{uid} \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

GET /api/v1/bevm/scans/{uid}

Property Value
Authentication Authorization: Bearer (jns_ key or SSO session)
Idempotency-Key not required
Success 200
Upstream trilocore-backend 
curl -X GET https://api.trilocore.ai/api/v1/bevm/scans/{uid} \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

▶ Run this example in the sandbox

GET /api/v1/bevm/scans/{uid}/findings

Property Value
Authentication Authorization: Bearer (jns_ key or SSO session)
Idempotency-Key not required
Success 200
Upstream trilocore-backend 
curl -X GET https://api.trilocore.ai/api/v1/bevm/scans/{uid}/findings \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST /api/v1/bevm/scans/{uid}:advance

Property Value
Authentication Authorization: Bearer (jns_ key or SSO session)
Idempotency-Key not required
Success 200
Upstream trilocore-backend

This operation takes no request body.

curl -X POST https://api.trilocore.ai/api/v1/bevm/scans/{uid}:advance \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST /api/v1/bevm/scans/{uid}:stop

Property Value
Authentication Authorization: Bearer (jns_ key or SSO session)
Idempotency-Key not required
Success 200
Upstream trilocore-backend

This operation takes no request body.

curl -X POST https://api.trilocore.ai/api/v1/bevm/scans/{uid}:stop \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"