Analysis and findings¶

31 endpoints. Every path below is served by bevm-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	`bevm-backend`

curl

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	`bevm-backend`

curl

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	`bevm-backend`

curl

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	`bevm-backend`

curl

curl -X GET https://api.trilocore.ai/api/v1/bevm/asset-flow/health \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

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

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

Request body not published

This endpoint accepts a body, but no machine-readable schema for it is published yet, so none is shown. The example below is therefore incomplete — do not read it as "send no body".

curl

curl -X POST https://api.trilocore.ai/api/v1/bevm/asset-flow/routes \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST `/api/v1/bevm/contract-analyses`¶

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

Request body not published

This endpoint accepts a body, but no machine-readable schema for it is published yet, so none is shown. The example below is therefore incomplete — do not read it as "send no body".

curl

curl -X POST https://api.trilocore.ai/api/v1/bevm/contract-analyses \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

GET `/api/v1/bevm/differentials`¶

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

curl

curl -X GET https://api.trilocore.ai/api/v1/bevm/differentials \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST `/api/v1/bevm/differentials`¶

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

Request body not published

This endpoint accepts a body, but no machine-readable schema for it is published yet, so none is shown. The example below is therefore incomplete — do not read it as "send no body".

curl

curl -X POST https://api.trilocore.ai/api/v1/bevm/differentials \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST `/api/v1/bevm/diffs`¶

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

Request body not published

This endpoint accepts a body, but no machine-readable schema for it is published yet, so none is shown. The example below is therefore incomplete — do not read it as "send no body".

curl

curl -X POST https://api.trilocore.ai/api/v1/bevm/diffs \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

GET `/api/v1/bevm/findings/oracles`¶

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

curl

curl -X GET https://api.trilocore.ai/api/v1/bevm/findings/oracles \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

GET `/api/v1/bevm/findings/summary`¶

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

curl

curl -X GET https://api.trilocore.ai/api/v1/bevm/findings/summary \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST `/api/v1/bevm/gas-fuzz-traces`¶

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

Request body not published

This endpoint accepts a body, but no machine-readable schema for it is published yet, so none is shown. The example below is therefore incomplete — do not read it as "send no body".

curl

curl -X POST https://api.trilocore.ai/api/v1/bevm/gas-fuzz-traces \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST `/api/v1/bevm/introspections`¶

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

Request body

Field	Type	Required	Constraints
`capture_memory`	boolean	no	—
`capture_stack`	boolean	no	—
`data`	string	no	`maxLength` 1000000
`max_steps`	integer	no	—
`sender`	string	no	`maxLength` 66
`to`	string	no	`maxLength` 66
`tx_hash`	string	no	`maxLength` 66
`value`	string	no	`maxLength` 66

curl

curl -X POST https://api.trilocore.ai/api/v1/bevm/introspections \
  -H "Authorization: Bearer $TRILOCORE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"capture_memory": false, "capture_stack": false, "data": "…"}'

GET `/api/v1/bevm/jobs`¶

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

curl

curl -X GET https://api.trilocore.ai/api/v1/bevm/jobs \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

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	`bevm-backend`

Request body not published

This endpoint accepts a body, but no machine-readable schema for it is published yet, so none is shown. The example below is therefore incomplete — do not read it as "send no body".

curl

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	`bevm-backend`

Request body not published

This endpoint accepts a body, but no machine-readable schema for it is published yet, so none is shown. The example below is therefore incomplete — do not read it as "send no body".

curl

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	`bevm-backend`

Request body not published

This endpoint accepts a body, but no machine-readable schema for it is published yet, so none is shown. The example below is therefore incomplete — do not read it as "send no body".

curl

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

POST `/api/v1/bevm/oracle-manipulation-findings`¶

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

Request body not published

This endpoint accepts a body, but no machine-readable schema for it is published yet, so none is shown. The example below is therefore incomplete — do not read it as "send no body".

curl

curl -X POST https://api.trilocore.ai/api/v1/bevm/oracle-manipulation-findings \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST `/api/v1/bevm/oracle-manipulation-probes`¶

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

Request body not published

This endpoint accepts a body, but no machine-readable schema for it is published yet, so none is shown. The example below is therefore incomplete — do not read it as "send no body".

curl

curl -X POST https://api.trilocore.ai/api/v1/bevm/oracle-manipulation-probes \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST `/api/v1/bevm/scans`¶

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

Request body not published

This endpoint accepts a body, but no machine-readable schema for it is published yet, so none is shown. The example below is therefore incomplete — do not read it as "send no body".

curl

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

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

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

