# Apply to a job for a candidate, with the person approving each submission

> Apply to a job for a candidate, with the person approving each submission: 0 companies fully do it, 4 with a limit, 20 carry the tag. Every listing in Recruiting & applicant tracking with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/recruiting.assisted-apply/
- Markdown: https://www.anchorterminal.com/niches/recruiting.assisted-apply/index.md (~1,600 tokens)
- Slim: https://www.anchorterminal.com/niches/recruiting.assisted-apply/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/recruiting.assisted-apply/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 4 | 20 | 16 | 7 |

## What counts as done

The form is filled with the CV attached and answers set, the candidate approves, the submission returns or emails a receipt the agent records against the posting, and no posting is applied to twice.

How agents ask for it: apply to this role with my tailored CV; fill in the Greenhouse form and let me check it; track which applications I've sent and who replied

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Manatal (Manatal. No registered entity is named in the terms, the DPA or the privacy policy. Offices are listed in Singapore and Bangkok, and the terms are governed by Thai law)**: Submit Application to Job Post takes the filled application form and a resume file with no security scheme in its definition, a sanctioned route for a candidate's agent, but no receipt, duplicate check or captcha policy is described.
- **NeverApply (Kasovy LLC)**: apply_to_job, answer_screening_question and approve_application gate each submission on the user's approval, and the tracker records each with status and receipt, but submission runs through NeverApply's own browser session, which its auto-apply page says continues where employer sites block AI agents.
- **Recruitee (Recruitee B.V. (Netherlands, company number 63881829), trading as Tellent. The contracting entity depends on the customer's location and can also be Recruitee Inc., Recruitee GmbH, Teamrise SAS or YooniQ Solutions GmbH)**: POST /has/:slug/candidates applies 'from candidate perspective' and sends the application confirmation email, a sanctioned route (acc-17 found only Recruitee on a verified auto-submit allowlist), but from 10 February 2027 it needs a token the employer issues.
- **SmartRecruiters (SmartRecruiters, Inc.)**: The Application API's POST /postings/:uuid/candidates applies on behalf of a candidate after GET .../configuration returns screening questions, and a status endpoint reads the result, but it is keyed for customers and partners, and acc-19 saw a confirmed submission later rejected.

- not this job: Ashby (Ashby, Inc.): applicationForm.submit is for an employer's own careers page and takes the employer's API key; no candidate-side submission route exists, so a job seeker's agent is left with the hosted form in a browser.
- not this job: Breezy HR (Breezy HR, Inc. (Jacksonville, Florida), part of Learning Technologies Group plc): No candidate-side apply route is documented; adding a candidate needs the employer's token.
- not this job: Bullhorn (Bullhorn, Inc.): No candidate-side submission route; JobSubmission writes need the agency's credentials.
- not this job: Gem (Gem Software, Inc.): Gem is an employer-side ATS and CRM; nothing on the readable pages has a candidate-side submission route, and its job board API is employer-keyed per the listing.
- not this job: Greenhouse (Greenhouse Software, Inc.): The Job Board API's application POST needs the employer's secret key, which the docs say must never be exposed client-side, so a candidate's agent has no sanctioned submission route.
- not this job: Himalayas Remote Jobs MCP (Himalayas Remote Jobs Pty Ltd): get_apply_link returns the employer's own application link (50 a day) and save_job tracks it, but nothing fills or submits the form, so submission stays with the candidate on the employer's site.
- not this job: Lever (Employ, Inc.): The Postings API apply POST needs a key a Super Admin generates, sent in the query string, so it is for employers' own careers pages; a candidate's agent has no sanctioned route.
- not this job: Pinpoint (The Infuse Group Limited, trading as Pinpoint Software (Jersey, registration number 124135)): Create Application needs the employer's API key; no candidate-side route is documented.
- not this job: Teamtailor (Teamtailor AB (Sweden, registration number 556936-6668), Östgötagatan 16, Stockholm): Creating a job application needs the employer's Admin key; no candidate-side submission route is documented.
- not this job: Workable (Workable Software Limited (England and Wales, company number 08125469), with Workable Inc. in the US and Workable Software Single Member Private Company in Greece): POST /jobs/:shortcode/candidates needs the employer's token with w_candidates; no candidate-side submission route is documented.
- not this job: Zoho Recruit (Zoho Corporation Private Limited): No candidate-side submission route; creating candidates and applications needs the employer's OAuth grant.

## What stops agents finishing

- captcha or two-factor code on the form, which tools may not solve
- no sanctioned candidate-side submission route, so only browser automation remains
- employer terms against automated applications

## Around it

Before: recruiting.job-discovery. After: mailbox-access.read-message, spreadsheets.append-row.

## Where this comes from

Weight 16 of 100 in Recruiting & applicant tracking: 7 of 32 accounts; job-seeker agents and extensions prefilling Greenhouse, Lever, Ashby and SmartRecruiters forms, an agent-kept application log on GitHub, and builders checking which ATSs allow automated submission (only Recruitee on one allowlist).

As data: https://www.anchorterminal.com/api/v1/use-cases/recruiting.assisted-apply.json, or the MCP tool get_use_case with id recruiting.assisted-apply. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
