healthpass1™, which helps make it simple to keep all your health and wellness information in one private, easy-to-manage place, has selected Autonomys Network’s Auto Drive as a secure, decentralized storage foundation underlying its platform. Auto Drive's client-side encryption architecture ensures that data is encrypted on the user's device before it ever touches the network, meaning no storage operator, no network participant, and no third party, including healthpass1, has access to unencrypted file content. Encryption keys are generated and held exclusively by the user, making the data's permanence and privacy inseparable. Auto Drive is purpose-built by the Autonomys Network to ensure that stored data persists without dependence on any single company's continued operation; however if a user deletes their encryption key, that data becomes cryptographically unrecoverable by anyone, including Autonomys and healthpass1.


‍WHAT HEALTHPASS1™  HAS BUILT

A secure and private digital health passport

Most people's health information is scattered across dozens of disconnected systems. The primary care physician holds one record. The specialist holds another. Each pharmacy, fitness app, and hospital holds pieces of a picture that, in general, no single provider, and no patient, sees in full. Each of those systems also stores highly sensitive personal data on servers controlled by companies whose security practices and data policies individuals have no ability to audit or influence. In a routine appointment, this fragmentation creates friction. In an emergency, it creates risk. And across a lifetime of care, it means that the people making healthcare recommendations  may not have the complete information they need to make the best decisions. healthpass1 changes this. The healthpass1 app helps make it simple for users to consolidate their health and wellness information into a single, private, encrypted digital passport that lives on their phone and travels with them everywhere.

The healthpass1 app is patent pending and will enable individuals to connect to healthcare portals and integrate with fitness apps and wellness platforms. It will accept manual uploads of photos, PDFs, and lab results. If enabled, it can also deliver AI-powered insights and organizational tools. Most importantly, the healthpass1 app will give individuals granular, consent-based sharing controls, so users decide exactly which providers, family members, or emergency personnel can see which information, and for how long. Throughout all of it, the data is designed to remain encrypted and private. Sharing is always an explicit act of consent, never a default.

"The healthpass1 app helps make it simple for individuals to keep their health and wellness information in one private, easy-to-manage place where they control what is shared, with whom and for how long. I’m excited to bring healthpass1 to market with an outstanding team of co-founders who have the depth and breadth of experience that highly regulated industries require."
  — Deborah A. Bussière, CEO healthpass1

‍

THE INFRASTRUCTURE

Why Auto Drive. Why It Matters.

A health record is only as reliable as the system storing it. Files held on conventional cloud servers can be deleted, altered, or made inaccessible through corporate policy changes, company failure, or acquisition. They can also be accessed, subpoenaed, or exposed through the security failures of the companies that control them. For medical records, none of these scenarios are acceptable.

Auto Drive is built differently. Before a file ever touches the network, it is encrypted on the user's own device using AES-256-GCM, the same encryption standard used by governments and financial institutions to protect their most sensitive data. The encrypted file is then written permanently into the archival record of the Autonomys Network and replicated across a global mesh of independent storage operators. No single entity controls the network. There is no central server to take offline, no single company to compel, and no designed pathway through which a stored record can be changed or removed. Critically, no storage operator or network participant ever handles anything other than encrypted data. Without the user's password, the stored content is designed to be cryptographically inaccessible to everyone. Permanence is not a promise or a policy. Neither is privacy. Both are structural properties of how the storage is designed to work.

For healthpass1, this means the health information its users store is designed to be private and secure from the moment it is written. For individuals, it means their health history belongs to them in a way that a conventional cloud application may not deliver. Not because of a privacy policy; but because of the inherent architecture.

Auto Drive is developed and operated by the Autonomys Network, a Layer-1 infrastructure platform whose storage network currently has approximately 400 independent operators globally pledging more than 50 petabytes of storage capacity. The product offers a developer experience comparable to familiar cloud storage tools, with a TypeScript and JavaScript SDK and a RESTful API, making integration straightforward for any engineering team.

"Health data is among the most personal information a person generates in their lifetime. Auto Drive is designed to give healthpass1 users confidence that their records exist privately, securely, and permanently, on infrastructure no single company controls, and remain accessible to the user from anywhere in the world."
  — Todd Ruoff, CEO Autonomys Network 

‍

ABOUT THE FOUNDER OF HEALTHPASS1™ 

