canonical: https://jentic.com/apis/applystead.com/applystead # Applystead API The Applystead API searches job listings and queues applications on a job seeker's behalf from their own code. It returns open jobs and company facts, lets a caller add a job to an application queue, and reports what each call charged and the balance left on a prepaid account. Webhook endpoints notify an HTTPS, Discord, or Slack destination as soon as a queued application is sent, and applications that are never sent are refunded automatically. ## For AI agents Search open jobs, look up company facts, queue job applications, and track their status and charges on a prepaid balance. Register webhooks that fire when an application is sent. Reads and writes authenticate with a bearer key. ## Scope Does not post job listings, run payroll, or manage employee records. Use for searching jobs and queuing a candidate's own applications only. ## Capabilities - Search open jobs and read a single job's details - Look up company facts by website domain or name - Queue a job application and track its status until it is sent - List submitted applications and read each one's charge and remaining balance - Register webhook endpoints that fire when an application is sent - Read the account plan, prices, and prepaid balance ## Use cases ### Automated Job Application Queue An agent searches Applystead for open roles that match a candidate's criteria, reads the company facts behind each listing, and queues the strongest matches to apply. Each queued application reports its charge against the prepaid balance, and anything never sent is refunded automatically, so the agent can batch applications without overspending. Example prompt: Call GET /jobs with a search term, then POST /applications to queue the chosen job and GET `/applications/{id}` to confirm its status ### Job Search Monitoring A monitoring workflow polls Applystead for newly posted jobs that match a saved search and enriches each with company facts before alerting the candidate. The agent reads jobs and companies on a schedule so new openings surface without manual browsing. Example prompt: Call GET /jobs to list current openings, then GET /companies to add firmographic context for each result ### AI Agent Integration via Jentic An AI agent reaches Applystead through Jentic without holding the bearer key itself. It searches by intent, receives the matching operation with its input schema, and executes the call with the credential injected at run time, so job search and application queuing become steps in a larger agent workflow. Example prompt: Search Jentic for 'search open jobs', load the GET /jobs schema, and execute it with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/jobs` | Search open jobs | | GET | `/jobs/{id}` | Get one open job | | GET | `/companies` | Company facts by domain or name | | POST | `/applications` | Add a job to the queue to apply | | GET | `/applications` | List submitted applications | | GET | `/applications/{id}` | Get one application | | POST | `/webhooks` | Add a webhook endpoint | | GET | `/me` | Account, plan, prices, and balance | ## Key resources - **Jobs and Companies** — Search open jobs and read company facts via /jobs, `/jobs/{id}`, and /companies - **Applications** — Queue and track applications via /applications and `/applications/{id}` - **Account and Webhooks** — Read account balance and manage delivery webhooks via /me, /usage, and /webhooks ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 47 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 81 / 100 - Developer Experience & Jentic Compatibility: 69 / 100 - AI-Readiness & Agent Experience: 23 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 55 / 100 - **View full report:** https://jentic.com/apis/applystead.com/applystead/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring Applystead by hand means managing its bearer key, reading the charge and balance on every response, and tracking which queued applications were sent yourself. Through Jentic you install once, import Applystead from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Applystead carries the job id and application details inside each request, so a rule bounds which operations your agent may call rather than which listing it touches. You choose the operations it may use, such as job search and queuing an application, so webhook deletion is not included unless you add it. - **Credential handling:** Your Applystead key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'search open jobs' or 'queue a job application', and Jentic returns the matching Applystead operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Adzuna** — Job search aggregator with salary and listing data - **ZipRecruiter** — Job board with search and listing endpoints - **Greenhouse** — Applicant tracking system for employers to manage hiring ## FAQ ### What authentication does the Applystead API use? The Applystead API authenticates with a bearer key sent as Authorization: Bearer , per its OpenAPI spec, with keys created on the API page in Applystead. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent. ### Can I queue a job application with the Applystead API? Yes. POST /applications adds a job to your queue to apply, and GET `/applications/{id}` returns the status of that application until it is sent. Each call reports what it charged against your prepaid balance, and an application that is never sent is refunded automatically. ### What are the rate limits for the Applystead API? Applystead charges per call from a prepaid balance rather than enforcing a fixed rate ceiling, and the OpenAPI spec does not state request limits. Read the balance from the account endpoint before a batch, watch for HTTP 429 responses, and check Applystead's documentation for current limits. ### How do I search open jobs with the Applystead API through Jentic? Search Jentic for 'search open jobs', and it returns the Applystead operation with its input schema. Load the schema and execute GET /jobs with the credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Is there an Applystead MCP server? You don't need an MCP server to give your agent Applystead. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the job and application operations it needs. Operations are discovered on demand, so no extra server's tool definitions sit in the agent's context. ### Can I limit what my agent is allowed to do with the Applystead API? Yes. Applystead carries the job and application details inside each request, so a rule bounds which operations your agent may call. Allow only job search and the queue operation, for example, so the agent can find and apply to roles while webhook deletion stays off the table, and every call runs through your own instance where it is logged.