Reactor SDKs

Reactor has one off-chain transport path and one on-chain path.


Application -> optional evm payload helper -> ReactorClient.send
            -> https://api.reactor.network/v1/messages
            -> Reactor Website/BFF -> Reactor Core.send

TypeScript, Python, and Go applications use an API key and the public HTTP endpoint. They never call Reactor Core directly. The optional evm namespace produces 0x-prefixed ABI payloads for Reactor’s current EVM actions without requiring an API key, HTTP client, RPC endpoint, signer, or private key.


Solidity contract -> IReactorFeeManager.getSendFee
                  -> IReactorHelper encode/decode
                  -> IReactorGateway.send

Solidity integrations use the Gateway contracts directly and have no HTTP or API-key model.

Choose an SDK

Language	Install	Start here
TypeScript	`npm install @reactor-network/sdk`	TypeScript
Python	`python -m pip install reactor-sdk`	Python
Go	`go get github.com/ReactorNetwork/reactor-sdk-go`	Go
Solidity	`npm install @reactor-network/sdk-solidity`	Solidity

EVM helper namespace

evm is intentionally chain-family-specific so Reactor can add other chain families later without polluting or breaking the SDK root API. It currently supports:

chain_message: wrap arbitrary bytes with named Reactor parameters.
web_message: encode a Web request and decode request/response payloads.
generate_random_numbers: encode a positive uint256 count and decode a uint256[] response.

All three action requests use the exact layouts implemented by the current Reactor EVM Helper. Their encoded output can be passed directly to the language client’s send method.

See Sending Messages, the HTTP API, and the Gateway reference.