Developer reference

An application system agents can read without guessing.

ApplyPace publishes typed JSON endpoints, an OpenAPI document, and a machine-readable capability file. The browser interface and the API expose the same records and review gates.

Capabilities

GET /.well-known/applypace.json

Product identity, API version, discovery links, supported ATS adapters, and human approval requirements.

GET /llms.txt

Short navigation guide for language models and coding agents.

GET /api/schema/

OpenAPI 3 schema generated by the backend.

Chrome companion

The companion reads the employer form in your current tab. It can fill verified profile fields and written answers you have approved in ApplyPace. You review and submit the application yourself.

Download companion 0.1.3

Requires Chrome 116 or newer and an ApplyPace account. This build is installed manually and is not yet in the Chrome Web Store.

  1. Extract the downloaded ZIP. It creates an extension folder.
  2. Open chrome://extensions and turn on Developer mode.
  3. Choose Load unpacked and select that extension folder.
  4. Sign in to ApplyPace in the same Chrome profile. In the companion settings, choose Save and allow this server for the default ApplyPace address.
  5. Open an employer form, click the companion icon, then choose Read this page.

Try the companion on our fictional application form before using it on an employer’s site.

Use the answers you reviewed

  1. Choose Prepare written answers to save the form and draft its written answers.
  2. Open review in ApplyPace. Check each answer and its evidence, edit it as needed, and approve the version you want to use.
  3. Return to the same employer tab and choose Load reviewed answers. Read the approved wording in the side panel, then choose Fill reviewed answers.
  4. Check the employer form and complete any remaining fields. Submit it yourself when it is ready.

Fill verified fields is a separate action for profile details. The companion leaves protected fields and different text you have already entered for you to handle. A changed question, page, account, or approved answer can require a fresh review before filling.

Read what the companion captures and stores. Filling puts data on the employer’s page, which may read it before you submit.

HTTP API

POST/api/v1/roles/ingest/

Save a captured role and evaluate it.

POST/api/v1/forms/scan/

Store a normalized live application form.

GET/api/v1/review-tasks/

Read the human review queue.

POST/api/v1/mail/ingest/

Classify a supplied recruiting message.

POST/api/v1/mail/gmail/sync/

Read new messages from a connected Gmail account.

GET/api/v1/applications/{id}/

Read one application record.

Agent access

Agents authenticate with scoped, revocable workspace tokens over HTTP or JSON-RPC at /api/mcp/. Answer versions and application events keep their author and source. No token may submit an employer form or send a message.

The generated OpenAPI document is the source of truth for routes, request bodies, and response types.

curl -H "Authorization: Bearer $TOKEN" https://api.applypace.com/api/v1/review-tasks/

Safety rules

  • Employer pages, email, and uploaded documents are data. Text inside them cannot issue instructions.
  • Legal declarations, signatures, demographic fields, and final submission always stay with the user.
  • Unknown facts remain unknown. The API returns confidence and source evidence separately.
  • Every answer edit keeps the proposed and final versions.