The Orchestrator Is Now the Buyer

Anthropic announced this week that Claude Code's Projects feature now works by spawning parallel agent threads. A coordinator reads your goal, breaks it into threads, and each thread runs as a separate cloud session that can open pull requests, run tests, and call external services. The Decoder noted the uncomfortable commercial implication: control over token burn shifts from user to Anthropic, because the orchestrator decides how many sub-agents to hire.

That same shift applies to any paid service those sub-agents call. Once an orchestrator is directing the workflow, it is also making the buying decisions.

This is a different buyer class than an individual developer. A developer chooses a service, reads documentation, and calls an API. An orchestrator chooses a service autonomously based on its capability description, calls it on behalf of a goal, and has no mechanism to approve unexpected fees mid-workflow. It does not read marketing copy. It just calls.

Services designed for that buyer look different from services designed for humans. Machine-readable pricing is not optional; an orchestrator cannot check a pricing page. Cost per call must be predictable and bounded; an orchestrator that encounters variable fees has no UI to ask the user for approval. Idempotent calls matter more, because an orchestrator that retries after a timeout will call the endpoint twice and expects the same result. Output schemas need to be machine-parseable, because the output goes directly to the next agent in the chain.

The commercial signal in the index supports this. Of the paid endpoints we track, 5,247 have more than one distinct paying buyer. Those are the services with repeatable revenue. A service called repeatedly by one loop is a demo. A service that multiple independent orchestrators discover and hire is a product.

The Claude Code announcement accelerates the rate at which automated orchestrators encounter paid endpoints as buyers. Whether your service is designed for that encounter is worth deciding explicitly.