IOTEX DEVELOPERS

Build for real machines,with other builders.

Contracts on an EVM chain, identity for devices, agents that use real-world data.
Pick what you’re building and start from an official guide.

Start building Read the docs ↗

What are you building?

Pick an outcome. Each path says what you’ll end up with and which guide gets you there.

Tutorial
Integration docs
Concept

01 · QuickSilver

Build an AI agent

A published agent that answers questions by calling your API.

Tutorial · 4 steps in the docs

Create your first agent ↗Or run it from source ↓

02 · Trio

Make a machine decision

A model reads machine state and proposes an operation for your code to check.

Concept · no public API guide

How Trio fits ↓

03 · ioID

Give a machine an identity

Each device gets a globally unique ID, paired with its own wallet.

Integration docs · 3 steps

Read the integration ↗Firmware or cloud? ↓

04 · IoTeX L1

Deploy a smart contract

A MessageBoard contract on testnet, then a client that posts a message to it.

Tutorial · deploy, then a client

Start the tutorial ↗Preview the code ↓

TESTNET FIRST?

Build with IoTeX

Six building blocks. Pick one to see what it solves, what you get and how to start today.

Self-serve
Overview
Talk to the team

SELF-SERVE · EVM CHAIN

Point your EVM tools at IoTeX

Deploy and call contracts. Hardhat, MetaMask and other EVM tools connect over standard RPC.

Network details · Testnet

Chain ID4690
RPChttps://babel-api.testnet.iotex.io
CurrencyIOTX

WHAT YOU GET

A deployed contract address you can open in the testnet explorer.
The same tools and workflow on mainnet when you’re ready.

Deploy tutorial ↗Get test IOTX ↗

Source: docs.iotex.io

Build for a use case

Four kinds of real-world system, and which building blocks they combine.

01 · REAL-WORLD AI AGENTS

An assistant that answers from live sources

Your API and QuickSilver’s data tools behind one chat endpoint.

QuestionQuickSilverYour API, data toolsAnswer

Create your first agent ↗

02 · ROBOTICS & EDGE

Machines that propose, code that decides

A model turns what a machine senses into a proposed operation.

SenseTrio proposesYour policy checksMachine acts or holds↺ then back to Sense

What to prepare ↑

03 · DEPIN & MACHINE DATA

Devices others can verify

Give each device an identity, then make its data usable by others.

Your deviceioID + walletYour project sends dataApps and agents read it

Integrating ioID ↗

04 · ON-CHAIN MESSAGES & COORDINATION

Machines that coordinate through events

One client posts to a contract. Others read its events instead of calling it directly.

MACHINE AYour client↓postMessage tx▶IOTEX L1MessageBoard↓MessagePosted event▶MACHINE BReads events

Deploy a simple contract ↗

Learn by building

Contracts, agents and device integrations from the official tutorials and repos. Open one and build from there.

IOTEX L1 · TUTORIAL

Deploy and talk to a contract

A MessageBoard contract that emits an event for each message, then a small client that posts one and prints the receipt.

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.0;

contract MessageBoard {
    event MessagePosted(address sender, string message);

    function postMessage(string calldata message) external {
        emit MessagePosted(msg.sender, message);
    }
}

Step 2 of “Deploy a simple contract” · docs.iotex.io

Deploy: Solidity · Hardhat (toolbox, ethers) · MetaMask
Client: Node.js · Web3.js — posts, prints the receipt
Needs: Node.js + npm · MetaMask on testnet · test IOTX

Deploy tutorial ↗

Client tutorial ↗

QUICKSILVER · SOURCE

Run the demo agent locally

The example agent from the open-source framework, on your own machine.

TypeScript
bun
Node.js 22
LLM key

example/demo_agent.tsSource ↗
src/toolsSource ↗

README ↗

QUICKSILVER · SOURCE · COMMANDS

Run the demo agent locally

terminal · from the README

git clone https://github.com/iotexproject/quicksilver.git
cd quicksilver
bun i
cp .env.template .env
bun run example/demo_agent.ts

BEFORE YOU RUN IT

Needs: Node.js 22 and bun. Docker is optional.
Keys: Put your LLM and data-tool API keys in .env before the last step.

README ↗example/demo_agent.ts ↗

QUICKSILVER · API

Call a published agent

OpenAI-compatible chat completions. Requires a QuickSilver API key.

HTTP
Python
JavaScript

POST /v1/chat/completionsHTTP docs ↗
SDK integrationsDocs ↗

