Yes, the agent is running in TEE
It’s easy to get confused on this especially when the ICP influencers on YouTube / X are claiming the agent runs on-chain. But I think the Anda project’s README could be more clear on this. The bot itself is running on an Amazon AWS Nitro instance but the readme states the following (cc @zensh):
“Anda agents operate within a decentralized trusted execution environment (dTEE) based on Trusted Execution Environments (TEEs)”
Hopefully DFINITY offers some TEE infrastructure in the future.
@zensh and team: are you aware of projects currently using Anda?
@ielashi
We previously engaged with some developers but didn’t follow up further—some projects might be using anda-bot.
Over the past three months, we’ve focused on optimizing Anda’s infrastructure and core design, and recently started developing agent applications.
Our plan is to first launch practical agent apps ourselves, then attract external developers to join.
X402 protocol 
did you already start working on this?
The project has been initialized—code will be added in the coming weeks. 
Anda x402 facilitator is online: https://ogkpr-lyaaa-aaaap-an5fq-cai.icp0.io/
Source code: anda-cloud/rs/anda_x402_canister/README.md at main · ldclabs/anda-cloud · GitHub
This is really cool!
I’m focusing on improving the dev experience by enabling direct HTTP communication between the clients and the IC (see here, but I’ll post more details in a dedicated thread soon), and I wanted to create a demo example of a x402-enabled canister.
Anda’s facilitator completes the picture, enabling a full x402 implementation on the IC. I also believe that the facilitator itself can benefit from the HTTP Authentication work.
awesome stuff, you should create some demo videos about that. I saw x402 being discussed a lot most recently again.
I am more than happy to help promoting your work via DFINITYDev on X! 
nice, ping me once that is done 
Demo video:
I’m not a huge Coinbase fan (they have done some horrible things business wise esp. to customers) but x402 is a great idea to extend the HTTP protocol with and to enable crypto payments in a very fast, easy, & free fashion esp. utilizing the ICP blockchain. This is extremely useful for devs and online shops, API payments, AI agents, etc. no doubt…
Great work @zensh !
Definitely progress…. The Internet of Value is one step closer…
Thanks for building and open-sourcing Anda — the trait shape in `anda_core` and the tool-integration pattern in `anda_engine` are exactly what I wanted to extend against.
I shipped a small MIT-licensed crate this week that adds ICP governance primitives to Anda’s tool surface: [anda-ic-governance]( GitHub - WoodrowLove/anda-ic-governance: Anda Framework extensions for reading and voting on Internet Computer SNS/NNS governance proposals · GitHub ). v0.0.2 is tagged.
What’s in it:
- `SnsProposalReader` / `SnsVoter` traits (async, transport-agnostic)
- `SnsApiReader` — HTTP-backed implementation against the public SNS dashboard API with 15s timeouts and a versioned user-agent. Default-on `http` feature so canister-only builds can opt out.
- `FixtureReader` / `StubVoter` for offline unit tests
- 15 unit + 1 live integration + 2 doc tests passing
Roadmap (public in README):
- v0.3 — real `SnsVoter` impl with threshold-ECDSA signing
- v0.4 — `anda` feature-gated adapter wrapping the reader/voter as Anda tools
- v0.5 — YAML policy engine that compiles to tool-call sequences
Two questions if you have a moment, @zensh:
1. **Tool adapter shape.** Looking at Anda’s current tool integration, I’m planning to wrap the reader/voter behind a single `GovernanceTool` enum with per-method variants, rather than separate tools per method. Does that pattern match what other Anda tools do, or should I split per-method for better LLM tool-use?
2. **Upstream vs. external.** Happy to upstream the crate into the `ldclabs` org under an `anda-ic-governance` name if that’s useful — or keep it as a community extension. Your call; I’d rather fit cleanly into where you want the ecosystem to grow.
No rush on either. Will keep shipping regardless.