ZEC will become the private money of AI agents. We’re making it happen on AxiomAI

Hello again all! I’m Aleph, one of the cofounders @ Astrea.

A few weeks ago, I posted here (shared below) about the private agentic economy we’re building toward, and why ZEC should be its private money.

In a few days, we’re releasing AxiomAI, our private AI desktop app for chat and agents.

I wanted to share our philosophy, explain what we’re building next, and get your thoughts.

Why there’s no privacy toggle

An agent doing useful work for you needs access to your files, memory, credentials, and sometimes financial information. It may also need tools that let it act on your behalf. The more you use it, the more it knows about you or your business.

Before a prompt leaves your device, AxiomAI verifies the execution environment and encrypts the request. The request is opened inside that verified environment, and the response comes back encrypted to your machine. The relay handles routing and billing without being designed to see the conversation in plaintext.

Every model follows this same path. There’s no privacy toggle.

A toggle would let us offer faster, cheaper options and probably win more users. But we think most people would leave it off for everyday work and switch it on only for sensitive tasks. By then, an agent may already have accumulated plenty of sensitive context.

The experience with transparent and shielded addresses also informs this decision. Activity outside the private path can reveal information about activity inside it. We don’t want users to have to work out when it’s safe to turn privacy off.

We think keeping it on is worth the tradeoff, but we’d like to hear whether you agree.

Why payments need to be private too

An agent researching trades, buying data, or negotiating for compute can keep its conversations encrypted and still reveal what it’s doing through its payments. Who it pays, how much it spends, and how much capital it has can all be sensitive.

If you ask an agent to research an investment privately, you probably don’t want the payment for that research to reveal your interest in it.

That’s why we’re supporting and incentivizing shielded ZEC usage. We believe ZEC should become the de facto currency for the agentic economy, and that agent settlement will become the largest available source of new shielded volume in the coming years. We’re building the agents ourselves to help make that happen.

Giving agents ZEC budgets

At launch, users can pay for AxiomAI with ZEC. Next, agents will have their own ZEC budgets, with permissions set by their owners. They’ll be able to pay for compute, data, APIs, financial services, or other agents, and earn ZEC for work they do.

For example, you could give an agent a research task and a small budget. Within your limits, it could buy a dataset, pay another agent for specialist analysis, and cover the compute needed to finish. If it earns ZEC from its own work, it could keep those earnings to fund future tasks.

This is what interests us beyond accepting ZEC for an app: agents having regular reasons to earn it, hold it, and spend it.

Where Astrea fits

Shielded ZEC should be useful wherever people want to put their money to work. But using it in an EVM market or an application on another network can compromise the privacy it provides.

Hence we’re building Astrea, a private execution layer, to give shielded ZEC real utility and composability while preserving that privacy. An individual or agent should be able to use it to pay for services, access lending markets, trade, or invest without exposing their identity, balances, and the private context behind those actions.

That would expand ZEC’s role beyond a private store of value. You could hold your savings in shielded ZEC and use that same capital to make payments or fund investments, bringing proceeds back into shielded ZEC afterward. There would be more reasons to keep ZEC on hand because there would be more you could do with it.

Composability means those uses can work together. An agent could pay for research, use the findings to make an investment within limits you set, and put the proceeds toward its next task. Astrea would connect it to the applications needed to do that, with shielded ZEC as its working capital.

AxiomAI is one place we want to make this useful, but Astrea is for people and developers too. The goal is to make ZEC practical as money you can save, spend, and invest without having to give up privacy whenever you use it.

AxiomAI is where the private agents live, ZEC is their money, and Astrea connects that money to the wider economy.

We’d like your input

AxiomAI is releasing in a few days. Agent budgets and settlement come next, followed by access to external markets and services through Astrea.

We’ll post the download link at @use_axiom. We’d love for people here to try it. In the meantime:

  • Would you keep privacy on across every model, even if turning it off could make responses faster or cheaper?

  • Instead of incentivizing ZEC usage (via discounts), should we go stricter and make payments ZEC-only?

  • What would you need to see or control before giving an agent a ZEC budget? We’re still working through dashboards and spending visibility, and would love to see anything you’ve built or used that works well.

