Execution¶

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

POST `/api/v1/bevm/execution-path-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

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

GET `/api/v1/bevm/executions`¶

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/executions \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

GET `/api/v1/bevm/executions/{execution_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/executions/{execution_id} \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST `/api/v1/bevm/executions/{execution_id}/analyses`¶

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
`force`	boolean	no	—
`mode`	string	no	—

curl

curl -X POST https://api.trilocore.ai/api/v1/bevm/executions/{execution_id}/analyses \
  -H "Authorization: Bearer $TRILOCORE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"force": false, "mode": "…"}'

GET `/api/v1/bevm/executions/{execution_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/executions/{execution_id}/events \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

GET `/api/v1/bevm/executions/{execution_id}/traces`¶

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/executions/{execution_id}/traces \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

GET `/api/v1/bevm/operations`¶

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/operations \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

GET `/api/v1/bevm/operations/{op_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/operations/{op_id} \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

GET `/api/v1/bevm/operations/{op_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/operations/{op_id}/events \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST `/api/v1/bevm/operations/{op_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/operations/{op_id}:cancel \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST `/api/v1/bevm/operations/{op_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/operations/{op_id}:pause \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST `/api/v1/bevm/operations/{op_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/operations/{op_id}:resume \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST `/api/v1/bevm/stateless/calls`¶

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/stateless/calls \
  -H "Authorization: Bearer $TRILOCORE_API_KEY"

POST `/api/v1/bevm/stateless/deployments`¶

Property	Value
Authentication	`Authorization: Bearer` (`jns_` key or SSO session)
Idempotency-Key	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/stateless/deployments \
  -H "Authorization: Bearer $TRILOCORE_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"

POST `/api/v1/bevm/transactions`¶

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

Request body

Field	Type	Required	Constraints
`args`	array	no	—
`fundings`	array	no	—
`gas_limit`	integer \| null	no	`maximum` 1000000000, `minimum` 21000
`gas_price`	integer \| null	no	`maximum` 1000000000000000000000000000000, `minimum` 0
`overrides`	object	no	—
`persist`	boolean	no	—
`raw_calldata`	string \| null	no	`maxLength` 1000000
`selector`	string	no	`maxLength` 512
`sender`	string	no	`maxLength` 66
`signature`	string \| null	no	`maxLength` 512
`to`	string	yes	`maxLength` 66
`value_wei`	integer \| string \| number	no	—

curl

curl -X POST https://api.trilocore.ai/api/v1/bevm/transactions \
  -H "Authorization: Bearer $TRILOCORE_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{"to": "…"}'

POST `/api/v1/bevm/transactions: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
`network`	string \| null	no	—
`rpc_url`	string	no	—
`tx_hash`	string	yes	—

curl

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

Execution¶

POST /api/v1/bevm/execution-path-recoveries¶

GET /api/v1/bevm/executions¶

GET /api/v1/bevm/executions/{execution_id}¶

POST /api/v1/bevm/executions/{execution_id}/analyses¶

GET /api/v1/bevm/executions/{execution_id}/events¶

GET /api/v1/bevm/executions/{execution_id}/traces¶

GET /api/v1/bevm/operations¶

GET /api/v1/bevm/operations/{op_id}¶

GET /api/v1/bevm/operations/{op_id}/events¶

POST /api/v1/bevm/operations/{op_id}:cancel¶

POST /api/v1/bevm/operations/{op_id}:pause¶

POST /api/v1/bevm/operations/{op_id}:resume¶

POST /api/v1/bevm/stateless/calls¶

POST /api/v1/bevm/stateless/deployments¶

POST /api/v1/bevm/transactions¶

POST /api/v1/bevm/transactions:resolve¶

POST `/api/v1/bevm/execution-path-recoveries`¶

GET `/api/v1/bevm/executions`¶

GET `/api/v1/bevm/executions/{execution_id}`¶

POST `/api/v1/bevm/executions/{execution_id}/analyses`¶

GET `/api/v1/bevm/executions/{execution_id}/events`¶

GET `/api/v1/bevm/executions/{execution_id}/traces`¶

GET `/api/v1/bevm/operations`¶

GET `/api/v1/bevm/operations/{op_id}`¶

GET `/api/v1/bevm/operations/{op_id}/events`¶

POST `/api/v1/bevm/operations/{op_id}:cancel`¶

POST `/api/v1/bevm/operations/{op_id}:pause`¶

POST `/api/v1/bevm/operations/{op_id}:resume`¶

POST `/api/v1/bevm/stateless/calls`¶

POST `/api/v1/bevm/stateless/deployments`¶

POST `/api/v1/bevm/transactions`¶

POST `/api/v1/bevm/transactions:resolve`¶