Use the SDKs when you want a simpler application integration model on Autonomi.
This approach combines:
a local daemon called antd
REST and gRPC interfaces exposed by that daemon
language SDKs in Python, Node.js / TypeScript, Go, Rust, Java, C#, Kotlin, Swift, Ruby, PHP, Dart, Zig, and other supported languages
Choose the SDKs if you want:
a local API between your application and the network
a stable local API instead of direct peer-to-peer networking in your app
one local daemon process that multiple apps, scripts, or tools can share
SDK support in the language you already work in
antd runs on your machine and talks to the network for you. The SDKs, REST API, gRPC clients, and MCP server all build on that same local daemon.
Your application code can still be Python, Node.js / TypeScript, Go, Rust, or another supported language. The supported antd install method in these docs is to build the daemon from the ant-sdk repo, then connect to it from the SDK language you choose.
If you would rather work directly from the terminal, use the CLI. If you want daemon-free Rust access, see Build Directly in Rust.
Start with Start the Local Daemon to build antd from source, run it in read-only mode, and verify that it is healthy.
If you only need read-only features, continue to Retrieve Data from the Network.
If you need uploads after the read-only flow, choose one of these next steps:
Prepare a Wallet for Uploads for daemon-signed writes on the default network
Use External Signers for Upload Payments when your app should keep the signing key outside antd
Set Up a Local Network if you want local services and test funds provisioned for you
Once the daemon is running and you have set up writes, continue to Store Data on the Network.
If you already know your target language, use the Language Bindings section for setup and API details.
Last updated
