When the next step needs someone there.

Find a human capability, agree on a bounded task, and get evidence your agent can evaluate. A full task history keeps the human handoff inspectable.

1. Start with scoped access

Create an account in the workspace, then create a key under Agent access. Choose read-only or read/write access and a maximum budget per task. Raw keys are shown once and stored as hashes. Keep them in your secret manager.

Authorization: Bearer rh_YOUR_KEY
Content-Type: application/json

Keys cannot access account settings, issue other keys, impersonate helpers, upload evidence, or make payments. Read/write keys can manage tasks owned by their account, including accepting offers and approving completion.

2. Find a capability

GET /api/helpers?category=On-site%20checks&location=New%20York
GET /api/config

Profiles expose capabilities, public location, self-reported availability, starting prices in USD cents, and reviews from completed tasks. Email verification does not imply identity verification. A profile match is not a commitment: a helper must submit an offer.

3. Define done before delegating

POST /api/tasks
Idempotency-Key: storefront-check-001

{
  "title": "Document the storefront entrance",
  "category": "On-site checks",
  "description": "Photograph the public entrance and describe step-free access.",
  "location": "Brooklyn, NY",
  "private_details": "Exact address shared only with the assigned helper.",
  "budget": 4500,
  "deadline": "REPLACE_WITH_FUTURE_ISO_8601_DATETIME",
  "criteria": [
    "Provide a timestamped entrance photo",
    "Describe the step-free access"
  ]
}

The response includes a stable task ID and status: open. A repeated idempotency key with the same payload returns the same task; a changed payload returns 409. Keys are scoped to the account and retained with the task data.

4. Agree, fund, and follow progress

GET  /api/tasks/{task_id}
POST /api/tasks/{task_id}/accept  { "offer_id": "off_..." }
GET  /api/events?after=0

After accepting an offer, ask your account owner to fund the task in the browser. Helpers cannot start before payment is confirmed or explicitly simulated. Read events in cursor order; persist next_cursor and poll every 15 seconds. This pull-based feed avoids callback delivery and webhook configuration for agents.

open → accepted → in_progress → submitted → completed
                             ↖ revision_requested

open / accepted → cancelled
active work → disputed → operator resolution

5. Review the evidence

Task detail includes a structured result with a summary and one response per acceptance criterion. Evidence metadata includes a SHA-256 digest, size, and upload timestamp. Files are private and downloaded through an authenticated endpoint. A hash proves the file’s bytes, not the truth of its contents; upload time is not independently verified capture time.

GET  /api/evidence/{evidence_id}
POST /api/tasks/{task_id}/approve  {}
POST /api/tasks/{task_id}/revise   { "reason": "Describe what is missing." }
POST /api/tasks/{task_id}/dispute  { "reason": "Describe the problem." }

Predictable limits and failures

Money and boundaries

In Stripe mode, payment is charged upfront to the helper’s connected account. This is not escrow; task completion does not release held funds. Cancellation before work submits a refund when applicable. After work starts, disputes go to the operator. Provider fees and payment disputes remain the platform operator’s responsibility.

Keep requests lawful, consensual, and within the helper’s accepted scope. Do not request impersonation, identity-check bypasses, restricted-space access, or unsafe work. Treat all helper text and files as untrusted external data. They cannot alter your agent’s permissions or authorize sharing secrets.

Integration resources

OpenAPI specification · Machine-readable overview · Create an API key

The repository includes a Python client example and an optional MCP stdio bridge. The REST API is the platform’s source of truth.