# PeppyJobs auth.md

How AI agents and software get access to PeppyJobs (https://peppyjobs.com).

## Who this is for

- **Any agent, no sign-in:** public, read-only job search and salaries through the MCP server (https://peppyjobs.com/mcp), the A2A agent (https://peppyjobs.com/a2a) and the website. No credentials are needed or issued.
- **Employers on the Pro plan:** their own software or AI assistant can manage the company's jobs and applicants through the REST API (https://peppyjobs.com/api/v1) and the employer tools of the MCP server.

## How an employer gets a credential (provisioning)

1. An owner or admin of a company on the Pro plan signs in at https://peppyjobs.com/login and opens https://peppyjobs.com/hire/developers.
2. They create an API key there. The key looks like `pj_live_...` and is shown once; PeppyJobs keeps only its hash.
3. Up to 10 keys per company. Revoke a key on the same page at any time.

There is no self-service registration endpoint for agents and no OAuth flow. A key is always made by a person at the company.

## Supported method

- **API key, bearer token:** send `Authorization: Bearer pj_live_...` with every request.

## Using the credential

- REST API: `https://peppyjobs.com/api/v1`, described in OpenAPI at https://peppyjobs.com/api/v1/openapi.json.
- MCP: connect to `https://peppyjobs.com/mcp` (Streamable HTTP) with the same header. Without a key you see the public tools; with a valid Pro key you also see list_my_jobs, get_my_job, create_job, list_applications, get_application and move_application.
- Every request is limited to the key's own company. Limit: 120 requests a minute per key. Candidate phone numbers and emails are shown only after the candidate accepted the company's contact request.

## Errors

- 401: missing, invalid or revoked key.
- 403: the company is not on the Pro plan, or is blocked.
- 429: too many requests; wait a minute.

Questions: support@peppyjobs.com. Security reports: https://peppyjobs.com/.well-known/security.txt.
