Worker Platform (For Buyers)

This page explains how real human workers see your jobs, how fast you can expect fulfillment, and how payout and quality controls protect both sides of the marketplace. It is not worker-app documentation — the worker API is an internal surface for the iOS app and is not documented publicly.

How workers see your job

Workers browse an in-app feed. When you post a job via POST /v1/jobs, it enters a priority distribution window. The first few minutes route the job to your highest-tier workers first; after the window, the job opens to the full eligible pool.

t=0s    Job posted via API
  │
  ▼
t=0–60s    Visible only to Gold + Diamond tier workers in the matching region
t=60–300s  Visible to Silver tier workers added
t=5min+    Open to all eligible workers (Bronze, New)

The window is why well-defined, fairly-priced jobs typically see their first submission within 5–15 minutes of posting — top-tier workers grab them immediately.

Worker tiers

Workers earn tier upgrades by maintaining a high approval rate (score 3+ on AI ensemble).

Tier	Approval rate gate	Perks
New	No history yet	Priority on first 3 jobs so new workers can build reputation
Bronze	60% approval, 10+ submissions	Standard access
Silver	75% approval, 50+ submissions	Earlier priority window, higher daily submission cap
Gold	85% approval, 150+ submissions	First-access window, can take high-value jobs
Diamond	92% approval, 500+ submissions	Top priority, eligible for geographic exclusives

As a buyer you never see which tier completed your job — you just see the resulting files and their AI scores. Tier is a supply-side lever we use to route your job to workers likely to produce approved work.

Daily submission cap

To prevent farming and protect quality, workers are capped at 50 submissions per worker per day across the platform. The cap resets at 00:00 UTC. For buyers this means a single worker cannot produce your entire dataset — large jobs naturally distribute across multiple contributors, which is good for geographic and device diversity.

Payout model

Workers earn 80% of price_per_file_cents for every approved file (3+ stars). The remaining 20% is the platform fee.

Buyer pays:  $1.00 per file
  ├── $0.80 → worker (earned immediately on approval)
  └── $0.20 → platform fee

Workers cash out in $10 minimum increments via Stripe Connect. Unpaid earnings accumulate until the threshold is reached.

Rejected submissions (< 3 stars) are free to buyers — no credit is deducted. This is a deliberate design choice: it aligns platform incentives with quality rather than volume.

Quality controls

Several layers protect the quality of files delivered to buyers:

Resolution floor — If you set min_width / min_height on the job, submissions below threshold are auto-rejected before AI scoring (no credit consumed).
Authenticity signals — The scoring ensemble detects AI-generated content and flags it. See Pre-Check Gates.
Reverse image search — Stock photos and prior-submission matches are rejected without scoring.
Content-hash dedup — A worker cannot submit the same file bytes twice on the same job.
Device attestation — iOS workers sign uploads via Apple App Attest, making it hard to submit from emulators or tampered devices.
3-strike ban — A worker who scores 1-star three times is banned from the platform.
Worker feedback loop — Rejected workers see ai_feedback explaining the rejection so honest mistakes can be corrected on re-submit (on 2-star rejections).

See Trust & Safety for detail on moderation, ban appeals, and privacy handling.

How fast will my job fulfill?

There’s no hard SLA, but these factors drive speed:

Factor	Faster	Slower
Price per file	At or above market rate for the format	Below platform floor (gets reflagged)
Description clarity	Specific requirements, explicit format/constraints	Vague (“good photos”)
Geographic constraint	Major metro (NYC, LA, London)	Niche regions or small towns
Format	Image (fast to capture)	Long video (minutes of capture time)
Files needed	1–100	10,000+ (may take days)
Time of day posted	Morning in the target region	Late night / pre-dawn

Typical first-submission latencies (not a guarantee — observed ranges):

Image jobs, major metro, clear description: 5–30 minutes
Audio jobs, major metro, 30–60s clips: 15–60 minutes
Video jobs, niche regions: 1–6 hours
Large image datasets (1,000+ files): 6–24 hours to full completion

If a job stays at open with zero submissions for 30+ minutes, check the description for ambiguity or the price for floor violations. Workers also flag unreasonable jobs — that fires job.flagged via webhook.

Geographic constraints

Jobs accept location with either { city, state }, { latitude, longitude, radius_km }, or both. Workers see your job only if their device GPS falls inside that radius (or within the city boundary for text-based constraints).

"location": {
  "city": "Seattle",
  "state": "WA",
  "latitude": 47.6062,
  "longitude": -122.3321,
  "radius_km": 25
}

If you don’t set location, the job is available globally to eligible workers. For ML training data you usually want no constraint (diversity is a feature). For UGC verification tied to real businesses, constrain tightly.