Yello

Yello is a Chicago-based talent acquisition software company, founded in 2008 (originally Recsolu), whose enterprise platform runs campus and early-career recruiting for roughly 100 Fortune 500 employers across 70+ countries and 15+ languages. The product line covers campus planning, recruitment events, candidate sourcing, interview scheduling, a recruitment CRM, recruitment analytics and an AI campus recruiting agent, plus Yello Government Recruiting Solutions (YGRS) for public-sector hiring and the WayUp candidate marketplace and Symba new-hire readiness products acquired by the company. Yello Enterprise is delivered as per-customer tenant sites on yello.co and recsolu.com in US (us-east-1) and EU (eu-west-1) environments. Its integration surface with ATS and HRIS systems (Workday, Taleo, Oracle Recruiting Cloud, iCIMS, SAP SuccessFactors, Greenhouse, ADP) is real but is sold and provisioned through a partner/sales conversation rather than a public developer portal. The one openly reachable machine surface found is a remote Model Context Protocol server on the WayUp property, published with RFC 8414 / RFC 9728 OAuth discovery.

Yello is listed with 1 API on the APIs.io network. Tagged areas include Talent Acquisition, Recruiting, Human Resources, Campus Recruiting, and Applicant Tracking.

Yello’s developer surface includes engineering blog, support, signup flow, pricing, and 21 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

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

AccessSelf serve

1 API 1 MCP Servers

Talent Acquisition Recruiting Human ResourcesCampus RecruitingApplicant TrackingRecruitment CRMInterview Scheduling Job MCP Government

Kin Score

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

Composite quality — 33.9/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 3.2 / 17

Access Clarity 10.3 / 17

Operational Transparency 2.6 / 11

Contract Governance 1.9 / 10

Discoverability 6.5 / 9

Regulatory Posture 7.1 / 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 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 4 / 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 Government & Public Sector 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 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/yello/"><img src="https://apis.io/badge/yello/card.svg" alt="Yello 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)
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
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

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
Operational Transparency scores 23.7 — up to +9.9 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/yello/apis.yml: open an issue on github.com/api-evangelist/yello 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 →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Government Cloud (FedRAMP, GovRAMP, G-Cloud)	regulated	38.8 (thin)	-	-
Zoom App Marketplace and Partner Ecosystem (builders and partners on Zoom)	regulated	38.8 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 3

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)

APIs 1

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

WayUp MCP Server

A remote Model Context Protocol (streamable HTTP) server operated by WayUp, a Yello company, at https://www.wayup.com/mcp. Discovered by probe: the host publishes RFC 9728 prote...

MCP Servers 1

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

Yello MCP Server

Remote MCP server at www.wayup.com over HTTP requiring OAuth.

MCP SERVER

Yello API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Yello Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Yello Rate Limits

0 limits

RATE LIMITS

Security Posture 3

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

Yello Authentication

oauth2 · 1 scheme

SECURITY

Yello Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Yello Trust Center

SOC 2, ISO 27001, FedRAMP

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Yello Scopes

1 scope · authorizationCode

1 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

SignUp

SignUp

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

LLMsTxt

LLMsTxt

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Lifecycle

Lifecycle

Conformance

Conformance

Conventions

Conventions

Build 2

SDKs, sample code, and the tooling you integrate with

IntegrationEdges

IntegrationEdges

Packages

Packages

Access & Security 3

Authentication, authorization, and security posture

TrustCenter

TrustCenter

Compliance

Compliance

DomainSecurity

DomainSecurity

Operate 4

Status, limits, changes, and where to get help

Deprecation

Support

StatusPage

RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

PrivacyPolicy

Plans

Company 3

The organization behind the API

Newsroom

Newsroom

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: yello
name: Yello
description: Yello is a Chicago-based talent acquisition software company, founded in 2008 (originally Recsolu), whose enterprise
  platform runs campus and early-career recruiting for roughly 100 Fortune 500 employers across 70+ countries and 15+ languages.
  The product line covers campus planning, recruitment events, candidate sourcing, interview scheduling, a recruitment CRM,
  recruitment analytics and an AI campus recruiting agent, plus Yello Government Recruiting Solutions (YGRS) for public-sector
  hiring and the WayUp candidate marketplace and Symba new-hire readiness products acquired by the company. Yello Enterprise
  is delivered as per-customer tenant sites on yello.co and recsolu.com in US (us-east-1) and EU (eu-west-1) environments.
  Its integration surface with ATS and HRIS systems (Workday, Taleo, Oracle Recruiting Cloud, iCIMS, SAP SuccessFactors, Greenhouse,
  ADP) is real but is sold and provisioned through a partner/sales conversation rather than a public developer portal. The
  one openly reachable machine surface found is a remote Model Context Protocol server on the WayUp property, published with
  RFC 8414 / RFC 9728 OAuth discovery.
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - scopes
  - rate-limits
  - security
  generated: '2026-11-06'
  method: derived
