Sigil documentation

Build something agents can use.

Connect to Sigil, understand its execution model, and turn agent work into verifiable records. Start with one read-only request.

Your first request

No wallet or signing key is needed to ask a public node which chain it serves. The response reports chain_id, version, and protocol_version.

curl --fail-with-body --show-error --silent --max-time 15 'https://rpc.sigil.ml/rpc' \
  -H 'content-type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"sigil_getNodeInfo","params":{}}'

Choose your starting point

Use the reference that matches the task in front of you.

ItemDetails
Connect a clientCheck network identity, activation, JSON-RPC errors, and response shapes.
Understand the protocolRead typed execution, identity, lineage, consensus, and verification boundaries.
Operate a nodeInspect synchronization, validator state, and activation before making changes.

From a useful action to a durable record

Contracts, evidence anchoring, artifact storage, compute, and labor are connected building blocks. Read the availability and policy boundaries for each capability before designing a transaction flow.

On this page