In AI developer culture, "meatbody" is an emerging term for a human being acting as an execution layer for an AI system. Where digital agents can process, reason, and decide — they cannot physically touch the world.
A meatbody bridges that gap. They are the last mile of the AI supply chain: picking up packages, witnessing documents, pressing buttons, scanning barcodes, verifying locations, or simply confirming that a thing in the physical world is what the digital world believes it to be.
The term carries cultural weight — darkly funny, technically precise, and increasingly used across AI alignment circles, developer communities, and speculative tech discourse.
The intelligence problem in AI has largely been solved. The physical problem has not. AI agents can book, plan, reason, negotiate, and decide — but they cannot touch a doorknob, hand over a form, or confirm with human eyes that a package arrived.
This creates a structural dependency. Every autonomous AI operating in the physical world will eventually require a human to complete its loop. Not as a supervisor — as an executor. That executor is a meatbody.
The gig economy was humans working for platforms. The meatbody economy is humans working for agents. The distinction matters. AI systems do not hire through HR — they dispatch tasks through APIs. Humans who fulfill those tasks are a new class of worker with a new kind of employer.
This market is nascent but structurally inevitable. As autonomous agents expand their operational scope, the demand for trusted, on-demand human execution will grow. Companies will be built specifically to supply this layer.
The category needs a name. It has one.
The infrastructure required to support this layer does not yet exist at scale. What will be built: dispatch networks, identity verification for human workers, reputation systems, liability frameworks, and real-time coordination between AI agents and human executors.