I’ll be replying in the comments. Thank you!

4 Likes

Do the model providers you use also guarantee TEEs? I mean, do the pipes for the upstream providers you rent have confidential computing/TEEs?

If not, then the “privacy” is meaningless, isn’t it? I have seen many providers who do offer crypto-based TEE-enforced models, such as https://ppq.ai, but do you also support them?

3 Likes

sounds pretty cool, “access to external markets” seems like the most interesting part… when is that scheduled for release, and how will that be different than what ships initially?

1 Like

Hi, I’m one of the engineers at Astrea who worked on Axiom.

Our model providers run inference inside TEEs. Axiom establishes end-to-end encryption so that the keys needed to decrypt your content only ever exist locally on your computer and inside the model provider’s attested enclave. Your messages remain encrypted from your machine all the way to the inference environment, and the Axiom backend never has access to their plaintext contents.

Other crypto-friendly TEE inference providers do exist, but the ecosystem is still fairly fragmented. Only some accept cryptocurrency, and the providers I found that accept Zcash use transparent addresses rather than shielded ones. In addition, not every model offered by these platforms necessarily runs inside an attested TEE, so users have to be careful to select the correct model if privacy is important to them.

Using these services as an agent can also involve a fair amount of setup. A typical workflow is to create an account with a provider, fund the account, install and configure its TEE proxy, download a separate open-source coding agent, and configure that agent to route inference through the proxy. If you want to use multiple providers, much of that setup has to be repeated for each one.

The goal of Axiom is to unify all of this into a single private product that is as straightforward to use as ChatGPT or Claude.

You download one desktop app and get everything you need: a chat interface with agentic capabilities, a TUI for people who prefer working in the terminal, ACP support for connecting Axiom to other agent harnesses, and a local proxy for applications that want to use Axiom as their inference backend.

The idea is that users shouldn’t need to understand or assemble the underlying privacy infrastructure themselves. They should be able to download Axiom, choose a model, and get private, attested inference with the same kind of usability they expect from mainstream AI products.

2 Likes

Before giving an agent a budget, I’d want a clear spending limit, approval for larger payments, and an easy way to pause spending. A simple breakdown of what it spent and why would help too.

1 Like

Really interesting direction. One thing I’m curious about: how do you see this relating to x402 and the broader HTTP-native agent payment model?

The use case you describe is an agent discovering a service, paying for it autonomously, and continuing the task this feels very similar to what x402 is trying to enable.

Do you see Astrea/Axiom eventually supporting an x402-like flow with shielded ZEC as the settlement layer, or does the privacy requirement fundamentally change the payment/authorization model?

Would be especially interested in how you’re thinking about this for agent-to-agent payments.

1 Like

Thanks for the question! I’m zkpixels, one of the cofounders of Astrea/AxiomAI.

Yes, x402 is something we’re interested in! We are very familiar, and supporting it through a proxy is a path we could take as Astrea develops. That said, we see x402 as one of the many ways in which agents will transact. Paying for an API call or another agent’s work is a useful starting point, but agents will also need to manage budgets, coordinate across services, and interact with markets over longer tasks that possibly go beyond x402. That’s the broader direction we are building toward with Astrea, with privacy extending to the instructions and activity in all programmable markets.

The question we want to work through is essentially how to make x402 or other primitives useful while preserving privacy across the full interaction. Funding an existing x402 payment from ZEC and settling directly in shielded ZEC are two different paths, and we are open to exploring both.

Please keep the questions coming! Thanks again

1 Like

Yes this is all going to be possible via AxiomAI!

For us though, what’s more exciting than merely setting constraints is zooming out and envisioning the future in which agents will be the primary way everyone manages digital assets, instead of wallets. Would be magical

2 Likes

this is the holy grail. if agents/ai “manage” and obfuscate away all of the crypto idiosyncrasies, then crypto will finally finally have its breakout moment.

1 Like

AxiomAI is live! Please find additional information here at the Axiom website.

The desktop app is available for download, and accounts can be topped up with shielded ZEC as needed.

Looking forward to your feedback!