Deborah A. Bussière, Founder and CEO of healthpass1
Deborah A. Bussière is an accomplished C-suite executive whose career spans 25 years in traditional financial services and over a decade in decentralized financial services. She served as Global Chief Marketing Officer at Broadridge Financial Solutions, Chief Marketing Officer at Grayscale Investments, and Chief Marketing Officer at EY Americas. Earlier in her career, Deborah held senior sales and marketing roles at UBS and Morgan Stanley.

healthpass1 is patent pending and built on her conviction that health data infrastructure should be as secure, private, and personally controlled as the most sensitive financial data in the world.

LOOKING AHEAD

Building the future together
This partnership represents something larger than a technology integration. It is a signal of where we believe patient-centered healthcare is heading: toward a future where individuals can arrive at every appointment, every emergency, and every health decision with a more complete health history in hand.  
healthpass1 and the Autonomys Network are building that future together.

To follow the journey and be among the first to experience what patient control of health data can look like, visit:

healthpass1.com

To learn more about and sign up for private, secure, and truly permanent storage, visit:

ai3.storage

‍

DISCLAIMER: healthpass1™ is a personal health information management tool and does not provide medical advice, diagnosis, or treatment. The information stored and organized through healthpass1 is not a substitute for professional medical advice, diagnosis, or treatment. Always seek the advice of your physician or other qualified health provider with any questions you may have regarding a medical condition. Never disregard professional medical advice or delay seeking it because of information accessed through healthpass1.

Auto Drive was built to make permanent, on-chain storage as simple as any cloud storage tool you already use. Today, we are taking a meaningful step toward the broader vision: you can now pay for storage directly with AI3, the native token of the Autonomys Network.

‍

What This Means

Until now, accessing Auto Drive credits required going through us. Foundation grants, manual credit allocations, and forms to fill out. That worked as a starting point, but it was never the end state. Pay with AI3 removes the intermediary entirely. If you hold AI3, you can purchase storage credits directly, on your own terms, without asking anyone for permission.

For developers, that shift has a practical benefit worth naming. You can now build applications on top of Auto Drive with a storage layer that is self-sufficient from day one, funded by the token, and free from any dependency on foundation access programs. That is a meaningful shift in what it means to build on Autonomys.

‍

How It Works

The flow is straightforward. Sign in via Google, connect your EVM wallet, select how much storage you want to purchase, and complete the transaction. Your credits are available immediately. From there, the experience is identical to what Auto Drive users already know: upload through the dashboard at ai3.storage, integrate via the Auto SDK, or call the REST API directly.

Storage pricing is derived from the on-chain cost of the Autonomys Distributed Storage Network, with a service fee applied on top. The price per byte is transparent and updated every block.

To learn how to Pay with AI3, visit: https://youtu.be/KMpVhpOaFgU

‍

A Note on Current Limitations

We want to be upfront about the restrictions in place at launch. These are deliberate economic protections, not permanent product decisions. The Autonomys Network is still in its early growth phase, and we need to prevent storage credit hoarding or speculative accumulation that would work against how the system is designed to operate. The goal is for credits to be used, not held.

The protections currently in place are these: 

• Google authentication is required to purchase credits. 
• Each account can hold a maximum of 100GB of purchased storage credits at any time. 
• Purchased credits expire after 90 days. Any unused credits remaining at expiry are automatically refunded. 

We want people storing data, not accumulating capacity they never intend to use.

These constraints will be revisited as the network matures and we have clearer data on real usage patterns. If you are building something that these limits add friction to, reach out.
For full details on Pay with AI3 Terms of Use, please visit:  autonomys.xyz/auto-drive-terms-of-use 

‍

Building on Top of Pay with AI3

If you are building an application that stores data on behalf of your users, the natural question is how payment works in that context. Pay with AI3 gives you options. Your application can handle storage costs directly, or you can have users purchase their own credits under their own Auto Drive identity. The right approach depends on your use case, and we expect different patterns to emerge as the ecosystem matures.

The first application built against it is Eulonomys, a tool for creating permanent, on-chain eulogies. It is open source (GitHub) and designed to serve as a reference for how third-party applications can integrate Auto Drive and Pay with AI3 end to end.
To see how the application works, visit: https://youtu.be/cMlaWvectS8 

The developer experience matters to us as much as the end-user experience. As more applications come online, the integration surface will mature, and we will document the patterns that prove out in practice. If you are building something now and want guidance, reach out.

‍

For Web2 Developers

