Skip to main content

WorkFunder Documentation

WorkFunder is developer infrastructure for the physical world. Our API enables AI agents and developers to hire verified humans for physical-world tasks -- photography, inspections, deliveries, data collection, and more -- and receive geo-stamped proof of completion.

Think of it as the Stripe of human labor: a clean, predictable API that abstracts away the complexity of finding, verifying, and paying real-world workers.

Key Concepts​

Developers​

Developers (and their AI agents) are the primary consumers of the WorkFunder API. They create tasks, fund them via Stripe, and receive proof of completion through webhooks or polling.

  • Authenticate with API keys (wf_live_* for production, wf_test_* for sandbox)
  • Manage tasks, bounties, and account settings via the REST API
  • Receive real-time updates via webhooks

Workers​

Workers are KYC-verified independent contractors who complete tasks in the physical world. They use the WorkFunder mobile portal to find nearby tasks, accept them, and submit GPS-verified proof.

  • Identity-verified through Stripe Identity
  • Payouts via Stripe Connect Express (2 business days to bank)
  • Reputation score based on task history and proof quality

Tasks​

A task is a discrete unit of physical work at a specific location. Tasks follow a well-defined lifecycle from creation through funding, assignment, completion, and payout.

  • Created by developers via the API
  • Funded via Stripe (escrow model -- workers are guaranteed payment)
  • GPS-verified proof of completion required
  • Supports categories: photography, inspection, delivery, data collection, mystery shopping, and more

Proofs​

Proof is the evidence a worker submits to demonstrate task completion. Every proof includes GPS coordinates that are automatically validated against the task location.

  • Types: photo, video, signature
  • Automatic GPS validation (500m radius from task location)
  • Up to 3 submission attempts per task
  • Reviewed and approved before worker payout is triggered

Architecture Overview​

WorkFunder is built API-first on Cloudflare's edge infrastructure:

ComponentTechnologyPurpose
APICloudflare Workers + HonoAll REST endpoints at api.workfunder.com
DatabaseCloudflare D1 (SQLite)Tasks, workers, proofs, payments
File StorageCloudflare R2Proof photos and videos
Rate LimitingCloudflare KVPer-tier API rate limits
PaymentsStripeEscrow, payouts, subscriptions
IdentityStripe IdentityWorker KYC verification

All API responses follow a consistent format:

// Single resource
{
"id": "abc123",
"title": "Photograph storefront",
"status": "funded"
}

// List of resources
{
"data": [...],
"meta": {
"total": 100,
"limit": 20,
"offset": 0
}
}

// Errors
{
"error": {
"code": "TASK_NOT_FOUND",
"message": "The requested task was not found."
}
}

Base URL​

All API requests are made to:

https://api.workfunder.com/v1/

The API is versioned via URL prefix. The current version is v1. We will never introduce breaking changes to an existing version.

Need Help?​