Litmus Hiring

Litmus is a Y Combinator-backed technical hiring platform that turns repositories, engineering tickets, and job descriptions into structured, project-based technical assessments and interview pipelines tailored to how a team actually ships. It evaluates candidates on both code quality and development process, lets them work in their own IDE or terminal, and captures AI-tool usage (Claude Code, Copilot CLI) transparently. Candidate management syncs with the Ashby, Greenhouse, and Lever applicant-tracking systems. Litmus exposes a bearer-key REST API (roles, invites, submissions) and an official hosted Model Context Protocol (MCP) server for agent-driven access to submissions, candidates, pipeline status, and assessment authoring.

Litmus Hiring publishes 3 API contracts indexed on the APIs.io network: Invites API, Roles API, and Submissions API. Tagged areas include Company, Hiring, Recruiting, Technical Assessment, and Developer Hiring.

The Litmus Hiring catalog on APIs.io includes 1 Spectral governance ruleset.

Litmus Hiring’s developer surface includes documentation, API reference, getting-started guide, support, authentication, and 20 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

40.0/100 developing ▬ flat Agent 42/100 agent ready Front door AI 5/6 prominent saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

1 published contract 1 MCP Servers 2 Agent Skills

Company Hiring Recruiting Technical Assessment Developer Hiring MCP Interviewing Y Combinator

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Human Capital Management

BC-300

InvitesRolesSubmissions

POST /invites GET /submissions/{id} GET /roles

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 40.0/100 · developing

Contract Quality 9.6 / 19

Developer Ergonomics 8.5 / 15

Access Clarity 4.2 / 15

Operational Transparency 0.0 / 10

Contract Governance 1.6 / 9

Discoverability 5.1 / 8

Regulatory Posture 4.3 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 42/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 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 Horizontal (data, software, accessibility, platform) regime, 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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/litmus-hiring/"><img src="https://apis.io/badge/litmus-hiring/card.svg" alt="Litmus Hiring 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):

Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
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) Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented) Ask about this →
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link Ask about this →
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks Ask about this →

5 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 27.7 — up to +14.5 composite points Ask about this →
Operational Transparency scores 0.0 — up to +13.0 composite points Ask about this →
Contract Quality scores 51.4 — up to +12.2 composite points Ask about this →

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.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

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/litmus-hiring/apis.yml: open an issue on github.com/api-evangelist/litmus-hiring 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 5

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.

Model Context Protocol (MCP)

measured — observed by APIs.io (verified)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 3

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

Litmus Hiring Invites API

Candidate invitations

Litmus Hiring Roles API

Open roles within your organization

Litmus Hiring Submissions API

Candidate assessment submissions

Open Collections 3

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Litmus Hiring REST Invites API

OPEN COLLECTION

Litmus Hiring REST Invites Roles API

OPEN COLLECTION

Litmus Hiring REST Invites Submissions API

OPEN COLLECTION

MCP Servers 1

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

Litmus Hiring MCP Server