If you are new to Web3 and do not yet hold AI3, that is not a barrier to getting started. We are still happy to provide a meaningful amount of complimentary credits so you can explore Auto Drive, test integrations, and build with confidence before committing to a purchase. Sign up at ai3.storage and the free tier is available immediately upon account creation.

Looking further ahead, we are actively exploring fiat payment options. The vision for Auto Drive has always been that anyone, regardless of their familiarity with crypto or token markets, should be able to access permanent decentralized storage on their own terms. Pay with AI3 is a major step in that direction. Fiat access would complete it, and we are thinking carefully about what that looks like. It is also worth noting that nothing prevents a third party from building that bridge independently, and we think that is an interesting opportunity for the right builder. 

‍

Why This Matters

The Autonomys Network was built from the ground up to provide permanent, on-chain storage as a protocol-level guarantee. What was missing was a direct, permissionless path to access it through AI3. Pay with AI3 addresses that directly. It connects the economic layer of the Autonomys Network to the storage layer in a way that does not require trusting a foundation, waiting on a grant, or asking for access. That is the kind of infrastructure that developers building production applications can actually depend on, and it is what we have been working toward from the start.

Get started at: ai3.storage.
Full SDK documentation is available at: develop.autonomys.xyz/sdk/auto-drive

March was defined by a clear signal: AI agent developers are adopting Auto Drive not as an experiment but as core infrastructure. March was Auto Drive's breakout month for agent memory storage, with upload activity at 4x February's volume as builders increasingly adopted permanent storage as a skill registry, a memory layer, and a verifiable record of agent behavior. Three integration updates deepened the network's presence across DePIN and agent ecosystems, the Subspace Foundation announced its first grantee, and engineering continued building toward releases that will expand what operators and developers can do on the network. This report outlines the material progress made in March and the momentum carrying into April.

‍

Operations

The lean, capital-efficient team structure continued to deliver in March. AI agents are now building analytical tools that surface how users interact with Auto Drive, informing more targeted outreach and audience development. An organisation-wide rollout of AI tooling across Slack, Notion, GitHub, Webflow, and Google Suite continued to accelerate team productivity, while Autonomys agents engage directly with users across social channels, generating organic community interaction and surfacing real partnership opportunities.

‍

Engineering & Protocol

• Proof-of-Stake performance: Updates are in progress and approaching release, with improvements expected to strengthen network stability and operator experience.
• Security: Routine dependency-level updates were applied across the stack.
• Substrate upgrade: Planning has begun; implementation is yet to start.
• Data Domains research: Research into Data Domains is ongoing. Further details to follow as the work progresses.
• Auto Drive frontend optimization: We've improved how the Auto Drive web frontend handles authentication requests, eliminating delays that could previously extend page load times to up to 20 seconds. Users can now expect a noticeably faster and more responsive experience across the platform.
• Auto Drive: Development continued on Pay with AI3, a new system that brings the opportunity to purchase additional storage capacity natively using AI3 tokens on the Autonomys Network. Over recent months, the full infrastructure was built out, from the tracking system for individual credit purchases, through the core business logic that atomically consumes purchased credits during uploads, to the payment intent system that locks in prices and confirms transactions on-chain. The purchase flow is secured behind Google authentication for the public launch, with safeguards against edge cases like concurrent cap breaches, dust payments, and transactions submitted while the payment manager was temporarily down. On the frontend, users get a complete purchase experience: package selection, price confirmation, on-chain transaction submission, and a credit balance displayed directly in the sidebar with expiry warnings and a full purchase history page. With the infrastructure in place and the remaining robustness and observability work complete, the feature is being prepared for launch.

‍

Community & Foundation

Stakeholder Unlocks

The Subspace Foundation's primary focus in March has been preparation for upcoming stakeholder unlocks with initial beneficiary emails being sent last week. Stakeholders can expect direct communications in the coming weeks with additional details on mechanics and any actions required.

Grants

The Subspace Foundation Grants Program continues to attract strong applications, with several projects currently in active review. This month marked a significant milestone: the Foundation's first grantee was announced.

Momento has been awarded a grant to build a protocol that preserves authentic human experiences as verifiable on-chain records using Autonomys. Momento turns the network's permanent DSN and EVM-compatible execution layer into a seamless capture-and-verify experience for real-world artefacts — photos, stories, cultural records — with no blockchain knowledge required from the end user. Read the announcement.

‍

