W3.io: YAML actions for autonomous finance workflows

W3.io is a workflow layer for money that has to move itself. You pick partner services (they call them ingredients), sequence them into a recipe, and ship that as a solution in someone else’s stack.

The public builder surface is GitHub-style YAML. Each step is a published action. Under that, Rust crates compile to WASM so the same primitive behaves on the W3 runtime and on a GitHub Actions runner.

Three layers

Docs at learn.w3.io use this vocabulary. A recipe starts with a trigger (chain event, clock, or API), keeps a variable pool, and runs steps with retries.

Call a step

Circle CCTP is a typical money step: attestation, burn, mint. Sandbox first. Wallet and compliance commands need a Circle API key.

- name: Check attestation
  uses: w3-io/w3-circle-action@v0
  with:
    command: get-attestation
    sandbox: "true"
    message-hash: "0xabcdef..."

Built-in primitives live in w3-io/w3-actions. Pin w3-io/w3-actions/http@v0, json@v0, encode@v0, crypto@v0, emit@v0, or cloud@v0 for S3-compatible W3.cloud storage.

Partner repos follow the same shape: Pyth prices, Privy wallets, Chainalysis screening, Stripe and PayPal, Hyperbolic GPU, Space and Time SQL, LayerZero messaging, Crossmint. Start from github.com/w3-io or the template w3-action-template.

What to do next

1. Read How it Works and the cookbook on identity, compliance, and RWAs.
2. Clone a partner action, pin @v0, run sandbox commands before mainnet keys.
3. Demo and sales sit on w3.io. The site headline is autonomous finance. The code is the recipes.

People and links