Official hosted Model Context Protocol server for the Litmus hiring platform. Connects Claude Desktop, Claude Code, or Cursor (via Clerk OAuth) and headless/automation clients (...

MCP SERVER

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Author an assessment and invite a candidate

AGENT SKILL

Track Litmus submissions for a role

AGENT SKILL

Terms of Service 1

What its API terms permit and prohibit, quoted from its own page.

Litmus Hiring

7 quoted statements, read from Litmus Hiring's own page on 2026-11-09.

TERMS

Privacy & Data 1

Its role, the data it processes, retention and transfers, quoted from its own privacy page.

Litmus Hiring

26 quoted statements, read from Litmus Hiring's own page on 2026-11-09.

PRIVACY

Eligibility 1

Who may sign up and where, quoted from its own terms.

Litmus Hiring

3 quoted statements, read from Litmus Hiring's own page on 2026-11-09.

ELIGIBILITY

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Litmus Hiring API Rules

52 rules · 50 error-severity 1 warn-severity 1 info-severity

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Litmus Hiring Overlay

3 actions · update · litmus-hiring-openapi.yml

DERIVED

Security Posture 2

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

Litmus Hiring Authentication

http/oauth2 · 2 schemes

SECURITY

Litmus Hiring Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Litmus Hiring Scopes

7 scopes · authorizationCode

7 scopes

SCOPES

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

MCPServer

WellKnown

LLMsTxt

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

OAuthScopes

OAuthScopes

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 3

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

UsageTerms

UsageTerms

Company 1

The organization behind the API

Website

Website

Other 4

Properties that don't map to a standard resource type

CapabilityMap

Overlay

DataProcessing

Eligibility

Source (apis.yml)

aid: litmus-hiring
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - scopes
  - security
  generated: '2026-11-13'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/litmus-hiring.png
name: Litmus Hiring
description: Litmus is a Y Combinator-backed technical hiring platform that turns repositories, engineering tickets, and job
  descriptions into structured, project-based technical assessments and interview pipelines tailored to how a team actually
  ships. It evaluates candidates on both code quality and development process, lets them work in their own IDE or terminal,
  and captures AI-tool usage (Claude Code, Copilot CLI) transparently. Candidate management syncs with the Ashby, Greenhouse,
  and Lever applicant-tracking systems. Litmus exposes a bearer-key REST API (roles, invites, submissions) and an official
  hosted Model Context Protocol (MCP) server for agent-driven access to submissions, candidates, pipeline status, and assessment
  authoring.
url: https://raw.githubusercontent.com/api-evangelist/litmus-hiring/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- y-combinator
x-tier: profiled
x-tier-reason: enriched-from-provider-surface
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Hiring
- Recruiting
- Technical Assessment
- Developer Hiring
- MCP
- Interviewing
- Y Combinator
tags_raw:
- Company
- Hiring
- Recruitment
- Technical Assessment
- Developer Hiring
- MCP
- Interviewing
- Y Combinator
common:
- type: CapabilityMap
  url: capabilities/litmus-hiring-capability-edges.yml
  name: Litmus Hiring Business Capability Map
- type: Overlay
  url: overlays/litmus-hiring-overlay.yaml
- url: https://litmushiring.com
  type: Website
- url: https://litmushiring.com/docs
  type: DeveloperPortal
- url: https://litmushiring.com/docs
  type: Documentation
- url: https://litmushiring.com/docs/rest
  type: APIReference
- url: https://litmushiring.com/docs/mcp/quickstart
  type: GettingStarted
- url: https://litmushiring.com/privacy
  type: PrivacyPolicy
- url: https://litmushiring.com/terms
  type: TermsOfService
- url: mailto:support@litmushiring.com
  type: Support
- url: mcp/litmus-hiring-mcp.yml
  type: MCPServer
- url: authentication/litmus-hiring-authentication.yml
  type: Authentication
- url: scopes/litmus-hiring-scopes.yml
  type: OAuthScopes
- url: conventions/litmus-hiring-conventions.yml
  type: Conventions
- url: errors/litmus-hiring-problem-types.yml
  type: ErrorCatalog
- url: lifecycle/litmus-hiring-lifecycle.yml
  type: Lifecycle
- url: conformance/litmus-hiring-conformance.yml
  type: Conformance
- url: data-model/litmus-hiring-data-model.yml
  type: DataModel
- url: well-known/litmus-hiring-well-known.yml
  type: WellKnown
- url: llms/litmus-hiring-llms.txt
  type: LLMsTxt
- url: skills/_index.yml
  type: AgentSkill
- url: security/litmus-hiring-domain-security.yml
  type: DomainSecurity
- type: UsageTerms
  url: terms/litmus-hiring-terms-of-service.yml
- type: DataProcessing
  url: privacy/litmus-hiring-privacy-policy.yml
- type: Eligibility
  url: eligibility/litmus-hiring-eligibility.yml
apis:
- aid: litmus-hiring:litmus-hiring-invites-api
  name: Litmus Hiring Invites API
  description: Candidate invitations
  humanURL: https://litmushiring.com/docs/rest
  baseURL: https://www.litmushiring.com/api/v1
  tags:
  - Invites
  properties:
  - type: OpenAPI
    url: openapi/litmus-hiring-invites-api-openapi.yml
  - type: Documentation
    url: https://litmushiring.com/docs/rest
  - type: APIReference
    url: https://litmushiring.com/docs/rest
- aid: litmus-hiring:litmus-hiring-roles-api
  name: Litmus Hiring Roles API
  description: Open roles within your organization
  humanURL: https://litmushiring.com/docs/rest
  baseURL: https://www.litmushiring.com/api/v1
  tags:
  - Roles
  properties:
  - type: OpenAPI
    url: openapi/litmus-hiring-roles-api-openapi.yml
  - type: Documentation
    url: https://litmushiring.com/docs/rest
  - type: APIReference
    url: https://litmushiring.com/docs/rest
- aid: litmus-hiring:litmus-hiring-submissions-api
  name: Litmus Hiring Submissions API
  description: Candidate assessment submissions
  humanURL: https://litmushiring.com/docs/rest
  baseURL: https://www.litmushiring.com/api/v1
  tags:
  - Submissions
  properties:
  - type: OpenAPI
    url: openapi/litmus-hiring-submissions-api-openapi.yml
  - type: Documentation
    url: https://litmushiring.com/docs/rest
  - type: APIReference
    url: https://litmushiring.com/docs/rest
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 17
  pass: local-v1

Litmus Hiring API — frequently asked questions

Does Litmus Hiring have an API?

Yes. APIs.io lists 3 APIs from Litmus Hiring, including Litmus Hiring Invites API, Litmus Hiring Roles API and Litmus Hiring Submissions API.

Is there an OpenAPI specification for the Litmus Hiring API?

Yes. APIs.io indexes 3 OpenAPI specifications for Litmus Hiring, each linked for download from this page.

How do I authenticate with the Litmus Hiring API?

Litmus Hiring documents its authentication (http/oauth2 · 2 schemes). The details are profiled on APIs.io as Litmus Hiring Authentication.

Does Litmus Hiring have an MCP server?

Yes. APIs.io lists 1 MCP server for Litmus Hiring: Official hosted Model Context Protocol server for the Litmus hiring platform. Connects Claude Desktop, Claude Code, or Cursor (via Clerk OAuth) and headless/automation clients (via a `litmus_sk_...` A

Is the Litmus Hiring API ready for AI agents?

Litmus Hiring has a Kin Score of 40.0 out of 100 (developing) and an Agent Readiness score of 41.9 (agent-ready), scored by API Evangelist on 2026-11-13.

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/litmus-hiring"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/litmus-hiring/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.