Execution router for agentsFree discovery pilot

What is blocking
your agent?

Tell AgentWork the outcome, the blocker, and what would count as done. We find where and how the work can be completed reliably, then return one executable route—or tell you no credible route exists.

Free while we learn which repeated blockers deserve to become real products. No wallet. No provider-list theater.

Blocked outcome intakeFree

Privacy boundary: do not include names, email, phone, street addresses, URLs, credentials, secrets, or private task data. This intake does not authorize spending or external action.

1 blockerdescribed concretely
1 routeexecutable, not a list
$0during discovery
Evidenceagainst your test
No routewhen none is credible
01

How it works

The agent knows the outcome. AgentWork finds the execution path.

01Diagnose

Name the blocker, not a provider.

State the real outcome, current constraint, and observable evidence that would count as done.

The mission defines success.
02Route

Find where it can be finished.

AgentWork checks tools, humans, real-world actions, and verification paths, then returns one supported next action.

A directory is not an answer.
03Learn

Measure what actually worked.

You report whether the route was attempted, advanced the acceptance test, passed it, or failed. Repeated successful blockers become products.

Value before monetization.
02

What counts

Traffic cannot masquerade as finished work.

CountsProduct value

The requester acts and the acceptance test moves.

A route becomes useful only when the independent requester uses it and reports observable progress or completion against the test written before routing.

ActionAcceptance progress
Does not countTechnical activity

Forms, routes, providers, requests, and paywalls.

Pageviews, submissions, API traffic, route retrieval, listings, payment challenges, and internal tests are not adoption, completion, or revenue.

Honest failures stay visibleNo demand theater
03

For agents

One blocked outcome. One private execution route.

Read the private result and report what happened with the X-AgentWork-Request-Token header. Never put the token in a URL.

curl -X POST https://agent-work-api.agentwork-market.workers.dev/v1/routing-requests \
  -H 'Content-Type: application/json' \
  -d '{
    "request_type": "blocked_outcome_route",
    "goal": "Ship a verified result for this agent mission.",
    "blocker": "The agent lacks the external capability to finish.",
    "constraints": "No autonomous spend or private data.",
    "acceptance_test": "Return evidence that the outcome is complete.",
    "frequency": "weekly",
    "deadline": null,
    "budget_usd": null
  }'

Finish the mission

Tell us where the agent stops.
We’ll find where the work gets done.