Guides
One starting point. A clear path to useful work.
An agent should understand the recruiter's goal, find the right connection, discover actual access, and return a useful result. These public docs make that contract explicit.
Agent-readable artifacts
Start here - Markdown
Routing, access checks, first value, and recovery.
Fetch MarkdownIntegration and workflow catalog - JSON
Documented routes, setup owners, prerequisites, and outcomes.
Fetch catalogHuman recipe guide
Plans for shortlist, market kickoff, and authorized ATS rediscovery.
Open recipesCandidate search reference
Canonical request, response, error, billing, rate-limit, and Try it behavior.
Open reference
Discovery that works without a browser agent
Public HTML, Markdown, structured catalogs, and current MCP tool/resource discovery remain the foundation. An index is useful only when its linked documents are retrievable.
WebMCP as an optional layer
This page exposes public catalog discovery and a workflow description. No search, contacts, authentication, or external writes are performed by the docs page itself.
Inspect the workflow output
This static sample mirrors the read-only contract an agent should infer from the public artifacts. It does not verify native browser discovery or account access.
{
"recipe_id": "shortlist",
"first_value": "A ranked slate with evidence and gaps",
"required_checks": [
"product_license",
"tenant_enablement",
"configured_connector",
"user_permission"
],
"canonical_links": [
"/reference/candidates_search",
"/reference/search_sources",
"/reference/profiles_unlock"
]
}The useful-result contract
- Use actual tool schemas, source access, and approved execution context.
- Distinguish an unavailable source from an empty search.
- Return evidence and gaps; do not invent people, contacts, profile URLs, or ROI.
- Adapt to host rendering: interactive view when supported, readable brief or table otherwise.
- Respect the recruiter's authorized action and destination.