Wonolo

Wonolo is an on-demand staffing marketplace, founded in 2013 and headquartered in San Francisco, that connects businesses needing flexible frontline labor with a pool of vetted independent workers ("Wonoloers") for warehousing, manufacturing, food production, retail, hospitality and general labor jobs. Businesses post job requests and are matched to available workers in real time without resumes or interviews, for one-off, ongoing and temp-to-hire needs. Wonolo operates a REST integration API (V2) on api.wonolo.com that lets customers create and manage job requests, jobs, workers and users programmatically and receive webhook callbacks, so scheduling, timekeeping, HR and CRM systems can be wired directly into the staffing platform.

Wonolo is listed with 1 API on the APIs.io network. Tagged areas include Company, Staffing, Workforce, Human Resources, and Marketplace.

Wonolo’s developer surface includes engineering blog, support, and 9 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

19.3/100 emerging ▬ flat Agent 19/100 agent aware Front door AI 2/6 trace Heartbeat 0/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API

Company Staffing Workforce Human Resources Marketplace Gig Economy Recruiting Labor On-Demand

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 19.3/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 3.2 / 17

Access Clarity 4.7 / 17

Operational Transparency 0.3 / 11

Contract Governance 1.9 / 10

Discoverability 5.6 / 9

Regulatory Posture 3.7 / 15

Agent readiness — 19/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Employment & Payroll regime (on an ambiguous tag, where no other regime matched), so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/wonolo/"><img src="https://apis.io/badge/wonolo/card.svg" alt="Wonolo on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Developer Ergonomics scores 19.0 — up to +16.2 composite points
Access Clarity scores 27.6 — up to +14.5 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/wonolo/apis.yml: open an issue on github.com/api-evangelist/wonolo to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Wonolo API V2

The Wonolo API V2 is a RESTful, JSON-only integration API for the Wonolo on-demand staffing platform. It performs CRUD operations against platform resources — Users (both Worker...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Wonolo Authentication

apiKey/http · 3 schemes

SECURITY

Wonolo Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Login

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Support

Support

HelpCenter

HelpCenter

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: wonolo
name: Wonolo
description: Wonolo is an on-demand staffing marketplace, founded in 2013 and headquartered in San Francisco, that connects
  businesses needing flexible frontline labor with a pool of vetted independent workers ("Wonoloers") for warehousing, manufacturing,
  food production, retail, hospitality and general labor jobs. Businesses post job requests and are matched to available workers
  in real time without resumes or interviews, for one-off, ongoing and temp-to-hire needs. Wonolo operates a REST integration
  API (V2) on api.wonolo.com that lets customers create and manage job requests, jobs, workers and users programmatically
  and receive webhook callbacks, so scheduling, timekeeping, HR and CRM systems can be wired directly into the staffing platform.
url: https://raw.githubusercontent.com/api-evangelist/wonolo/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  probe_state: gated
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://framerusercontent.com/assets/PBgIa3TL1hQKy1ZdIQ2vbm12CE.png
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-05'
modified: '2026-08-05'
tags:
- Company
- Staffing
- Workforce
- Human Resources
- Marketplace
- Gig Economy
- Recruiting
- Labor
- On-Demand
apis:
- aid: wonolo:wonolo-api-v2
  name: Wonolo API V2
  description: 'The Wonolo API V2 is a RESTful, JSON-only integration API for the Wonolo on-demand staffing platform. It performs
    CRUD operations against platform resources — Users (both Workers/Wonoloers and Employers/Requesters), Job Requests (a
    unit of work to be staffed) and Jobs (an individual worker''s assignment against a request) — and supports webhook callbacks
    so a customer system can track resource state changes. Callers authenticate by exchanging an issued api_key and secret_key
    for a token at /api_v2/authenticate and pass that token on subsequent calls. API keys are issued at one of two access
    levels: Public Pool (read-oriented access to Wonolo''s public worker pool) and Private Pool (for companies managing their
    own worker pool), with write operations restricted at the Public Pool level.'
  humanURL: https://www.wonolo.com/businesses
  baseURL: https://api.wonolo.com/api_v2/
  tags:
  - Staffing
  - Workforce
  - Job
  - Webhook
  tags_raw:
  - Staffing
  - Workforce
  - Jobs
  - Webhooks
  properties:
  - type: Authentication
    url: authentication/wonolo-authentication.yml
  - type: Lifecycle
    url: lifecycle/wonolo-lifecycle.yml
  - type: Conformance
    url: conformance/wonolo-conformance.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.wonolo.com/
- type: Blog
  url: https://www.wonolo.com/blog
- type: GitHubOrganization
  url: https://github.com/Wonolo
- type: Support
  url: https://support-business.wonolo.com/
- type: HelpCenter
  url: https://support-worker.wonolo.com/
- type: TermsOfService
  url: https://info.wonolo.com/terms/
- type: PrivacyPolicy
  url: https://info.wonolo.com/privacy/
- type: Login
  url: https://api.wonolo.com/users/sign_in
- type: WellKnown
  url: well-known/wonolo-well-known.yml
- type: DomainSecurity
  url: security/wonolo-domain-security.yml
- type: LLMsTxt
  url: llms/wonolo-llms.txt
x-enrichment:
  date: '2026-08-05'
  status: minimal
  artifacts_added: 8
  pass: local-v1
x-coverage:
  state: gated
  reason: customer-only-docs
  detail: Wonolo's API is live — https://api.wonolo.com/api_v2/info answers 200 anonymously — but its public reference at
    wonolo.readme.io now returns a hard 404 and the Developer Center at developer.wonolo.com is a dangling Netlify custom
    domain (cert covers only *.netlify.app, origin 404s), so the api_v2 contract is reachable today only by customers Wonolo
    has issued an api_key/secret_key to.
  evidence:
  - url: https://api.wonolo.com/api_v2/info
    status: 200
  - url: https://wonolo.readme.io/docs/getting-started
    status: 404
  - url: https://wonolo-developer-center.netlify.app/
    status: 404
  - url: https://api.wonolo.com/openapi.json
    status: 404
  checked: '2026-08-05'

Wonolo API — frequently asked questions

Does Wonolo have an API?

Yes. APIs.io lists 1 API from Wonolo, including Wonolo API V2.

How do I authenticate with the Wonolo API?

Wonolo documents its authentication (apiKey/http · 3 schemes). The details are profiled on APIs.io as Wonolo Authentication.

Is the Wonolo API ready for AI agents?

Wonolo has a Kin Score of 19.3 out of 100 (emerging) and an Agent Readiness score of 18.7 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/wonolo"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/wonolo/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/wonolo/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.