QuickHire for developers
QuickHire Developer Resources
Everything needed to build an integration with QuickHire or connect an AI agent to it: a full REST API reference, an MCP server, and the machine-readable files QuickHire publishes for search engines and LLMs.
Resources
- REST API referenceOpenAPI 3.0 (JSON)
The full public API surface: browse the service catalog, get a price quote, read talent/PM profiles, and manage a customer session. Every operation has a unique operationId, a description, and typed parameters/responses.
/openapi.json→ - MCP serverModel Context Protocol, Streamable HTTP
Call QuickHire as MCP tools from an agent runtime (Claude, ChatGPT, or any MCP client) — search the catalog, get quotes, and look up markets without a bespoke integration. POST a JSON-RPC 2.0 request to get started.
/mcp→ - Agent instructionsPlain text
When an AI agent should reach for QuickHire, when it shouldn’t, and how to call it programmatically.
/agent.txt→ - Site map for LLMsPlain text (llmstxt.org)
A curated, low-noise summary of QuickHire and a link map to every solution hub, service, and market a fast way for an assistant to ground answers about QuickHire.
/llms.txt→ - Full URL indexPlain text
Every indexable page on the site, including individual talent profiles.
/llms-full.txt→ - XML sitemapXML
The complete, machine-readable page index used by search engines.
/sitemap.xml→
Authentication
Endpoints that read public catalog/content data need no authentication. Endpoints that act on a specific customer (bookings, payments, chat, account) require a bearer JWT, obtained via the Auth endpoints in the OpenAPI spec (POST /auth/send-otp + POST /auth/verify-otp, or POST /auth/guest-access for an anonymous session). Send it as Authorization: Bearer <token>.
Rate limits
Every response carries standard RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers so a caller can self-throttle; a 429 response also carries Retry-After.