Agent Docs

Affinity Talent API and Agent Discovery

This page documents the machine-readable resources published by affinitytalent.bio for role discovery, candidate submission, and agent integrations.

Discovery

Published discovery endpoints

/.well-known/api-catalog returns the API catalog as application/linkset+json.
/.well-known/mcp/server-card.json describes the remote MCP endpoint.
/.well-known/agent-skills/index.json lists available skill artifacts.

/llms.txt and /llms-full.txt provide LLM-oriented site summaries.
Public HTML pages return markdown when the request sends Accept: text/markdown.
/robots.txt includes Content-Signal directives for AI usage preferences.

REST API

Candidate submission API

The public form posts to POST /api/submit-candidate. The machine-readable description lives at /openapi/submit-candidate.json.

This endpoint is designed for the website's own candidate form flow. It validates origin, rate-limits requests, accepts multipart form uploads, and currently expects name and email plus any optional profile fields the form provides.

POST /api/submit-candidate
Content-Type: multipart/form-data | application/json

200 {"ok": true}
4xx/5xx {"error": "..."}

MCP

Remote MCP endpoint

/api/mcp exposes a lightweight stateless MCP server over Streamable HTTP. It currently supports role discovery and opening site actions.

initialize negotiates protocol version 2025-06-18.
tools/list returns the four published site tools.
tools/call supports list_open_roles, get_role_brief, open_candidate_submission, and open_discovery_call.
GET /api/mcp currently returns 405, which signals that no SSE stream is offered on this deployment.

Browser Tools

WebMCP on the public site

The browser app calls navigator.modelContext.provideContext() on load to expose equivalent site tools directly in compatible browsers and agent runtimes.

The browser-side tools can navigate to the candidate form or open the discovery call page, while the remote MCP server returns the same live URLs as structured results.

Auth

Authentication status

The currently published role-discovery and candidate-site endpoints do not rely on a dedicated OAuth or OIDC authorization server. The site therefore publishes discovery for its public APIs and MCP surface, but does not advertise a non-functional OAuth issuer.