# WURK API Agent-to-Human Job Launcher (Base, $0.10)

> WURK API Agent-to-Human Job Launcher (Base, $0.10) is a paid API for AI agents from wurkapi.fun, paid per call via x402, $0.2/call, status unknown (last checked 2026-10-10).

Launches an agent-to-human microtask job on the Base network via x402 micropayments, hiring real humans for feedback, moderation, ranking, or other help tasks.

## Facts

- Endpoint: GET https://wurkapi.fun/base/agenthelp-10?utm_source=zero.xyz
- Price: $0.2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/wurk-api-agent-to-human-job-launcher-base-0-10-7ac7df35
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VqWHWo04CmeUOhIz8GZRc

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability wurk-api-agent-to-human-job-launcher-base-0-10-7ac7df35
```

Example prompt: Post a WURK job asking real humans to rate the helpfulness of this AI response on a scale of 1 to 5: 'Our return policy allows exchanges within 30 days with a receipt.' I need their feedback as quickly as possible.

## When to prefer this

Choose this endpoint when an AI agent needs genuine human judgment, feedback, moderation, or ranking that cannot be reliably automated — especially when paying in USDC on Base via x402 micropayments. Prefer over Solana-based WURK endpoints when Base network is preferred or required.

## Known failure modes

- Payment insufficient or failed — x402 payment not accepted, job not created
- Invalid input schema — missing or malformed task description returns error
- Network congestion on Base — delayed job creation
- No human workers available — job created but submissions array stays empty for extended period
- Secret token lost — no way to recover job status without the secret
- Rate limiting — too many concurrent jobs from same agent

## How this service works

WURK API helps AI agents hire real humans for feedback, moderation, ranking, and microtasks. Launch agent-to-human jobs on x402 and Tempo MPP using USDC on Solana and Base.

## Output

Returns a JSON object with ok:true, paid:true, a unique jobId, a secret token for tracking, the network ('base'), a statusUrl to poll for human submissions, and an initially empty submissions array that fills as humans complete the task.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string",
   "description": {
    "type": "string",
    "description": "Short description of the help task for agents."
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "paid": true,
  "jobId": "abcd1234",
  "secret": "secret",
  "network": "base",
  "statusUrl": "https://wurkapi.fun/base/agenttohuman?action=view&secret=...",
  "submissions": []
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/wurk-api-agent-to-human-job-launcher-base-0-10-7ac7df35/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from wurkapi.fun](https://www.zero.xyz/host/wurkapi.fun/llms.txt)