Ecosystem & Developer Momentum

Three integration updates in March continued to deepen Auto Drive's presence across DePIN infrastructure and the AI agent ecosystem.

Fry Networks

Fry Networks has integrated Auto Drive as the permanent public record layer for its global distributed physical infrastructure network. Sensor data collected by Fry Networks nodes, including bandwidth, GPS location, ambient radiation, and acoustic measurements, is now permanently archived on the Autonomys DSN and independently verifiable on-chain. Read more.

SpoonOS

SpoonOS has deepened its Auto Drive integration from basic upload and download to a complete programmatic interface covering the full Auto Drive API surface. With 25 production-ready tools now available, every SpoonOS agent in the ecosystem can upload, manage, retrieve, and publish files as a native capability within its reasoning loop. Read more.

Heurist Skills Marketplace

Heurist has launched a full Skills Marketplace in which every skill is verified and permanently stored on Autonomys' DSN via Auto Drive. Each skill is assigned a permanent, immutable Content Identifier (CID), ensuring the version deployed is the version accessible and verifiable indefinitely. Skills are compatible with OpenClaw, Claude Code, Codex, and any agent supporting the SKILL standard. Read more.

Secret Network

Progress on deepening the bidirectional Autonomys and Secret Network integration is going well. Further details will be announced in April.

WeatherXM x Autonomys Builders Program

The first wave of applicants is currently in the discovery process. Updates will follow as successful applicants are confirmed. To apply: autonomys.xyz/builders.

‍

ICYMI: Content Published in March

• Momento Awarded Subspace Foundation Grant — March 4
• Autonomys Network x Fry Networks: Permanent On-Chain Storage for Real-World DePIN Data — March 5
• Integration Update: SpoonOS Deepens Auto Drive Integration — March 10
• Integration Update: Introducing the Heurist Skills Marketplace — March 17

‍

New for Builders

Building AI agents and want to give them permanent memory?

• Auto Drive: ai3.storage
• Developer Docs: develop.autonomys.xyz/sdk/auto-drive
• OpenClaw Skills: github.com/autonomys/openclaw-skills
• Autonomys GitHub: github.com/autonomys
• Autonomys-backed ClawHub Skills:
  
  • clawhub.ai/0xautonomys/permanent-memory
  • clawhub.ai/0xautonomys/respawn

‍

Metrics: March Snapshot

Staking: 39,851,605 AI3
Auto Drive Files Uploaded: 1,227 (Mar.) / 129,323 (All time)
Auto Drive Downloads: 1,199 (Mar.) / 12,575 (All time)
Auto Drive Users: 646
Total Announced Partnerships: 63
Announced Auto Drive Integrations: 8
Total Grant Applications: 45

‍

Looking Ahead

In April we anticipate being able to share further details on the Secret Network bidirectional integration, initial results from the WeatherXM x Autonomys Builders Program discovery process, and continued progress on stakeholder unlock preparation. We are also working toward announcing a partnership with a health data application that would represent a genuinely new category of use case for permanent, verifiable on-chain storage.

We are proud to announce that Heurist has deepened its integration with Autonomys. What began as permanent, verifiable storage for Heurist’s research app, image minting features, and the Heurist Imagine interface, ensuring AI-generated outputs are cryptographically stored and persistently accessible, has now expanded into something far more consequential: a full Skills Marketplace, where every skill is verified and permanently stored on Autonomys via Auto Drive, the gateway to our permanent storage layer.

‍

The Problem with Unverified Agent Tools

“AI agents are only as good as the tools they run.” ~Heurist. In crypto and finance workflows, this is not an abstract concern. An agent signing a transaction, querying on-chain data, or executing a financial operation based on unverified code is a real and serious security risk. Unverified scripts have no accountability. They can be tampered with, swapped out, or simply wrong.
The Heurist Skills Marketplace was built to solve this directly.

‍

What Launched

The Heurist Skills Marketplace and CLI is a curated, audited registry of agent skills built exclusively for crypto and finance workflows. Every skill and every version in the catalog is reviewed and verified before it is listed. No exceptions.

You can explore and install skills today:

• Search the catalog: npx @heurist-network/skills find
• Install a skill: npx @heurist-network/skills add <skill-name>
• Browse the marketplace: https://mesh.heurist.ai/console/skill-marketplace

The catalog includes 30+ verified skills, including Binance Web3 tools, OpenZeppelin handlers, and on-chain analytics capabilities.

