Wellfound

Wellfound (formerly AngelList Talent) is a startup hiring marketplace and AI recruiting platform operating wellfound.com, the Wellfound Reach AI sourcing product and the Autopilot managed-recruiting service. Its entire public machine-readable API surface is two OAuth-protected Model Context Protocol servers - https://wellfound.com/api/mcp for recruiter applications and https://reach.wellfound.com/mcp for Reach projects, sourcing agents, candidates and company lists - discovered from a complete RFC 8414 / RFC 9728 / OpenID Connect discovery stack and verified by probe. Wellfound publishes no OpenAPI document, no public GraphQL endpoint, no REST reference and no developer portal, so the discovery documents are the only published description of how to integrate.

Wellfound is listed with 2 APIs on the APIs.io network. Tagged areas include Recruiting, Hiring, Talent, Human Resources, and Applicant Tracking.

Wellfound’s developer surface includes support, engineering blog, pricing, signup flow, authentication, and 23 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

32.3/100 thin ▬ flat Agent 33/100 agent ready Front door AI 6/6 dominant Heartbeat 100/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessSelf serve

2 APIs 1 MCP Servers

Recruiting Hiring Talent Human Resources Applicant Tracking Job Board Startups MCP Agent-Native OAuthAI SourcingAuthentication

Kin Score

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

Composite quality — 32.3/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 3.2 / 17

Access Clarity 10.3 / 17

Operational Transparency 2.9 / 11

Contract Governance 1.9 / 10

Discoverability 5.8 / 9

Regulatory Posture 6.8 / 15

Agent readiness — 33/100 · agent ready

Machine-Readable Contract 0 / 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 7 / 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/wellfound/"><img src="https://apis.io/badge/wellfound/card.svg" alt="Wellfound 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
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)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks

6 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
Contract Governance scores 18.2 — up to +9.8 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/wellfound/apis.yml: open an issue on github.com/api-evangelist/wellfound 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 4

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

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

APIs 2

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

Wellfound Applications MCP

Remote MCP server exposing a recruiter's inbound job applications to an agent, and letting it accept or reject them. Named "Wellfound recruiter applications" in its own RFC 9728...

Wellfound Reach MCP

Remote MCP server for Wellfound Reach, the AI sourcing product. Seven scopes across four resources - projects:read, agents:read, agents:write, candidates:read, candidates:write,...

MCP Servers 1

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

Wellfound MCP servers

Wellfound runs TWO separate first-party hosted MCP servers, each with its own OAuth authorization server, its own scope vocabulary and its own protected-resource document. Neith...

MCP SERVER

Wellfound API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Wellfound Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Wellfound Rate Limits

0 limits

RATE LIMITS

Security Posture 4

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

Wellfound Authentication

2 schemes

SECURITY

Wellfound Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Wellfound Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Wellfound Trust Center

SOC 2

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Wellfound Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 2

Portal, sign-up, and the first successful call

SignUp

SignUp

Login

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

MCPServer

MCPServer

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conformance

Conventions

ErrorCatalog

Lifecycle

Build 1

SDKs, sample code, and the tooling you integrate with

Packages

Packages

Access & Security 8

Authentication, authorization, and security posture

TrustCenter

Authentication

OAuthScopes

SecurityTxt

Security

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Compliance

Compliance

Scroll for all 8

Operate 3

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

RateLimits

RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

PrivacyPolicy

Plans

Company 3

The organization behind the API

Website

Website

Blog

Blog

BlogRSS

BlogRSS

Source (apis.yml)

