Build with the Vitae AI developer platform.
Use the versioned REST API for direct integrations or connect an agent through the hosted Model Context Protocol server. Both surfaces use documented schemas, scoped authorization, tenant isolation, and approval gates for governed actions.
Start from a machine-readable contract.
Vitae AI API documentation
Authentication, endpoint guides, examples, and integration concepts for the versioned REST API.
Read API docs →Vitae AI OpenAPI contract
The machine-readable OpenAPI 3 contract with operation IDs, request schemas, response schemas, and typed errors.
Open OpenAPI JSON →Vitae AI OAuth 2.1 discovery
Authorization-server metadata for OAuth authorization code with PKCE and dynamic public-client registration.
Open OAuth metadata →Vitae AI MCP server
Connect an MCP-compatible client to recruiting tools using Streamable HTTP and the same authorization boundaries as the product.
Set up MCP →Conventions agents can rely on.
Versioning
Stable REST operations use the major version in the URL, beginning with /v1. Breaking request or response changes require a new major path.
Deprecation
A deprecated stable version is announced with migration guidance. Responses may use Deprecation, Sunset, and Link headers to identify the replacement and removal date.
Rate limits
Responses publish current IETF RateLimit and RateLimit-Policy fields plus compatibility headers. A 429 includes Retry-After.