Chain API

Loading version info...

Execute

Run a connector on chain, or simulate one you created on this server

Execute runs a connector registered on chain with the chain's runner. Simulate runs a connector you created on this server on its local EVM.

Click any node in the dependency graph (including scalar dots) to edit running instance values.

Only explicitly saved RI values are sent in execute request.

Blue border means static RI is present. "Static RI (locked)" nodes block popup edits; "Fallback RI (overrideable)" nodes can still be edited.

Green glow means dynamic RI is set in popup.

Dotted circles are scalar outputs. Amber boxes with dashed links are connectors introduced by bindings.

-
Waiting...

                            

Connectors

Interact with existing connectors or create a new connector

Static RI uses DFS connector-tree positions: 0 is root, then composites/bindings descendants in traversal order.

Loading static RI positions...

...
-
Waiting...

Transformations

Interact with existing transformations or create a new transformation

function run(uint32 x, uint32 [] calldata args) view external returns (uint32){
}
...
-
Waiting...

Conditions

Interact with existing conditions or create a new condition

function check(int32 [] calldata args) view external returns (bool){
}
...
-
Waiting...

Publish

Register one of your entities on chain. Your wallet sends the transaction, or signs it for the server to relay; either way your account pays for it.

Preparation and sending

Prepare builds an unsigned transaction without spending gas. Send with wallet submits it; publication happens when it is successfully mined.

For wallets that can sign a transaction without sending it. The server checks it and broadcasts it through its own node, so the wallet needs no network access; your account still pays. MetaMask cannot sign without sending: leave this off.

A connector's transformations, conditions and composites must be published first.

Confirmation

Confirm checks the transaction receipt to verify that it successfully published this entity for your account. It sends no transaction and spends no gas, so it is safe to repeat. After sending, pending transactions are checked automatically every five seconds for about ten minutes.

Log in, then prepare the publication of an entity you created.

A successful confirmation means the publication was mined. The server's registry listing updates after the block is final, even if you never press Confirm.

After refreshing, select the same entity and Prepare again. If it is already published, its address is shown. To check the original transaction's receipt, paste its hash and press Confirm; do not send it again.

-
Waiting...

Explore

Browse account resources and format hash results

Account Overview

Gather information about an account

Cursor page 1

Formats

Fetch data for a format hash

Cursor page 1

Events Feed

Live stream of recent events via SSE

Disconnected
seq: —

Recent Events

Waiting for connection...

Event History

Static browse via limit, before cursor, and event type

History Events

Waiting...