‍

All Skills Permanently Stored on Autonomys

Every skill and version listed in the marketplace is verified and permanently stored on Autonomys via Auto Drive. This is not a database record or a hosted file that can be quietly modified. It is a permanent, content-addressed record stored across Autonomys’ globally distributed storage network, where the data inherits the same integrity guarantees as the network itself.

What that means in practice: the version of a skill you deploy today is the version that will be accessible and verifiable indefinitely. There is no silent update. There is no link that goes dead. The record is permanent, and it cannot be altered after the fact.

This is what verified means in the context of the Heurist Skills Marketplace. Not just audited once and filed away. Cryptographically stored, permanently accessible, and independently verifiable by anyone.

‍

Works Out of the Box

Heurist Skills are compatible with OpenClaw, Claude Code, Codex, and any agent that supports the SKILL standard. Each skill is optimized for high signal and low overhead: fewer tool calls, less token usage, faster execution. For developers building agentic systems on high-stakes workflows, that efficiency matters.

‍

The Bigger Picture

This launch represents a meaningful step in what the Heurist and Autonomys partnership is building toward. Permanent storage is not a feature for its own sake. It is the infrastructure condition that makes trust possible at scale. When the tools your agents use are permanently recorded and independently verifiable, you have a foundation for accountability that centralized storage simply cannot provide.

Explore the Heurist Skills Marketplace or try Auto Drive for free today to give your agent or AI build permanent storage.

Marketplace: https://mesh.heurist.ai/console/skill-marketplace
Auto Drive: https://ai3.storage/
Documentation: https://develop.autonomys.xyz/sdk/auto-drive

‍

About Heurist

Heurist is building the agentic Web3 AI economy. Built on a privacy-preserving ZK Layer-2, it enables an open and composable agent ecosystem by allowing developers to create AI agents for Web3 use cases with accurate blockchain data, efficient tool execution, and deep research. Heurist Mesh aggregates high-quality datasets, crypto APIs and verified agent skills in one secure platform, supporting ERC-8004 discovery and x402 monetization. Ask Heurist agent is the flagship crypto analysis and financial research agent, powered by the premium data source and tools of the Heurist Mesh. Through comprehensive infrastructure covering compute, payment, and agent coordination, Heurist provides the foundation for scaling the next generation of decentralized AI.

X | LinkedIn | Discord | Telegram | Blog | Docs

‍

About Autonomys

The Autonomys Network — the foundation layer for AI3.0 — is a hyper-scalable decentralized AI (deAI) infrastructure stack encompassing high-throughput permanent distributed storage, data availability and access, and modular execution. Our deAI ecosystem provides all the essential components to build and deploy secure super dApps (AI-powered dApps) and on-chain agents, equipping them with advanced AI capabilities for dynamic and autonomous functionality.

X | LinkedIn | Discord | Telegram | Blog | Docs | GitHub | Forum | YouTube

‍SpoonOS agents can now upload, manage, retrieve, and publish files to Autonomys’ permanent storage infrastructure, directly within their reasoning loops, with 25 production-ready tools built on the Auto Drive REST API.

Overview

SpoonOS and Autonomys Network share a foundational conviction: AI agents need infrastructure that matches their level of autonomy. An agent that reasons, acts, and learns deserves a storage layer that does not expire, does not depend on any single company staying online, and produces outputs that are permanently cryptographically verifiable.

That conviction is now fully realized in code. SpoonOS has deepened its existing Auto Drive integration from basic file upload and download into a complete programmatic interface covering the entire Auto Drive API surface. Every SpoonOS agent running in the ecosystem can now treat permanent storage as a native capability, not a custom integration project.

What is SpoonOS?

SpoonOS is an agentic operating system powered by a leading Layer 1 blockchain, Neo, designed to meet the evolving needs of the Web3 developer ecosystem. It supports Neo’s AI strategy by managing the full lifecycle of AI agents on Neo X, including deployment, configuration, monitoring, upgrading, and cross-agent collaboration. Its agents follow the ReAct pattern: they reason about a problem, take an action using one of their available tools, observe the result, and iterate. The spoon-toolkit package is the library of modular, production-ready tools that agents use. SpoonOS supports multi-model LLM execution across OpenAI, Anthropic, DeepSeek, and others, with MCP (Model Context Protocol) support for connecting to external tool servers.

