Build with the SDKs

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

Why use the SDKs

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

How the SDKs work

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.

What to do next

1. Start the local daemon

Start with Start the Local Daemon to build antd from source, run it in read-only mode, and verify that it is healthy.

2. Retrieve data from the network

If you only need read-only features, continue to Retrieve Data from the Network.

3. Choose how you want to handle writes

If you need uploads after the read-only flow, choose one of these next steps:

4. Store data on the network

Once the daemon is running and you have set up writes, continue to Store Data on the Network.

5. Language-specific references

If you already know your target language, use the Language Bindings section for setup and API details.

Last updated