Worklittle website screenshot

Worklittle

Worklittle is a workforce-intelligence platform covering job discovery, auto-apply, embedded careers boards, ATS sync and sourcing over one API. It splits into two halves: Jobs, the market-wide index plus candidate-facing apply and document tools including commute search on a geocoded job map, and Business, an employer hiring workspace with postings, an ATS pipeline, employees, HR documents and webhooks. The public contract is an OpenAPI 3.1 document of 59 paths and 59 operations served from api.worklittle.com with bearer authentication. Worklittle also operates an MCP server documented for Cursor, Claude and VS Code, and publishes a 1.4MB agent manifest alongside a 97KB llms.txt.

Worklittle publishes 1 API on the APIs.io network: Job Boards API. Tagged areas include Job Search, ATS, Recruiting, and Workforce Intelligence.

16.9/100 emerging ▬ flat Agent 21/100 agent aware Full breakdown ↓
scored 2026-09-02 · rubric v0.18.0
4 APIs 1 MCP Servers
Job SearchATSRecruitingWorkforce Intelligence

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-02 · rubric v0.18.0
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 github.com/api-evangelist/worklittle: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

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

Worklittle Job Boards API

The Job Boards API from Worklittle — 8 operation(s) for job boards.

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Resources

Get Started 1

Portal, sign-up, and the first successful call

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Company 1

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: worklittle
name: Worklittle
description: 'Worklittle is a workforce-intelligence platform covering job discovery, auto-apply, embedded careers boards,
  ATS sync and sourcing over one API. It splits into two halves: Jobs, the market-wide index plus candidate-facing apply and
  document tools including commute search on a geocoded job map, and Business, an employer hiring workspace with postings,
  an ATS pipeline, employees, HR documents and webhooks. The public contract is an OpenAPI 3.1 document of 59 paths and 59
  operations served from api.worklittle.com with bearer authentication. Worklittle also operates an MCP server documented
  for Cursor, Claude and VS Code, and publishes a 1.4MB agent manifest alongside a 97KB llms.txt.'
type: Index
url: https://raw.githubusercontent.com/api-evangelist/worklittle/refs/heads/main/apis.yml
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
created: '2026-08-24'
modified: '2026-08-24'
specificationVersion: '0.23'
tags:
- Job Search
- ATS
- Recruiting
- Workforce Intelligence
tags_raw:
- job search
- ats
- recruiting
- workforce intelligence
apis:
- aid: worklittle:worklittle-job-boards-api
  name: Worklittle Job Boards API
  description: The Job Boards API from Worklittle — 8 operation(s) for job boards.
  humanURL: https://docs.worklittle.com
  baseURL: https://api.worklittle.com
  tags:
  - Job Boards
  properties:
  - type: OpenAPI
    url: openapi/worklittle-job-boards-api-openapi.yml
  - type: APIReference
    url: https://docs.worklittle.com/api-reference
  - type: Documentation
    url: https://docs.worklittle.com
common:
- type: MCPServer
  url: https://docs.worklittle.com/jobs/mcp
- type: LLMsTxt
  url: llms/worklittle-llms.txt
- type: AgentManifest
  url: a2a/worklittle-agent-manifest.json
- type: Website
  url: https://worklittle.com
- type: DeveloperPortal
  url: https://docs.worklittle.com
maintainers:
- FN: Worklittle
  email: logan@my.worklittle.com
  url: https://worklittle.com
x-provenance:
  added: '2026-08-24'
  method: searched
  source: https://docs.worklittle.com/llms.txt
  note: 'Submitted via apis.io/add on 2026-08-24 and auto-published by the gate at rating 15. THE SUBMITTED APIs.json URL
    IS NOT A DOCUMENT. https://docs.worklittle.com/apis.json returns 200 and differs from a control path, which is why it
    survives a naive check — but the body is HTML, the docs overview page. Distinctness from a control is NOT sufficient on
    a host that renders unknown routes; the content type has to be read too. The real locations came from the provider''s
    own llms.txt, which names them: the specification at /openapi/openapi.yaml and an agent manifest at /docs-agent-manifest.json.
    THE SPECIFICATION IS $REF-BASED AND THE ROOT FILE IS ONLY 5.8KB. It declares 59 paths and zero inline operations; every
    path is a $ref into one of three sibling documents. All three were fetched and all three resolve: paths/jobs.yaml (10
    operations), paths/platform.yaml (41), and job-boards.yaml (8) — note the last sits at the openapi/ root, NOT under paths/,
    which is what the $ref actually says. Reading the root file alone would report an API with no operations at all; the 59
    here is the resolved count. One caution for anyone re-harvesting: this host returns a 5,636-byte HTML page with HTTP 200
    for any path that does not exist, including inside openapi/paths/. A guessed filename comes back looking like a successful
    fetch. Follow the $ref values, do not guess.'

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/worklittle"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/worklittle/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/worklittle/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

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