curl

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	`bevm-backend`

curl

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

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

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

curl

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	`bevm-backend`

Request body not published

This endpoint accepts a body, but no machine-readable schema for it is published yet, so none is shown. The example below is therefore incomplete — do not read it as "send no body".

curl

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	`bevm-backend`

Request body not published

This endpoint accepts a body, but no machine-readable schema for it is published yet, so none is shown. The example below is therefore incomplete — do not read it as "send no body".

curl

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

POST `/api/v1/bevm/share-inflation-probes`¶

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

Request body not published

This endpoint accepts a body, but no machine-readable schema for it is published yet, so none is shown. The example below is therefore incomplete — do not read it as "send no body".

curl

curl -X POST https://api.trilocore.ai/api/v1/bevm/share-inflation-probes \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST `/api/v1/bevm/storage-traces`¶

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

Request body

Field	Type	Required	Constraints
`capture_reads`	boolean	no	—
`data`	string	no	`maxLength` 1000000
`max_steps`	integer	no	—
`merge_graph`	boolean	no	—
`sender`	string	no	`maxLength` 66
`to`	string	yes	`maxLength` 66
`track_taint`	boolean	no	—
`value`	string	no	`maxLength` 66

curl

curl -X POST https://api.trilocore.ai/api/v1/bevm/storage-traces \
  -H "Authorization: Bearer $TRILOCORE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"to": "…"}'

POST `/api/v1/bevm/taint-traces`¶

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

Request body not published

This endpoint accepts a body, but no machine-readable schema for it is published yet, so none is shown. The example below is therefore incomplete — do not read it as "send no body".

curl

curl -X POST https://api.trilocore.ai/api/v1/bevm/taint-traces \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST `/api/v1/bevm/traces`¶

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

Request body not published

This endpoint accepts a body, but no machine-readable schema for it is published yet, so none is shown. The example below is therefore incomplete — do not read it as "send no body".

curl

curl -X POST https://api.trilocore.ai/api/v1/bevm/traces \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

GET `/api/v1/bevm/traces/{tx_hash}`¶

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

curl

curl -X GET https://api.trilocore.ai/api/v1/bevm/traces/{tx_hash} \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST `/api/v1/bevm/transient-analyses`¶

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

Request body not published

This endpoint accepts a body, but no machine-readable schema for it is published yet, so none is shown. The example below is therefore incomplete — do not read it as "send no body".

curl

curl -X POST https://api.trilocore.ai/api/v1/bevm/transient-analyses \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

Analysis and findings¶

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

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

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

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

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

POST /api/v1/bevm/contract-analyses¶

GET /api/v1/bevm/differentials¶

POST /api/v1/bevm/differentials¶

POST /api/v1/bevm/diffs¶

GET /api/v1/bevm/findings/oracles¶

GET /api/v1/bevm/findings/summary¶

POST /api/v1/bevm/gas-fuzz-traces¶

POST /api/v1/bevm/introspections¶

GET /api/v1/bevm/jobs¶

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

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

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

POST /api/v1/bevm/oracle-manipulation-findings¶

POST /api/v1/bevm/oracle-manipulation-probes¶

POST /api/v1/bevm/scans¶

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

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

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

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

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

POST /api/v1/bevm/share-inflation-probes¶

POST /api/v1/bevm/storage-traces¶

POST /api/v1/bevm/taint-traces¶

POST /api/v1/bevm/traces¶

GET /api/v1/bevm/traces/{tx_hash}¶

POST /api/v1/bevm/transient-analyses¶

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

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

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

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

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

POST `/api/v1/bevm/contract-analyses`¶

GET `/api/v1/bevm/differentials`¶

POST `/api/v1/bevm/differentials`¶

POST `/api/v1/bevm/diffs`¶

GET `/api/v1/bevm/findings/oracles`¶

GET `/api/v1/bevm/findings/summary`¶

POST `/api/v1/bevm/gas-fuzz-traces`¶

POST `/api/v1/bevm/introspections`¶

GET `/api/v1/bevm/jobs`¶

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

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

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

POST `/api/v1/bevm/oracle-manipulation-findings`¶

POST `/api/v1/bevm/oracle-manipulation-probes`¶

POST `/api/v1/bevm/scans`¶

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

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

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

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

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

POST `/api/v1/bevm/share-inflation-probes`¶

POST `/api/v1/bevm/storage-traces`¶

POST `/api/v1/bevm/taint-traces`¶

POST `/api/v1/bevm/traces`¶

GET `/api/v1/bevm/traces/{tx_hash}`¶

POST `/api/v1/bevm/transient-analyses`¶