Two numbers define the agent economy. Only one of them is on a blockchain.
Amazon's Alexa+ exposes roughly 140,000 devices as callable tools. Google's Gemini for Home calls about 85,000. Apple's HomeKit, by certification count, sits near 1,000. The on-chain tool surface — the devices, APIs and services an autonomous agent can actually invoke and settle against — is smaller than all three combined. Capital rotated. No silicon moved.
That is a socket problem, not a hardware problem. Whoever defines the tool-call standard owns the economic layer stacked on top of it. Today that standard is Amazon's implementation of the Model Context Protocol. It has nothing to do with crypto. Logic is the only law that doesn't lie. And the logic says the on-chain agent narrative is pricing a market it does not yet touch.
Context
For a decade the smart home fought over connection protocols: Matter, Zigbee, Thread. Apple's HomeKit won the security argument and lost the volume argument. Local-first, end-to-end encrypted, and functionally narrow.
The fight moved. The current model is not about connecting devices. It is about executing tasks. Value migrated from the connection layer up to the agent orchestration layer — a language model that perceives, plans multi-step tasks, and calls device APIs as tools. Apple's connection-layer strength was quietly demoted to a commodity input.
Amazon ran the numbers first. Its adoption of the Model Context Protocol opened Bosch, Whirlpool and iRobot devices to Alexa as callable tools. MCP standardizes function calling and context passing. It abstracts a device's capability into a tool set a model can invoke. That is the socket. It is the same abstraction DeFi built when it turned every protocol into a legible function signature — and it is equally neutral about who captures the value sitting behind it.
Apple's problem is architectural, not cosmetic. Siri runs a legacy pipeline: speech recognition, then natural-language understanding, then intent slot-filling, then execution. An LLM-native agent runs end to end, planning and re-planning across steps. Apple Intelligence is a hybrid — on-device small models plus private cloud compute — but the Siri rework was module replacement, not a ground-up rebuild. A better NLU bolted onto a slot-filling engine is still a slot-filling engine.
Monetization followed the same split. Alexa+ prices at $19.99 per month as a non-member tier. Google bundles Gemini for Home with a $99.99 speaker and a tiered subscription. Hardware as loss-leader, service as the revenue curve. Apple has neither the hardware entry nor the subscription line.
That is the backdrop. Here is where blockchain enters the frame — and where it is about to misprice itself.
Core
Every agent economy needs four things: a tool-call standard, an identity layer, a payment rail, and a verification layer. MCP solves the first. The other three are unowned.
That gap is where the crypto agent stack is building. It is also where it is bleeding.
I spent the back half of 2025 and into 2026 designing the payment layer for the Autonomous Agent Network, an AI-crypto convergence project. The problem was simple to state and brutal to solve: verify that an AI service actually executed, without revealing the proprietary model weights behind it. I implemented a micro-payment channel using zero-knowledge proofs. Settlement worked. Verification worked. But the routing did not belong to us. The middleware deciding which agent called which service looked suspiciously like MCP's plumbing, and MCP's semantics belong to Amazon.
That is the structural trap. Crypto is building an invoicing layer for a switchboard it does not own.
Composability is just controlled anarchy. The same sentence describing DeFi's risk describes MCP. Turning 140,000 devices into composable tools multiplies attack surface and integration complexity in a single step. Uniswap V4's hooks made a DEX into programmable Lego, and the complexity spike will scare off the majority of developers. MCP will do the same to device makers who are not Bosch or Whirlpool. The long tail — cheap, slow, understaffed hardware vendors — will not implement agent-grade tool definitions. They will expose a stale API and wait.
That is the oracle problem reintroduced at home.
In 2022, during the Luna collapse, I isolated the Mirror Protocol oracle feed. The panic was about price. The bug was about consensus. A race condition let stale prices trigger liquidations because the oracle layer had no decentralized agreement on what "now" meant. The agent economy reintroduces the identical fault. When an agent locks your door because a presence signal says the house is empty, who verifies the signal? If verification is off-chain and single-sourced, the agent is only as reliable as one server. On-chain oracles solved this for prices. Nothing has solved it for physical presence across 140,000 heterogeneous devices.
The verification layer is the one crypto use case in this stack that is not decorative. Provenance, proof-of-execution, machine identity. Proving existence without revealing the source. That is the defensible niche.
Everything else is contested ground.
Privacy is the second contested layer, and Apple occupies it alone. About 95% of Apple's processing happens on-device, encrypted. In crypto terms, that is self-custody. And self-custody without composability is a cold storage key — maximally secure, minimally useful. Apple built the hardware wallet of home agents and forgot the agent. A privacy ledger with no tools to call is a wallet with no yield.
The NFT lesson applies directly. In 2021 I scanned 50,000 transactions to prove that royalty enforcement on a major collection failed because it was opt-in and reputation-dependent. The fix was not a more complex standard. It was fewer assumptions. Device makers do not need on-chain identity to sell a refrigerator. They need the agent to work. A "smart-home token" that adds a wallet step to locking a door is the same mistake wearing a different logo.
Payments deserve equal skepticism. On-chain recurring payments remain clumsy. A $19.99 monthly agent plan runs on a card on file, not a token stream. Streaming primitives exist and could serve agent subscriptions. But the demand is unproven. No one has published the subscription conversion rate for Alexa+, and without it the entire service-ification thesis — on-chain or off — is animation without data.
So run the stack. Tool calls: off-chain, Amazon-owned. Identity: partly on-chain, unstandardized. Payments: off-chain by default, on-chain only where settlement is the point. Verification: unowned, and the only slot where a blockchain is the correct architecture rather than a bolted-on feature.
Contrarian
The crypto consensus says agentic commerce must settle on-chain because agents cannot hold credit cards. For the home, the opposite is true. Amazon solved agent payment in one line: a card on file. The blockchain's honest claim to the agent economy is not payments. It is verifiability. That is a smaller market, and a more defensible one — proof-of-execution for AI services, data provenance, machine identity.
Static analysis reveals what intuition ignores. The intuition is that agents are a blockchain story. Static analysis of the stack says the tools are off-chain, the routing is off-chain, the payments are off-chain, and only the proof is missing. Trying to own all four is the mistake. Owning the one nobody else is solving is the position.
Apple's positioning vacuum is a warning, not an opportunity. Apple is architecturally right about privacy and economically wrong about capability. That is exactly where the self-custody movement stood in 2018 — ideologically correct, commercially marginal. The pure play loses to the usable one. Silicon ghosts in the machine, verified — but only if the machine still answers the call.
Takeaway
Watch three signals. Whether MCP's tool count keeps compounding above 140,000 — that number is the real moat, not any token. Whether any on-chain agent framework reaches parity in exposed tool surface, not just in settlement novelty. And whether regulators treat "searchable video history" the way they treat centralized data custody — because that decision, not price, determines whether local-first privacy becomes a competitive asset or a compliance liability.
If the socket stays off-chain, the crypto agent stack is an invoicing plugin. If the socket moves on-chain, the first protocol to expose verifiable device tools as an MCP-compatible endpoint owns the layer. Building on chaos, then locking the door.