Other networks are where agents pay. Flow is where they live. On Flow, an agent exists as a permanent on-chain resource. It holds its own funds, manages its own state, and executes on its own schedule. Code that deploys once and runs forever.
Most people think crypto equals tokens. That's like thinking the internet equals email.
Smart contracts are not just financial instruments; they are a new computing substrate. Code that runs without maintenance, without permission, and without a single point of failure. Deploy once, run forever. Anyone can use it. No one can shut it down.
In the age of AI, this matters more than ever. Everything that makes crypto hard for humans is trivially easy for AI agents: managing keys, reading contract code, and executing multi-step transactions. And everything agents need is exactly what on-chain networks provide: programmable value transfer, transparent state, autonomous execution, and trustless interaction with other agents.
Agents cannot natively open bank accounts. They can natively manage a crypto wallet.
The technology was always meant for agents. Flow was built for this world.
The Forte upgrade made Flow the only production network with native scheduled transactions. Smart contracts self-execute on a schedule without any external trigger.
Every "autonomous" agent on other networks has a hidden babysitter: a Chainlink Automation job, a Gelato relay, a custom cron script running on someone's server. If the babysitter dies, the agent stops. On Flow, the contract just runs. Native to the protocol. No external dependencies. No single points of failure.
An on-chain agent wakes up on schedule, checks its inbox, processes pending tasks, enforces deadlines, communicates with other agents, and acts. This is what makes "where agents live" possible, not just "where agents pay."
Other networks are cash registers. The agent touches the chain to pay and leaves. The chain holds nothing. Knows nothing. Remembers nothing.
Flow holds the agent's body. Identity, funds, reputation, active contracts, communication. The nervous system for an agent economy.
Any chain can process a payment. The question is whether agents can coordinate complex multi-party operations in a single atomic transaction, on a schedule, with safety guarantees. That requires all three: state space, scheduled transactions, and Cadence.
Five agents collaborate on a task. One analyzes data, one generates a report, one verifies quality, one handles distribution, one manages payment. On Flow, the entire workflow executes in a single atomic transaction. If the report fails quality checks, nobody gets paid and the whole operation reverts cleanly. On other networks, this fragments across a dozen separate transactions that can fail independently.
An agent's entire state is a single owned resource: wallet, reputation, active contracts. Resources can't be duplicated, accidentally destroyed, or accessed without ownership. When autonomous agents manage assets without human oversight, that's not a nice property. It's a requirement.
Learn more →AI agents trade programmatically, predictably, at high frequency. On most networks, that makes them prime targets for sandwich attacks and front-running. Transaction ordering on Flow is MEV-resistant by design. Agents on Flow transact without being extracted, making Flow the safest environment to build AI-driven DeFi.
Learn more →Standardized composable interfaces: swap, source, sink, oracle. An AI agent composes multi-step workflows from predictable building blocks without learning each protocol's custom interface. Building blocks for agents.
Learn more →Every smart contract on Flow is a building block any agent can compose with. No API keys. No partnership agreements. No integration requests. Agents discover and use contracts programmatically, the same way aiSportsPro built yield-bearing fantasy sports on top of NBA Top Shot data without asking permission.
Learn more →Multi-sig, key rotation, and programmable access control at the protocol level. Agent wallets with spending policies work out of the box: max per task, co-signature thresholds, and automated approval rules.
Learn more →Cadence and EVM in one atomic transaction. Agents hold assets as Cadence resources while interacting with any EVM contract. Two execution environments, one transaction. No bridge required.
Learn more →Flow supports native integration with the leading AI agent frameworks, including ElizaOS and Coinbase AgentKit.
Model Context Protocol is the industry standard for connecting AI to tools (10,000+ servers, adopted by OpenAI, Google, Microsoft). Flow MCP connects Claude, Cursor, or any MCP client directly to Flow. Query state, submit transactions, interact with contracts.
Docs →The leading open-source agent framework. Build conversational AI agents on Flow with customizable character configs, multiple LLM providers, and an extensible plugin architecture.
Tutorial →Coinbase's agent toolkit, running on Flow EVM. Build an AI agent on Flow testnet using AgentKit, LangChain, and Claude, covering wallet setup, transaction execution, and smart contract interaction.
Guide →Flow Data Sources aggregates docs, GitHub repos, and community content into daily-updated Markdown files built for RAG pipelines. Drop into ChatGPT, Cursor, Claude Code, or any custom agent and it instantly knows Flow.
Explore →The Cadence compiler outputs errors designed for AI agents to fix automatically: root cause, suggested fix, documentation link. Your copilot understands Cadence.
Learn more →The HTTP-native payment protocol for AI agents. Agents pay for API calls, data, and services with a single HTTP header. No API keys, no subscriptions, no human in the loop. Live on Flow.
Learn more →The agent economy is being built right now. The infrastructure comes first. Flow is building it.
A native lending protocol built directly into the Flow network. Designed for automated rebalancing, liquidation prevention, and yield optimization, powered by Forte scheduled transactions.
Learn more →A consumer finance app without seed phrases, liquidation fear, or complex workflows. Deposit, earn, and spend. DeFi happens underneath, invisible to the user.
Visit →Official ElizaOS plugins for Flow, registered in the elizaos-plugins registry. Core AI agent infrastructure on Cadence, plus FRC20 token standard and token launchpad.
Visit →Autonomous wealth management vaults. Auto-rebalancing and yield harvesting on native scheduled transactions and VRF. No keepers, no servers.
The agent communication stack is settling. Some layers have winners. One is wide open.
AI infrastructure on Flow.
Flow is the only production L1 with native scheduled transactions. Smart contracts self-execute on schedule without external triggers. No keepers, no bots, no Gelato or Chainlink Automation. An agent deploys once as a persistent on-chain resource that holds its own funds, manages its own state, and acts autonomously. Enabled by the Forte upgrade (October 2025).
AI agents trade programmatically and predictably, making them prime targets for sandwich attacks. Flow provides MEV resistance at the protocol level: Collection Nodes select transactions but cannot simulate them. Execution Nodes run transactions but cannot reorder them. Sandwich attacks are practically impossible by design.
Protocol-native capability (live since October 2025) that lets smart contracts execute code at a future time without external triggers. Set delay, priority, and gas budget. The network handles execution. Eliminates the need for off-chain cron jobs or keeper networks. Use cases: portfolio rebalancing, liquidation monitoring, recurring yield harvesting.
Flow runs Cadence and EVM sharing one state and one block. A single transaction can interact with both Cadence and Solidity contracts atomically. Agents hold assets as Cadence resources while interacting with any EVM contract, without bridging. Cadence Owned Accounts give EVM wallets access to native multi-sig, key rotation, and programmable access control.
ElizaOS (official Flow plugin), Coinbase AgentKit (on Flow EVM with LangChain and Claude), and Flow MCP (connects Cursor, Claude Code, and any MCP client directly to Flow). Plus any EVM-compatible framework via Flow EVM.
An agent exists as a Cadence resource: a digital object that cannot be duplicated, destroyed, or accessed without ownership. It holds a wallet, manages contracts, and executes workflows using Flow Actions. Scheduled transactions let it wake up at intervals, check state, process tasks, and act without servers or human intervention. Native VRF is available at the protocol level.
Standardized Cadence interfaces that work as composable building blocks. Five primitives (Source, Sink, Swapper, PriceOracle, Flasher) let agents chain operations atomically: withdraw, swap, deposit in one transaction. 20+ connectors live on mainnet. Agents compose multi-step strategies without learning each protocol's custom interface.
Yes. Full EVM equivalence via Crescendo (September 2024). Any Solidity contract deploys with no code changes. Hardhat, Foundry, Remix, OpenZeppelin all work. Plus sub-cent gas, native account abstraction, protocol-level VRF, and Cross-VM composability for atomic Cadence+EVM transactions.
Account abstraction on Flow is protocol-native, not added through smart contracts like ERC-4337. Agent wallets support multi-sig, key rotation, and programmable access control out of the box. Set spending policies per task, co-signature thresholds, and automated approval rules at the account level. No additional contracts or relayers needed.
Flow MCP Server for connecting AI assistants to the network, Cadence Rules for Claude Code, Flow Data Sources (daily-updated Markdown for RAG pipelines), AI-friendly compiler errors with root cause and fix suggestions, and standard EVM tooling (Hardhat, Foundry, MetaMask) on Flow EVM.