The existing spoon-toolkit storage category already included integrations with AIOZ, OORT, and 4EVERLAND. Auto Drive now joins that category as a first-class member, with substantially more functional depth than any of the other storage integrations.

What is Auto Drive?

Auto Drive is the developer-facing gateway to Autonomys Network’s Distributed Storage Network (DSN). It transforms the underlying infrastructure of the Autonomys Network into a practical, developer-friendly storage tool. Think of it as the simplest way to store a file and guarantee it will exist permanently, without relying on any centralized service, without ongoing fees for keeping the file alive, and without trusting a third party to honor your data.

Every file stored through Auto Drive receives a content identifier (CID), a unique cryptographic fingerprint derived from the content itself. That CID is stable and permanent. Files can be optionally encrypted end-to-end. A RESTful API and a TypeScript/JavaScript SDK via @autonomys/auto-drive are available for developers integrating into production systems. Auto Drive is available on Autonomys Mainnet and is accessible at ai3.storage.

Think IPFS meets S3, but permanent by default. Auto Drive delivers content-addressed storage with a familiar developer interface, zero pinning requirements, and permanence guaranteed at the infrastructure level.

What Spoon Built: A Full-Surface Integration Across 25 Tools

The integration is organized into four functional layers, each implemented as a set of BaseTool subclasses that SpoonOS agents can call as native actions within their reasoning loops. The entire module is activated with a single environment variable: AUTONOMYS_AUTO_DRIVE_API_KEY.

1. Uploads (4 Tools)

The most developer-significant tool is UploadFileTool, which implements intelligent routing based on file size. Files under 25MB are handled with a direct single-request upload. Files over 25MB automatically switch to chunked upload, where the file is broken into sequential 5MB chunks, each uploaded individually with retry logic and configurable exponential backoff on failure. MIME type is detected automatically from the file extension. Developers interact with one tool regardless of file size.

For teams that need precise control, UploadFileSmallTool and UploadFileLargeTool are available as direct callers with fully configurable parameters including chunk size, retry count, and resume behavior for interrupted uploads.

2. Downloads (8 Tools)

The download layer covers four distinct retrieval patterns, each with two modes: standard (loads the full file into memory) and streaming (processes the file in chunks, preventing memory overload for large files).

• DownloadObjectTool / StreamDownloadTool: Retrieve any file by CID from the Auto Drive network.
• DownloadPublicObjectTool / StreamDownloadPublicObjectTool: Retrieve files that have been published and made publicly accessible, using the object’s public ID rather than its CID.
• CreateAsyncDownloadTool / GetAsyncDownloadStatusTool / ListAsyncDownloadsTool / DismissAsyncDownloadTool: Initiate a background download task by CID, poll its status using the returned UUID, and dismiss it upon completion. This pattern enables agents in long-running workflows to initiate a retrieval, continue other work, and collect the result without blocking.

3. Object Management (12 Tools)

This is the layer that elevates the integration from a storage utility into a full data management capability. Agents can now programmatically control the full lifecycle of any object they store.

• GetRootObjectsTool / SearchObjectsTool: List and search objects by name or CID, scoped to the agent’s own files or the global network.
• PublishObjectTool / UnpublishObjectTool: Publish a stored file to a publicly accessible endpoint, receiving a stable object ID distinct from the CID. Unpublish to revoke public access.
• ShareObjectTool: Share a specific file with another user via their Auto Drive public ID.
• DeleteObjectTool / RestoreObjectTool: Soft-delete and restore objects, with GetDeletedRootObjectsTool for inspecting what has been removed.
• GetObjectSummaryTool / GetObjectStatusTool / GetObjectMetadataTool: Retrieve summary, status, and full metadata for any object by CID, enabling agents to reason about their stored artifacts before acting on them.
• GetSharedRootObjectsTool: List files that other users have shared with the agent.

4. Account (1 Tool)

GetAccountInfoTool retrieves the agent’s current account information including storage limits and credit status. This enables cost-aware agent behavior: an agent can check its available upload capacity before attempting to store a large file, rather than failing mid-operation.

Why This Matters for Developers in Both Ecosystems

For SpoonOS Developers

Before this integration, SpoonOS agents producing outputs had three options: store them in ephemeral in-memory state (lost when the session ends), write them to a centralized service (introduces a single point of failure), or use one of the other storage toolkit integrations (all off-chain, none with verifiable permanence). None of those options gave an agent the ability to produce a cryptographically addressable, permanently retrievable artifact.

