JobRipe for AI agents and developers

Searching needs no key (lower limits). Everything that acts for you needs a key from API keys.

curl "https://jobripe.com/api/agent/v1/jobs?q=registered%20nurse&where=Toronto&page_size=5"

curl "https://jobripe.com/api/agent/v1/jobs/JOB_SLUG"

curl -X POST "https://jobripe.com/api/agent/v1/saved" \
  -H "Authorization: Bearer jrk_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"slug": "JOB_SLUG"}'

curl -X POST "https://jobripe.com/api/agent/v1/alerts" \
  -H "Authorization: Bearer jrk_YOUR_KEY" -H "Content-Type: application/json" \
  -d '{"name": "Nurse jobs in Toronto", "q": "nurse", "where": "Toronto", "frequency": "daily"}'

curl -X POST "https://jobripe.com/api/agent/v1/applications" \
  -H "Authorization: Bearer jrk_YOUR_KEY" -H "Content-Type: application/json" \
  -d '{"slug": "JOB_SLUG", "cover_note": "Text the person approved", "answers": [], "human_confirmed": true}'

Send the key as Authorization: Bearer jrk_… or X-API-Key: jrk_…. Keys work only on the agent API and MCP. They never sign anyone in to the website, and website sign-in tokens are refused by the agent API.

A key acts as you and never with more rights than your account has. Each key has a per-minute limit and a daily cap that you choose (up to 120 a minute and 5,000 a day). Without a key: search, job details and company facts only, at a lower per-address limit. Over a limit you get HTTP 429 with Retry-After.

Applying through an agent is limited to a few applications per person per day (all keys together), only to jobs that take applications on JobRipe, and only with human_confirmed: true. Jobs on an employer's own site return their link instead.

Every call made with your keys is listed in the audit log on the API keys page.

Full schema: https://jobripe.com/api/agent/v1/openapi.json (OpenAPI 3).

• GET /api/agent/v1/jobs?q=&where=

  Search open jobs by keywords and place, with pay, trust, freshness and reply speed.

  Scope: none needed · MCP tool: search_jobs

• GET /api/agent/v1/jobs/{slug}

  One job in full: description, screening questions, trust reasons and warning flags, how to apply.

  Scope: none needed · MCP tool: get_job

• GET /api/agent/v1/companies/{slug}

  Company facts, business-register check, measured reply rates, review signal.

  Scope: none needed · MCP tool: get_company

• POST /api/agent/v1/saved

  Save a job to the person's list.

  Scope: saved:write · MCP tool: save_job

• POST /api/agent/v1/alerts

  Create an email job alert for a search.

  Scope: alerts:write · MCP tool: create_alert

• POST /api/agent/v1/applications

  Apply to a job that takes applications on JobRipe. Needs human_confirmed: true; a few a day.

  Scope: applications:write · MCP tool: apply_to_job

• GET /api/agent/v1/employer/jobs

  Employers: your jobs with applicant counts.

  Scope: employer:jobs · MCP tool: list_my_jobs

• GET /api/agent/v1/employer/jobs/{id}/applicants

  Employers: applicants for one job (full resumes stay in the dashboard).

  Scope: employer:jobs · MCP tool: list_applicants

• PATCH /api/agent/v1/employer/applicants/{id}

  Employers: move an applicant or add a private note.

  Scope: employer:jobs · MCP tool: update_applicant_stage

GET /api/agent/v1/me shows the calling key, its scopes and what is left today.

• Pay exactly as given. pay.published is the employer's own figure. pay.estimate comes from similar jobs: always call it an estimate (“est.”), never the employer's number. When both are empty, say the pay isn't published.
• Verified means verified. Only call a job verified when trust.level is verified. listed means a copy from a public job board that JobRipe can't confirm with the employer. Pass on caution flags.
• No invented numbers. Reply speed is measured only from applications sent through JobRipe, and star ratings exist only with 5 or more verified reviews. If a field is empty, the answer is “not enough data”.
• The person decides. Apply only after the person read the job and approved the exact cover note and answers, then send human_confirmed: true. Never set it on your own.
• Link back. Give the person the job's url so they can check it themselves.

• Use the API for the person who owns the key (or, without a key, for your own users' searches). Don't copy JobRipe's listings into another job board or database, and don't try to get around the limits with extra keys or addresses.
• No mass applying. Agents can send a few applications per person per day, only with that person's confirmation of each one.
• Keep keys secret. Anyone with a key can act as you within its scopes: revoke it at once at API keys if it leaks.
• Keys and their limits may be suspended for abuse. The site terms and privacy policy apply.