# Connect Hirify

Choose one connection method that fits the environment. All three methods use the same Hirify
Agent API capabilities and allowances.

Once connected, read https://hirify.me/agent-playbook.txt once per session. It is the working
method: learning the person, setting up the search, scoring a vacancy and applying.

## CLI agent

Use this for a local coding or terminal agent.

```sh
npx -y hirify-cli@latest init
```

The command needs Node 18 or newer. It installs the `hirify` CLI, adds the `hirify` skill to the
agents found on the computer and opens Hirify in the browser so the user can sign in, accept the
access terms and approve the connection. Run it yourself and ask the user to confirm in the browser.
The skill provides the working order for searching, reading vacancies and applying.

## Web or cloud agent

Add `https://api.hirify.me/api/mcp` as an MCP server. Hirify opens in the browser for sign-in,
terms and approval. Choose MCP when the environment supports connectors and should not install local
software.

## REST API

Use REST for application code and the user's own service. The user starts at
`https://hirify.me/mcp-api`, chooses API, accepts the access terms and creates an
API key. For this REST method, ask the user for that key and send it as a Bearer token to
`https://api.hirify.me/api/agent`.

Read the complete machine contract at `https://api.hirify.me/api/agent/openapi.json` before writing
the integration.

For automatic processing of new vacancies, read
`https://hirify.me/agent-automation-guide.txt` before designing the service.

## Applying

A vacancy card carries `can_apply_directly`. When it is true, the application can be sent through
Hirify. Everywhere else `vacancy reveal` returns the destination - a link, a form or an address -
and the application is made there. What happens at that destination is between you and your user.