That changes now. A SpoonOS agent can upload an output, receive a CID, publish it to a stable public URL, pass that URL to another agent in a multi-agent workflow, and have every downstream consumer retrieve the exact same content using that CID indefinitely. The content cannot change. The reference cannot break. The file cannot disappear.

The async download pattern is particularly valuable for SpoonOS’s StateGraph workflow architecture. An agent can now kick off retrieval of a large file, transition to another state in the graph to continue parallel work, and return to collect the downloaded result. That is a materially different execution model than blocking on a synchronous download.

For the Autonomys Ecosystem

SpoonOS is a Python-first framework, and the existing Autonomys Auto Drive SDK is TypeScript/JavaScript-only. This integration brings permanent storage access to the Python AI agent development community natively, through a package that installs with a single pip command: pip install spoon-toolkits.

That distribution matters. Python is the dominant language for AI/ML development. Every developer building agents on SpoonOS who installs spoon-toolkits now has access to Auto Drive without writing a single line of API client code. The barrier to permanent storage adoption collapses to setting one environment variable and calling a tool.

The Bigger Picture: Agents That Remember

The most consequential property of this integration is not any individual tool. It is what becomes possible when an AI agent has a memory layer that persists across sessions, produces verifiable outputs, and operates without depending on any single company to maintain infrastructure.

An agent with permanent storage can accumulate knowledge over time. Its past decisions and their outcomes do not disappear when a session closes. Its outputs can be audited by humans or other agents. Its reasoning can be independently verified. These are the properties that transform an AI agent from a stateless query-response machine into a system capable of genuine, accountable autonomy.

This is precisely what the Autonomys Network was designed to enable, and what SpoonOS is now delivering to its developer ecosystem in production-ready Python.

Get Started

The Auto Drive integration is available now in the spoon-toolkit repository. To use it:

Create your free Auto Drive account and API key at ai3.storage. Every account includes a complimentary 20MB upload and 5GB download per month on signup. No wallet required to get started.

Full SDK documentation is available at: develop.autonomys.xyz/sdk/auto-drive

The spoon-toolkit integration source is available in the SpoonOS GitHub repository at: https://github.com/XSpoonAi/spoon-toolkit/tree/main/spoon_toolkits/storage/autonomys_auto_drive

Autonomys Network | Access Auto Drive | @AutonomysNet

‍

Autonomys is pleased to share that Fry Networks has integrated Auto Drive, gaining direct access to Autonomys’ Distributed Storage Network (DSN) for permanent, tamper-proof, on-chain data storage.

This integration establishes Auto Drive as the permanent public record layer for Fry Networks’ distributed physical infrastructure, a deliberate choice to make the network’s real-world activity, geographic coverage, and operational health independently verifiable on-chain, so trust is earned through proof, not asked for on faith.

What the Integration Is

Fry Networks is building a distributed physical infrastructure network (DePIN) where hardware nodes deployed around the world run sensors and execute compute tasks. Each node continuously collects real-world measurements across multiple sensor categories, with more being added over time.

Fry Networks uses Auto Drive as the permanent storage layer for this sensor data. Auto Drive is Autonomys’ S3-compatible gateway to its Proof-of-Archival-Storage (PoAS)-powered DSN, where stored data inherits the permanence, immutability, and cryptographic verifiability guarantees of the Autonomys Network itself.

In practice, this means every hourly data record produced by Fry Networks’ global node fleet is written permanently to Autonomys’ decentralized storage layer, where it remains tamper-resistant and publicly verifiable indefinitely.

How It Works (Technical Overview)

The following data pipeline is implemented by Fry Networks and shared here for clarity and accuracy.

Data Collection and Aggregation

Each Fry Networks node samples sensor data every minute. Raw samples are aggregated into hourly Parquet files before upload, reducing storage overhead while preserving statistical fidelity.
The current data types stored are (with more to come):

Bandwidth: Download and upload speeds sampled every minute, aggregated into hourly records capturing average, minimum, and maximum Mbps values along with peak usage hours.

GNSS/Satellite: GPS fix quality, satellite count, and HDOP (Horizontal Dilution of Precision) scores per node, proving each node’s location reliability over time.

Radiation: Ambient ionizing radiation measurements in CPM (counts per minute), µSv/h (microsieverts per hour), and mR/h (milliroentgens per hour), representing a continuously updated environmental sensing record.

