Developers and agents

TalentPrism Developer API and MCP

Integrate with TalentPrism through a typed OpenAPI surface, the tp CLI, or MCP Streamable HTTP. All recruiting data stays authenticated and team-scoped. Public discovery endpoints reveal schemas and safety contracts without exposing candidate or customer records.

OpenAPI and REST

Start with the public OpenAPI 3.1 description or agent API overview. The predictable schema documents public discovery, tool manifests, JSON errors, authentication, and the MCP transport.

Model Context Protocol

Connect to /mcp/ using MCP Streamable HTTP. Initialization and tool discovery are public. Tool calls require a team-scoped credential. MCP v1 exposes read-only recruiting tools; mutations stay on authenticated first-party CLI and product paths with their existing confirmation policies.

Connect Claude with OAuth

Add /mcp/ as a custom connector. Sign in with an existing approved TalentPrism account, choose the authorized team, and approve read-only access. Public signup remains disabled; if your company is not yet provisioned, use the Book a Demo path below. No API key is copied into Claude.

CLI and agent guidance

Read the TalentPrism CLI guide for commands and structured errors, and llms.txt for when agents should use TalentPrism, how they should call it, and which actions are unsupported.

Disconnect and CLI compatibility

Disconnect TalentPrism from Claude's connector settings to revoke its OAuth grant. The tp CLI and existing integrations still use Authorization: Api-Key <key>; OAuth does not create, migrate, or invalidate those team-scoped keys. See auth.md for the complete protocol and error contract.