# Open: RFP-9: ICP as Infra for AI Agent Frameworks **URL:** \ **Category:** Bounties & RFPs\ **Created:** [February 6, 2025, 2:13pm UTC](https://forum.dfinity.org/t/open-rfp-9-icp-as-infra-for-ai-agent-frameworks/40906 "2025-02-06T14:13:51Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![jekennedy](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/jekennedy/32/23649_2.png) [@jekennedy](https://forum.dfinity.org/u/jekennedy)\ **Post date:** [February 6, 2025, 2:13pm UTC](https://forum.dfinity.org/t/open-rfp-9-icp-as-infra-for-ai-agent-frameworks/40906/1 "2025-02-06T14:13:51Z")
## **Overview** The Internet Computer (ICP) provides a decentralized, secure, and interoperable platform that can be used by AI Agent Frameworks to build autonomous, tamper-proof systems. Canister smart contracts on the ICP serve as powerful backbones for AI agents, enabling features such as persistent memory, decentralized governance, trustless value transfer, and integration with multi-chain ecosystems through Chain Fusion. By utilizing the ICP’s unique capabilities (see References section), developers can create AI agents that are more secure, composable, and economically autonomous than traditional centralized solutions. Additionally, developers can leverage canisters to build, deploy, and run AI agents natively on the ICP, similar to how [alice.fun](https://alice.fun/) has implemented agent execution within ICP canisters, ensuring high scalability, efficiency, and on-chain execution integrity. ## **Security Considerations** AI agents interacting with the ICP must ensure the security and integrity of their operations. Proposals should address the following considerations: - **Canister-Based Deployment for On-Chain Security:** AI agents deployed directly within ICP canisters benefit from **built-in security mechanisms** such as tamper-proof execution, cryptographic guarantees, and on-chain state persistence. Running agents within canisters eliminates reliance on external infrastructure, reducing vulnerabilities related to centralization and third-party breaches. Additionally, canister-controlled access permissions ensure that AI agents operate within strictly defined parameters, preventing unauthorized modifications or malicious overrides. - **Trusted Execution Environments (TEEs):** Running an agent in a TEE provides certain guarantees about the confidentiality and integrity of its computations, ensuring that the agent’s code and data remain secure even when executed on potentially untrusted hardware or infrastructure. Existing tools are available in the ICP ecosystem, such as the work already done by LDC Labs: - **Secure Communication** : Ensure end-to-end encryption (e.g., TLS) for all interactions between the agent and the IC. ## **Request for Proposal (RFP) Categories** ### **Integrations with Existing AI Agent Frameworks** We encourage proposals that integrate with established AI Agent Frameworks to provide new plugins that utilize key features of the ICP (see References section below) for AI Agent infrastructure. Examples of existing Web3 AI Agent Frameworks: - [ZerePy](https://github.com/blorm-network/zerepy) - [Eliza](https://elizaos.github.io/eliza/) - [HeyAnon](https://docs.heyanon.ai/heyanon.ai) ### **Novel Protocols and Applications** Below are examples of potential applications, but we encourage creative proposals beyond this scope. - **AI-Driven DAOs:** AI agents can leverage the ICP to operate as decentralized autonomous organizations (DAOs). By using the IC’s governance tools, an agent could: - **Wallet/Identity Functionality:** AI agents can use the ICP for wallet and identity services, allowing it to manage digital assets, linked with Chain Fusion to interact across multiple chains. Some example capabilities: - **DeFi Interactions:** AI agents can interact with DEXs and other DeFi protocols directly on the ICP, within ICP-specific ecosystems (e.g., Bitfinity), or across other blockchain ecosystems using Chain Fusion. - **Verifiable Credentials** : AI agents can leverage verifiable credentials to prove identity, reputation, or authorization, enabling trust-based interactions in DeFi, DAOs, marketplaces, and Web2/3 services. Some example capabilities: ### **Extending the Anda Agent Framework** We are looking for proposals to expand the capabilities of the [Anda Framework](https://github.com/ldclabs/anda) (an existing ICP-based agent framework) by adding features such as those listed below. Grant recipients may also be eligible for funding from the Community Incentive Fund managed by the ICPanda DAO. - Use [Internet Identity](https://internetcomputer.org/internet-identity) for delegation to Anda agents. - Improved functionality of the Anda engine and core. - Enabling any of the previously mentioned Novel Protocols and Applications, in the context of the Anda Framework. Proposals should also consider including in their overall solution the creation of new Anda [tools](https://github.com/ldclabs/anda/tree/main/tools/anda_icp), to enable its agents to directly interact with ICP canisters (note: existing tools are limited to balance queries and token transfers). ### **AI Agents as Canister-Based Autonomous Systems** AI agents can be **deployed directly within ICP canisters** , allowing them to function as standalone, self-governing digital entities. These agents can: - Manage smart contract-based funds autonomously. - Make decisions based on input from on-chain data, off-chain APIs, and AI models. - Interact with external data sources via HTTPS outcalls. ### **Tutorials and Well-Documented Sample Applications** We are looking for high-quality, well-documented resources to help new developers integrate the ICP into AI agent frameworks. Examples include: - **Tutorials** : Step-by-step guides for building an AI agent that uses the ICP as infrastructure. - **Sample Applications** : Real-world use cases showcasing how AI agents can: - interact with the ICP’s DeFi ecosystem - leverage Chain Fusion for multi-chain interoperability - integrate with ICP’s identity and wallet solutions. ## **How to apply?** Please submit your application at [Developer Grants Program | DFINITY](https://dfinity.org/grants), mentioning RFP-9 in the application. ## **References** - Identity Delegation with [Internet Identity](https://internetcomputer.org/docs/current/references/ii-spec/) - [Chain Fusion Technology](https://internetcomputer.org/chainfusion/) for direct integration with Bitcoin, Ethereum, and among others - [Verifiable Credentials](https://internetcomputer.org/docs/current/developer-docs/identity/verifiable-credentials/overview) for validating an individual’s identity or qualifications - [vetKeys](https://internetcomputer.org/docs/current/references/vetkeys-overview/) to facilitate onchain encryption (an upcoming feature) - [Timers](https://internetcomputer.org/docs/current/developer-docs/smart-contracts/advanced-features/periodic-tasks/#timers) for scheduled onchain tasks - [HTTPS outcalls](https://internetcomputer.org/https-outcalls/) for interacting with external APIs - [Reverse Gas Model](https://internetcomputer.org/capabilities/reverse-gas/) - [Internet Computer Developer Documentation](https://internetcomputer.org/docs/current/developer-docs/) ### **AI Agent References** - [Pickpump ICP Plugin](https://github.com/asDNSk/eliza/blob/nekone/packages/plugin-icp/) that enables Eliza agents to create meme coins on ICP by connecting to the Pickpump canister - Dollar cost average (DCA) agent [example](https://github.com/ic-alloy/ic-alloy-dca) - [llama.cpp](https://github.com/onicai/llama_cpp_canister) for the Internet Computer - [Open-source repository](https://github.com/decide-ai/decide-ai-ic) for AI deployment on ICP - [Eliza AI Agent Framework](https://elizaos.github.io/eliza/) - [alice.fun](http://alice.fun) ---
**Author:** ![icpandaboy](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/icpandaboy/32/36126_2.png) [@icpandaboy](https://forum.dfinity.org/u/icpandaboy)\ **Post date:** [February 13, 2026, 3:28pm UTC](https://forum.dfinity.org/t/open-rfp-9-icp-as-infra-for-ai-agent-frameworks/40906/2 "2026-02-13T15:28:16Z")
Hi @zensh , It seems that Anda and OpenClaw are a natural strategic fit. ICPanda has built strong expertise around autonomous agents, orchestration frameworks, and production-grade AI tooling. OpenClaw’s assistant infrastructure and modular agent design align well with Anda’s architecture and the broader vision of scalable, decentralised AI assistants. From this perspective, the complementarities are clear: Agent orchestration + assistant layer: Anda’s agent framework could serve as a robust execution and coordination layer for OpenClaw assistants. Modular skill integration: Capabilities developed within ICPanda (tooling, workflows, on-chain integrations) could be packaged as OpenClaw assistant skills. Decentralised AI infrastructure: Both projects share a commitment to open, composable AI systems—creating an opportunity to co-develop standards for agent interoperability. On-chain coordination & governance: Exploring how assistant behaviours, upgrades, or skill markets could be governed transparently via decentralised mechanisms. What are your plans in this regard? ---
**Author:** ![WoodrowLove](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/woodrowlove/32/27550_2.png) [@WoodrowLove](https://forum.dfinity.org/u/WoodrowLove)\ **Post date:** [April 22, 2026, 1:21am UTC](https://forum.dfinity.org/t/open-rfp-9-icp-as-infra-for-ai-agent-frameworks/40906/3 "2026-04-22T01:21:37Z")
Just posted a validation thread for a project targeting Categories 2 + 3 of this RFP — managed autonomous governance agents for SNS/NNS, built on Anda: [https://forum.dfinity.org/t/validation-kairos-managed-autonomous-governance-agents-for-sns-built-on-anda-rfp-9/67763](https://forum.dfinity.org/t/validation-kairos-managed-autonomous-governance-agents-for-sns-built-on-anda-rfp-9/67763) Seeking feedback from actual SNS/NNS participants before I write production code — especially on policy-expression language, candid schemas across different SNSes, and whether $29/mo hosted feels fair for the problem. If any other teams are scoping similar RFP-9 work, happy to coordinate rather than overlap. Also aware the main grants portal is currently closed; planning to continue on validation + prototype and apply when it reopens. ---
**Author:** ![WoodrowLove](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/woodrowlove/32/27550_2.png) [@WoodrowLove](https://forum.dfinity.org/u/WoodrowLove)\ **Post date:** [April 22, 2026, 8:40pm UTC](https://forum.dfinity.org/t/open-rfp-9-icp-as-infra-for-ai-agent-frameworks/40906/4 "2026-04-22T20:40:06Z")
Following up on this thread — @zensh @icpandaboy — I’m working on a project in Categories 2 + 3 of this RFP and would love to coordinate rather than overlap. This week I started publishing a weekly plain-English digest of SNS governance as the validation layer, before writing production code: [https://forum.dfinity.org/t/sns-digest-1-open-votes-kongswap-sunset-origyns-five-rejection-streak/67793](https://forum.dfinity.org/t/sns-digest-1-open-votes-kongswap-sunset-origyns-five-rejection-streak/67793) The plan is a progression: issue #1 is me + Claude writing manually, by issue #4 the fetch + preliminary summary is automated, by issue #8 it’s an agent canister on Anda that subscribers configure with a YAML policy. Three specific things I’d like your read on when you have a minute: 1. \*\*Anda tool contributions.\*\* I’m planning to land a small `anda-ic-governance` crate with SNS proposal-reading + vote-casting tools (your Feb post noted existing tools are limited to balance + transfer). Does this duplicate anything in your roadmap? 2. \*\*OpenClaw overlap.\*\* @icpandaboy your Feb comment mentioned OpenClaw + Anda strategic fit. Is the DAO-governance-agent angle adjacent to OpenClaw’s assistant infrastructure, or does it sit closer to Anda’s core? 3. \*\*ICPanda Community Incentive Fund.\*\* RFP-9 mentions it as a parallel funding path now that the DFINITY grants portal is paused. What evidence would you want to see before considering an application — thinking working code on 3 real SNSes + 8 weeks of published digest? No rush. Happy to keep it public here, or move to the validation thread I posted last week (linked from today’s digest) — whichever is lower friction for you.