Open the portal ↗

IOID · TWO TUTORIALS

Register a device on-chain

From the device itself, or from your cloud when the firmware can’t change.

ESP32
ioID-SDK
Hardhat
ioctl

In the firmware · ESP32 + ESP-IDFTutorial ↗
In your cloud · proxy contract, Node.jsTutorial ↗

Firmware source ↗Cloud example ↗

Docs, APIs & tools

The values you copy most, then the official references, grouped four ways.

All documentation ↗

Network values

Switches all four values below.

EVM chain ID · testnet4690

RPC · HTTP · testnethttps://babel-api.testnet.iotex.io

RPC · WSS · testnetwss://babel-api.testnet.iotex.io/ws

CurrencyIOTX

Get test IOTX ↗Add to MetaMask ↗All RPC endpoints, incl. archive ↗

Source: docs.iotex.io · RPC endpoints

APIs & SDKs

Python
JavaScript
HTTP
CLI
MCP

QuickSilver APIReference ↗
ioID API overviewReference ↗
iotex-antenna · JS SDKRepo ↗

Contracts & RPC

Deploy a simple contractTutorial ↗
Build a clientTutorial ↗
RPC endpointsReference ↗
Calling any RPC methodDocs ↗

Identity & Data

Integrating ioIDDocs ↗
ioID step-by-stepTutorial ↗
RealmsOverview ↗

Nodes & Upgrades

Set up an RPC nodeDocs ↗
Node manual (bootstrap)Repo ↗
iotex-core releasesGitHub ↗
Improvement proposalsRepo ↗

Tools you’ll have open

IoTeXScan ↗Mainnet and testnet block explorer
DePINscan ↗Where ioID projects get an API key
ioctl ↗CLI for accounts and contracts
Wallets ↗ioPay and other supported wallets

Releases & upgrades

2026-10-19Node manual ↗
Zanzibar hard forkMainnet block 53533081 · nodes v2.5.0+
2026-10-04Release ↗
iotex-core v2.5.1Maintenance patch, no hard fork
2026-09-28Release ↗
iotex-core v2.5.0Minimum version for Zanzibar
2026-08-07IIP-59 ↗
IIP-59 draftProtocol-native voter reward distribution

DATE	RECORD	DETAIL	SOURCE
2026-10-19	Zanzibar hard fork	Mainnet block 53533081 · nodes v2.5.0+	Node manual ↗
2026-10-04	iotex-core v2.5.1	Maintenance patch, no hard fork	Release ↗
2026-09-28	iotex-core v2.5.0	Minimum version for Zanzibar	Release ↗
2026-08-07	IIP-59 draft	Protocol-native voter reward distribution	IIP-59 ↗

Source: GitHub · iotex-core, iotex-bootstrap, iips · as of 23 Oct 2026

BUILD IN THE OPEN

Ask, share and shipin the open.

Ask on Discord, discuss on the Forum, send fixes on GitHub.

ASK

Stuck on a step?

Bring the error, your setup and a small repro.

Developer Discord ↗

Show what you built

Post the repo and the problem it solves.

Community Forum ↗

CONTRIBUTE

Send a fix

Open an issue, then a pull request.

How to contribute ↗github.com/iotexproject ↗

WHERE THE CODE LIVES

iotex-coreRepo ↗
Go · Apache-2.0The L1 protocol and node.
iotex-antennaRepo ↗
JavaScript · Apache-2.0The JavaScript SDK for the chain.
quicksilverRepo ↗
TypeScriptThe agent framework and its data tools.
iipsRead ↗
ProposalsWhere protocol changes are discussed.

Build for real machines,with other builders.

What are you building?

Build an AI agent

Make a machine decision

Give a machine an identity

Deploy a smart contract

Build with IoTeX

Point your EVM tools at IoTeX

Give each device an on-chain identity

Agents that call your APIs and data tools

Models that propose machine operations

Realms: knowledge bases fed by machines

Run models near your machines

Build for a use case

An assistant that answers from live sources

Machines that propose, code that decides

Devices others can verify

Machines that coordinate through events

Learn by building

Deploy and talk to a contract

Run the demo agent locally

Run the demo agent locally

Call a published agent

Register a device on-chain

Docs, APIs & tools

Network values

APIs & SDKs

Contracts & RPC

Identity & Data

Nodes & Upgrades

Tools you’ll have open

Releases & upgrades

Ask, share and shipin the open.

Stuck on a step?

Show what you built

Send a fix

WHERE THE CODE LIVES