aid: wellfound
name: Wellfound
description: Wellfound (formerly AngelList Talent) is a startup hiring marketplace and AI recruiting platform operating wellfound.com,
  the Wellfound Reach AI sourcing product and the Autopilot managed-recruiting service. Its entire public machine-readable
  API surface is two OAuth-protected Model Context Protocol servers - https://wellfound.com/api/mcp for recruiter applications
  and https://reach.wellfound.com/mcp for Reach projects, sourcing agents, candidates and company lists - discovered from
  a complete RFC 8414 / RFC 9728 / OpenID Connect discovery stack and verified by probe. Wellfound publishes no OpenAPI document,
  no public GraphQL endpoint, no REST reference and no developer portal, so the discovery documents are the only published
  description of how to integrate.
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Self-serve signup
  confidence: medium
  probe_state: covered
  source:
  - authentication
  - scopes
  - rate-limits
  - security
  generated: '2026-11-06'
  method: derived
image: https://reach.wellfound.com/assets/marketing/og/homepage-2fb80e2936cb06211fa7702e4b089510c772d1b887166b884b4720f73445e875.png
url: https://raw.githubusercontent.com/api-evangelist/wellfound/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
position: Producing
specificationVersion: '0.20'
created: '2026-09-04'
modified: '2026-09-04'
tags:
- Recruiting
- Hiring
- Talent
- Human Resources
- Applicant Tracking
- Job Board
- Startups
- MCP
- Agent-Native
- OAuth
- AI Sourcing
- Authentication
tags_raw:
- Recruiting
- Hiring
- Talent
- Human Resources
- Applicant Tracking
- Job Board
- Startups
- MCP
- agent-native
- OAuth
- AI Sourcing
- Authentication
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: wellfound:wellfound-applications-mcp
  name: Wellfound Applications MCP
  description: Remote MCP server exposing a recruiter's inbound job applications to an agent, and letting it accept or reject
    them. Named "Wellfound recruiter applications" in its own RFC 9728 protected-resource document. OAuth 2.1 authorization
    code + PKCE S256 with dynamic client registration; scopes applications:read, applications:accept, applications:reject.
    The tool list is auth-gated - an unauthenticated tools/list returns HTTP 401 with an RFC 9728 WWW-Authenticate challenge.
  image: https://reach.wellfound.com/assets/marketing/og/homepage-2fb80e2936cb06211fa7702e4b089510c772d1b887166b884b4720f73445e875.png
  humanURL: https://wellfound.com/recruit/pricing
  baseURL: https://wellfound.com/api/mcp
  tags:
  - Recruiting
  - Applicant Tracking
  - MCP
  - Agent-Native
  - OAuth
  - Authentication
  tags_raw:
  - Recruiting
  - Applicant Tracking
  - MCP
  - agent-native
  - OAuth
  - Authentication
  properties:
  - type: MCPServer
    url: mcp/wellfound-mcp.yml
  - type: Authentication
    url: authentication/wellfound-authentication.yml
  - type: OAuthScopes
    url: scopes/wellfound-scopes.yml
  - type: OpenIDConnect
    url: well-known/wellfound-openid-configuration.json
- aid: wellfound:wellfound-reach-mcp
  name: Wellfound Reach MCP
  description: Remote MCP server for Wellfound Reach, the AI sourcing product. Seven scopes across four resources - projects:read,
    agents:read, agents:write, candidates:read, candidates:write, company_lists:read, company_lists:write - so an agent can
    read sourcing projects and both read and write the sourcing agents, candidates and company lists on an account. Its own
    authorization server at https://reach.wellfound.com accepts public clients only. The tool list is auth-gated.
  image: https://reach.wellfound.com/assets/marketing/og/homepage-2fb80e2936cb06211fa7702e4b089510c772d1b887166b884b4720f73445e875.png
  humanURL: https://reach.wellfound.com/
  baseURL: https://reach.wellfound.com/mcp
  tags:
  - Recruiting
  - AI Sourcing
  - Talent
  - MCP
  - Agent-Native
  - OAuth
  - Authentication
  tags_raw:
  - Recruiting
  - AI Sourcing
  - Talent
  - MCP
  - agent-native
  - OAuth
  - Authentication
  properties:
  - type: MCPServer
    url: mcp/wellfound-mcp.yml
  - type: Authentication
    url: authentication/wellfound-authentication.yml
  - type: OAuthScopes
    url: scopes/wellfound-scopes.yml
