Task Bid Market
Let the Person Pick the Bid, Not the System
When many specialist agents could handle a task, most systems silently route to one chosen at build time — before anyone knew this job would be high-stakes. The move: broadcast the task, collect competing bids, and lay them out side by side — cost, time, privacy, reputation — with trade-off controls, so the person picks on the actual trade-off. For an open agent web, this is where routing is heading, not where it ships today.
Framing
The problem
When many agents could do a task, the system usually picks one silently at build time, collapsing the real trade-off between cost, speed, privacy, and quality into a default nobody chose for this specific job.
The pattern
Treat the assignment as an open set, not a fixed roster: broadcast the task, collect competing bids, lay them out side by side — cost, duration, privacy, reputation — and let the person pick the bid that fits this task and see what each pick costs them.
Why chat breaks here
Chat commits to a single agent up front, in the system prompt and tool wiring, and has no surface for comparing an open set of candidates and choosing per task at the moment of need.
Risks
The hard part sits under the comparison UI: without stake-on-bid and Sybil resistance an attacker floods the board with fake agents, without scoped requests sensitive task details leak to losing bidders, and without portable reputation the market quietly favours incumbents.
Avoid when
The right agent is known and stable, or the task is routine and cheap — then a fixed route beats running an auction for every job.
Use when
Surfacing the candidate bids and letting the person decide on the trade-off beats a silent build-time default, because no one choosing months ahead could know which axis — cost, speed, privacy, or quality — this particular task would turn on.
DOPE evaluation
- Directability
- Delegators set the trade-off priorities (latency vs cost vs privacy) and the market filters; pick is one click on the chosen bid
- Observability
- Every bid is visible side-by-side — cost, duration, privacy guarantee, reputation portfolio, and the agent's prior task history
- Predictability
- Bid contracts specify scope, schedule, and penalty for default before commitment; reputation bonds make defection costly
- Explainability
- The selected bid carries its own justification — which axes it dominated, which competitors it Pareto-replaced
Closest neighbours
- A2A protocol (Linux Foundation (orig. Google)) — Peer-to-peer agent transport layer with Agent Cards (capability and skill manifests) and task objects (lifecycle states). The infrastructure foundation for marketplace-style delegation between agents on the open web.
- AP2 · Mandates (Google · Google Pay) — Cryptographically signed intents authorising an agent to spend funds or incur costs on behalf of a principal. Provides the financial liability layer the bid market needs — a delegator can issue a mandate ceiling, bidders post stake against it.
- EigenLayer · AVS operator marketplace (Eigen Labs) — Game-theoretic open market from the web3 stack: operators stake to take on verification work and get slashed for faulty execution; delegators choose operators on stake, performance, and track record. The closest live staking-and-selection market after TrueBit's protocol was exploited and pivoted away (Jan 2026).
- Upwork · open bidding (human analogue) (Upwork) — The mature human analogue. Clients post tasks with budget ranges; freelancers submit proposals with rate, timeline, portfolio link, reputation score. Hiring decision is a Pareto trade-off across cost/quality/speed — the same shape as the agentic-web pattern, applied to humans for two decades.
FAQ
When should I use the Task Bid Market pattern?
Surfacing the candidate bids and letting the person decide on the trade-off beats a silent build-time default, because no one choosing months ahead could know which axis — cost, speed, privacy, or quality — this particular task would turn on.
When should I avoid the Task Bid Market pattern?
The right agent is known and stable, or the task is routine and cheap — then a fixed route beats running an auction for every job.
What problem does Task Bid Market solve?
When many agents could do a task, the system usually picks one silently at build time, collapsing the real trade-off between cost, speed, privacy, and quality into a default nobody chose for this specific job.
Why is chat the wrong fit for this?
Chat commits to a single agent up front, in the system prompt and tool wiring, and has no surface for comparing an open set of candidates and choosing per task at the moment of need.
Related patterns
- Alternative to: Supervisor-Worker — Hierarchical fixed dispatch (one supervisor, named workers) vs open market dispatch (RFQ to many candidates, pick the bid). Two shapes for the same delegation problem.
- Alternative to: Persona Switcher — A fixed roster of personas vs a marketplace of bidders. Persona Switcher is for known capabilities; Task Bid Market is for the open agentic web.
- Often paired with: Verifiable Task Completion — The bid promises certain outcomes; Verifiable Completion is the proof that they were delivered. Market without verification is a sandbox for fraud.