Skip to content

Bytecode and decoding

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

POST /api/v1/bevm/calldata-decodings

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
data_hex string yes maxLength 1000000
signature string | null no maxLength 512
curl -X POST https://api.trilocore.ai/api/v1/bevm/calldata-decodings \
  -H "Authorization: Bearer $TRILOCORE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data_hex": "…"}'

POST /api/v1/bevm/cfg-recoveries

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 -X POST https://api.trilocore.ai/api/v1/bevm/cfg-recoveries \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST /api/v1/bevm/decompilations

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 -X POST https://api.trilocore.ai/api/v1/bevm/decompilations \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST /api/v1/bevm/disassemblies

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 -X POST https://api.trilocore.ai/api/v1/bevm/disassemblies \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST /api/v1/bevm/facets:resolve

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
address string | null no maxLength 66
curl -X POST https://api.trilocore.ai/api/v1/bevm/facets:resolve \
  -H "Authorization: Bearer $TRILOCORE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"address": "…"}'

POST /api/v1/bevm/logs:query

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
address string | null no maxLength 66
addresses array no
fromBlock string | integer | null no
limit integer no maximum 5000, minimum 1
toBlock string | integer | null no
topics array no
curl -X POST https://api.trilocore.ai/api/v1/bevm/logs:query \
  -H "Authorization: Bearer $TRILOCORE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"address": "…", "addresses": [], "fromBlock": "…"}'

POST /api/v1/bevm/revert-decodings

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
data_hex string yes maxLength 1000000
curl -X POST https://api.trilocore.ai/api/v1/bevm/revert-decodings \
  -H "Authorization: Bearer $TRILOCORE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data_hex": "…"}'

POST /api/v1/bevm/selector-recoveries

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 -X POST https://api.trilocore.ai/api/v1/bevm/selector-recoveries \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"