common:
- type: Website
  url: https://wellfound.com/
- type: Support
  url: https://help.wellfound.com/
- type: Blog
  url: https://wellfound.com/blog
- type: BlogRSS
  url: https://wellfound.com/blog.rss
- type: Pricing
  url: https://wellfound.com/recruit/pricing
- type: SignUp
  url: https://wellfound.com/jobs/signup
- type: Login
  url: https://wellfound.com/login
- type: TermsOfService
  url: https://wellfound.com/terms
- type: PrivacyPolicy
  url: https://wellfound.com/privacy
- type: StatusPage
  url: https://status.wellfound.com/
- type: TrustCenter
  url: https://trust.wellfound.ai/
- type: MCPServer
  url: mcp/wellfound-mcp.yml
- type: Authentication
  url: authentication/wellfound-authentication.yml
- type: OAuthScopes
  url: scopes/wellfound-scopes.yml
- type: WellKnown
  url: well-known/wellfound-well-known.yml
- type: SecurityTxt
  url: well-known/wellfound-security.txt
- type: Security
  url: security/wellfound-vulnerability-disclosure.yml
- type: VulnerabilityDisclosure
  url: security/wellfound-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/wellfound-domain-security.yml
- type: Compliance
  url: security/wellfound-trust-center.yml
- type: Conformance
  url: conformance/wellfound-conformance.yml
- type: Conventions
  url: conventions/wellfound-conventions.yml
- type: ErrorCatalog
  url: errors/wellfound-problem-types.yml
- type: Lifecycle
  url: lifecycle/wellfound-lifecycle.yml
- type: Plans
  url: plans/wellfound-plans-pricing.yml
- type: RateLimits
  url: rate-limits/wellfound-rate-limits.yml
- type: Packages
  url: packages/wellfound-packages.yml
- type: LLMsTxt
  url: llms/wellfound-llms.txt
x-enrichment:
  date: '2026-09-04'
  status: enriched
  artifacts_added: 22
  pass: local-v3
x-coverage:
  state: covered
  reason: null
  detail: Contract discovery hit. Wellfound serves no OpenAPI and no public GraphQL, but it runs two live first-party MCP
    servers - https://wellfound.com/api/mcp and https://reach.wellfound.com/mcp - found via a complete RFC 8414 / RFC 9728
    / OpenID Connect discovery stack and verified by probe (both return HTTP 401 with a conformant WWW-Authenticate resource_metadata
    challenge). Their tool lists are OAuth-gated, so the 16 published scopes are recorded instead of invented tool schemas.
  evidence:
  - url: https://wellfound.com/.well-known/oauth-protected-resource
    status: 200
  - url: https://wellfound.com/api/mcp
    status: 401
  - url: https://reach.wellfound.com/.well-known/oauth-protected-resource
    status: 200
  - url: https://reach.wellfound.com/mcp
    status: 401
  - url: https://wellfound.com/openapi.json
    status: 404
  checked: '2026-09-04'

Wellfound API — frequently asked questions

Does Wellfound have an API?

Yes. APIs.io lists 2 APIs from Wellfound, including Wellfound Applications MCP and Wellfound Reach MCP.

How do I authenticate with the Wellfound API?

Wellfound documents its authentication (2 schemes). The details are profiled on APIs.io as Wellfound Authentication.

Does Wellfound have an MCP server?

Yes. APIs.io lists 1 MCP server for Wellfound: Wellfound runs TWO separate first-party hosted MCP servers, each with its own OAuth authorization server, its own scope vocabulary and its own protected-resource document. Neither is documented on any

Is the Wellfound API ready for AI agents?

Wellfound has a Kin Score of 32.3 out of 100 (thin) and an Agent Readiness score of 32.7 (agent-ready), 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/wellfound"

All providers

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

Every operation they expose

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

How their score was established

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