image: https://yello.co/wp-content/uploads/2021/04/yello-logo@4x.png
url: https://raw.githubusercontent.com/api-evangelist/yello/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:
- Talent Acquisition
- Recruiting
- Human Resources
- Campus Recruiting
- Applicant Tracking
- Recruitment CRM
- Interview Scheduling
- Job
- MCP
- Government
tags_raw:
- Talent Acquisition
- Recruiting
- Human Resources
- Campus Recruiting
- Applicant Tracking
- Recruitment CRM
- Interview Scheduling
- Jobs
- Model Context Protocol
- Government
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Deprecation
  url: lifecycle/yello-lifecycle.yml
- type: Hosts
  url: hosts/yello-hosts.yml
- type: IntegrationEdges
  url: integrations/yello-integration-edges.yml
- type: Vendors
  url: vendors/yello-vendors.yml
- type: Newsroom
  url: https://yello.co/about/newsroom/
- type: TrustCenter
  url: security/yello-trust-center.yml
- type: Website
  url: https://yello.co/
- type: Blog
  url: https://yello.co/blog/
- type: Support
  url: https://yello.co/contact/
- type: SignUp
  url: https://yello.co/request-a-demo/
- type: Pricing
  url: https://yello.co/government-recruiting/how-to-buy/
- type: TermsOfService
  url: https://yello.co/msa/
- type: PrivacyPolicy
  url: https://yello.co/privacy-policy/
- type: StatusPage
  url: https://yello.statuspage.io/
- type: Compliance
  url: https://yello.co/trust-and-security/
- type: Lifecycle
  url: lifecycle/yello-lifecycle.yml
- type: WellKnown
  url: well-known/yello-well-known.yml
- type: Conformance
  url: conformance/yello-conformance.yml
- type: DomainSecurity
  url: security/yello-domain-security.yml
- type: Conventions
  url: conventions/yello-conventions.yml
- type: Plans
  url: plans/yello-plans-pricing.yml
- type: RateLimits
  url: rate-limits/yello-rate-limits.yml
- type: Packages
  url: packages/yello-packages.yml
- type: LLMsTxt
  name: WayUp llms.txt (published)
  url: llms/yello-wayup-llms.txt
- type: LLMsTxt
  name: Yello llms.txt (generated)
  url: llms/yello-llms.txt
apis:
- name: WayUp MCP Server
  description: 'A remote Model Context Protocol (streamable HTTP) server operated by WayUp, a Yello company, at https://www.wayup.com/mcp.
    Discovered by probe: the host publishes RFC 9728 protected-resource metadata naming the endpoint and RFC 8414 authorization-server
    metadata for it. The server is fully OAuth-gated - an unauthenticated tools/list returns HTTP 401 with a WWW-Authenticate
    Bearer challenge carrying resource_metadata - so the tool set and input schemas require authenticated introspection. No
    public documentation of this server was found.'
  humanURL: https://www.wayup.com/
  baseURL: https://www.wayup.com/mcp
  image: https://yello.co/wp-content/uploads/2021/04/yello-logo@4x.png
  tags:
  - MCP
  - Job
  - Recruiting
  tags_raw:
  - Model Context Protocol
  - Jobs
  - Recruiting
  properties:
  - type: MCPServer
    url: mcp/yello-mcp.yml
  - type: Authentication
    url: authentication/yello-authentication.yml
  - type: OAuthScopes
    url: scopes/yello-scopes.yml
  aid: yello:wayup-mcp-server
x-enrichment:
  date: '2026-09-04'
  status: enriched
  artifacts_added: 17
  pass: local-v3

Yello API — frequently asked questions

Does Yello have an API?

Yes. APIs.io lists 1 API from Yello, including WayUp MCP Server.

How do I authenticate with the Yello API?

Yello documents its authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Yello Authentication.

Does Yello have an MCP server?

Yes. APIs.io lists 1 MCP server for Yello: Remote MCP server at www.wayup.com over HTTP requiring OAuth.

Is the Yello API ready for AI agents?

Yello has a Kin Score of 33.9 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/yello"

All providers

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

Every operation they expose

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

How their score was established

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