Acoustics: Ambient noise levels in dBFS (decibels relative to full scale), providing environmental monitoring data from each node’s physical location.

AI Tool: Per-node uptime ratios, tasks completed per hour, and memory usage statistics, proving AI workload execution across the network.

Privacy Redaction Before Upload

Before any data is uploaded to Auto Drive, Fry Networks applies two privacy redaction steps: GPS coordinates are coarsened to approximately 250 km² H3 hexagonal grid cells (removing precise location data while preserving geographic distribution information), and IP addresses are stripped entirely. The resulting Parquet files contain no personally identifiable information.

Upload via S3-Compatible API

Aggregated, privacy-redacted Parquet files are uploaded to Auto Drive using its S3-compatible API. Once written to Autonomys’ DSN, each file is assigned a unique content identifier (CID) and stored permanently on-chain across Autonomys’ globally distributed network of storage nodes.

Why Fry Networks Chose Auto Drive

Trustless Verifiability for Investors and Partners
Fry Networks’ primary motivation for choosing Auto Drive is eliminating the need to ask stakeholders to trust a dashboard the team controls. Because data is written to Autonomys’ on-chain storage layer, anyone can independently retrieve and verify the raw records: node count over time, geographic coverage, uptime ratios, sensor outputs, and AI workload execution. The data is not hosted by Fry Networks. It lives on Autonomys’ DSN, where the protocol’s PoAS consensus makes it tamper-resistant by design.

S3-Compatible Integration
Auto Drive’s S3-compatible API allowed Fry Networks to integrate without building against a novel protocol interface. The upload pipeline plugs directly into existing tooling, reducing integration friction and development overhead.

Permanent Record
By design, data written to Autonomys’ DSN cannot be deleted, modified, or made unavailable by any single party. For a network whose credibility depends on demonstrating consistent long-term operation, this permanence is not a feature. It is the point.

Why This Matters

DePIN networks face a structural credibility problem: the data they publish about their own performance is inherently unverifiable if it lives in the infrastructure they control. Investors, partners, and users have no way to distinguish a thriving network from a well-maintained dashboard.

Fry Networks’ integration with Auto Drive resolves this directly. By writing operational data permanently to Autonomys’ DSN, Fry Networks transforms its activity record from a set of claims into a set of on-chain facts. Node counts, geographic coverage, sensor outputs, and AI workload execution are now independently auditable by anyone, at any time, without requiring trust in any party.

This is the infrastructure model that serious DePIN networks will need to adopt as the sector matures. Data permanence and independent verifiability are not competitive advantages. They will be baseline requirements.

Autonomys is proud to support the Fry Networks team as they build out their global node infrastructure. Their approach to operational transparency through on-chain data anchoring reflects exactly how we think permanent storage should be used: not as a passive archive, but as an active trust mechanism that makes network claims independently verifiable by design.

Start building on Auto Drive: ai3.storage
Documentation: develop.autonomys.xyz/sdk/auto-drive

About Fry Networks

Fry Networks is building the orchestration layer of interconnected networks: a “network of networks” that bridges protocols, systems, and devices into one cohesive data mesh. Founded and led by Samuel Fry, who brings over 15 years of experience in enterprise networking, cybersecurity, and systems architecture, Fry Networks ships real hardware across a growing range of device categories — including AI Edge Agents, Bandwidth Gateways, Satellite Sensors, Noise Sensors, and Radiation Sensors — with over 9,100 devices currently online and a Bring-Your-Own-Device (BYOD) program that allows individuals and organizations to connect compatible hardware directly into the mesh. The network’s Fry 2.0 evolution advances the project toward a sustainable, privacy-first, hardware-verified data layer, with Auto Drive serving as the permanent on-chain ledger that enables trustless, independent verification of network scale, geographic coverage, and operational health.

X | LinkedIn | Discord | Telegram | GitHub | YouTube

About Autonomys

The Autonomys Network — the foundation layer for AI3.0 — is a hyper-scalable decentralized AI (deAI) infrastructure stack encompassing high-throughput permanent distributed storage, data availability and access, and modular execution. Our deAI ecosystem provides all the essential components to build and deploy secure super dApps (AI-powered dApps) and on-chain agents, equipping them with advanced AI capabilities for dynamic and autonomous functionality.

X | LinkedIn | Discord | Telegram | Blog | Docs | GitHub | Forum | YouTube