Documentation
Last updated: August 19, 2026
Reqline keeps one base resume you have reviewed and verified, and builds tailored, ATS scored PDFs from it. The Claude connector is how you tailor today, and the web app is where your resume, your builds, and your job tracker live. Uploading a resume PDF on the site and tailoring inside the app are both coming soon; this page says so wherever it matters.
What Reqline does
Your verified base resume is the source of truth for your history. When you supply a job description, the service does four things:
- checks whether the posting and your background are about the same work, and says so plainly when they are not;
- reorders and rewords your verified content against the posting's own terminology;
- validates the result against your base resume and refuses anything it cannot ground there;
- builds an ATS safe PDF and scores it.
The service is a free beta. It writes resumes from content you gave it, and it does not apply to jobs for you, send anything to an employer, or contact anyone on your behalf.
Getting started
- Sign in. Use your Google account. There is no password to create. Signing in lands you on the Claude connector page, which is the first thing to set up.
- Add the connector to Claude. Paste the connector URL into Claude on web or desktop and sign in with the same Google account. The full steps are on that page and in outline below.
- Give it your resume. Paste or attach your resume in the chat and ask Claude to save it as your base resume. It is stored as structured content: summary, jobs and their bullets, skills, education, certifications, awards, and publications. Uploading a PDF on the site is coming soon.
- Review every field and verify it. Open the base resume editor in the app, fix anything that came across wrong, and save. Nothing builds until a resume is marked verified, in the app or through the connector.
- Tailor. Ask Claude for a resume tailored to a posting. Tailoring inside the app is coming soon, so the Tailor page is greyed out for now.
The Claude connector
The connector is an MCP server. Adding it lets Claude read your verified resume and build tailored PDFs inside any chat, so you never paste your resume into a conversation. It reaches only your own account.
Connecting
The Claude connector page in your dashboard has an Add to Claude button, which opens Claude with the connector URL already filled in. Use it on Claude web or desktop; the iOS app has no option to add a connector, and it reaches your mobile chats once it is connected anyway. Two steps follow:
- Claude shows the name and URL, flagged as having come from an external link. Check them and choose Add.
- Sign in with Google when Claude asks. Use the same account you sign in here with; any other account is refused.
To add it by hand instead, open Customize, then Connectors, in Claude, click +, choose Add custom connector, and paste the URL from the same page. There is nothing to fill in under advanced settings.
Signing in is what identifies you, and the connector reaches only the account you signed in with. To disconnect, remove the connector in Claude. Access ends there, and nothing here has to be revoked.
Claude writes the draft. The connector validates it, scores it, and builds the PDF. No tool on the server sends your resume to a model provider of its own. Using the connector means your conversation is governed by Anthropic's privacy policy and your own Claude settings, alongside ours.
What the connector can do
Twenty tools, with reads and writes kept separate. The thirteen that write carry the MCP destructive hint, so Claude asks for your approval before running them.
Five of them answer with an interactive card in the chat, wherever Claude renders MCP apps. Scoring a draft returns the ATS check card, with the coverage meter, the pass bar, and the missing terms as chips. Building returns the report card, with both scores and the download button. Listing your applications returns the board, a row per job that opens the posting and the resumes built for it. The two search-criteria tools return a picker whose answers save as you tap them. On a surface that does not render cards, the same tools answer in plain text and nothing is lost.
| Tool | What it does | Writes |
|---|---|---|
| Start a tailoring session | Checks your verified resume against one job posting and returns a fit verdict, keyword coverage, and the terms the posting weights most. The posting can be pasted in, or taken from a job already on your tracker. | No |
| Score a tailored draft | Checks a draft against your verified resume and the posting, and reports what still needs work. Stores nothing. The posting can be pasted in, or taken from a job already on your tracker. | No |
| Build the tailored resume PDF | Builds the PDF, scores it, stores it with your build history and the job it was built for, and returns a download link. Naming a job on your tracker supplies its stored posting too, so the text is not pasted again to build what was just scored. | Yes |
| Save a tailoring preference | Saves one short instruction that applies to every later tailoring session for your account, and returns its id so it can be removed again without looking it up. | Yes |
| List saved tailoring preferences | Returns your saved preferences with their ids, including any that are disabled. | No |
| Delete a saved tailoring preference | Removes one saved preference by its id and returns the deleted sentence in full, so it can be saved again if you change your mind. | Yes |
| Curate a posting's keyword list | Replaces the word list a posting is scored against. Left alone, the server picks keywords by counting words, which cannot tell a skill from ordinary prose and cannot produce a phrase like “context engineering” at all. Claude reads the posting and sends the terms an ATS would really search for, and every later score of that job uses them. | Yes |
| Choose the keywords the PDF bolds | Picks which terms print bold in the experience bullets, so the page reads to a recruiter the way it scores to a filter. Claude names the terms it worked into the draft; the server bolds them only where your bullets already say them, in the spelling your bullets use, and reports the ones it could not find. It cannot add a word to the resume. | Yes |
| Set the resume layout | Saves how the page is arranged: which order the sections print in, what the skills section is called, the margins, and the spacing. Every later build starts from it, including builds from the web app. It cannot change a word of what the resume says. | Yes |
| Read the base resume | Returns your stored base resume. | No |
| Update the base resume | Edits one part of your stored base resume in place and leaves the rest alone. The change applies to every resume built afterwards. | Yes |
| Save a base resume | Stores a resume you supply in the conversation as your base resume, without going through the web uploader. | Yes |
| List tracked job applications | Returns the jobs on your tracker, best fit first, with each one's score and the posting terms your resume does not cover. The posting text and your notes stay out of it. | No |
| Track a job application | Adds a job to your tracker and scores its posting against your verified resume at the same time. A weak score is still saved. | Yes |
| Read one tracked job application | Returns one job on your tracker in full, including the stored posting text and your notes, which the list leaves out. | No |
| Update a tracked job application | Changes one job on your tracker, leaving anything it does not mention alone. Replacing the posting scores the new text and discards the previous score. | Yes |
| Rescore tracked job applications | Recomputes the scores on your tracker against your resume as it stands now, in one call rather than one call per job. Editing your resume is what makes them stale; saving it again without changing a word does not. | Yes |
| Delete a tracked job application | Removes one job from your tracker permanently, along with its stored posting, your notes, and its score. Claude puts the deletion to you by name before anything is removed. | Yes |
| Read job search criteria | Returns what you told us you are looking for: target roles, where you are based, relocation, salary floor, contract work, company size and stage, employer rating, and whether you want to manage people. Also returns the next few questions when any are still unanswered. | No |
| Save job search criteria | Stores your answers to those questions, one or several at a time, and remembers the ones you skipped so they are not asked again. Your criteria rank your tracker and flag jobs that contradict them; they never stop a resume being tailored or built. | Yes |
An approval prompt shows you the raw request. The two tools that change your stored base resume, and the one that deletes a tracked job, go further and put the change itself to you before anything is written, naming what would be rewritten, replaced, or removed. Declining writes nothing, and nothing the assistant can set on its own turns that decline into a yes.
When a posting and your background are about different work, the session comes back as a plain no with the reason. No resume content leaves the server for that posting, and no PDF can be built from it.
The tracker is the exception, and deliberately so. A job you save keeps its score whatever the score is, because a weak match is something worth knowing about a job rather than a reason to forget you found it. Refusing to write a resume and refusing to remember a posting are separate decisions, and only the first one is made for you.
What tailoring will and will not do
Tailoring reorders and rewords experience you have already verified:
- bullets get reordered so the most relevant ones lead;
- bullets and the summary get rewritten using the posting's exact terms;
- skills get regrouped;
- you choose which of your stored certifications print, and in what order.
It will not invent metrics, employers, titles, or dates. The server validates every draft against your stored resume and returns a specific error instead of building. Tools and technologies your demonstrated experience makes probable may be named even when the stored resume does not spell them out. Numbers and employment facts may not.
Drafts are also refused for punctuation and phrasing the house style rules out, and for anything past the length limits.
None of that makes a resume true. You are responsible for what you send to an employer, so read the PDF before you send it.
What the score means
The score combines weighted keyword coverage with formatting checks, weighting terms roughly the way applicant tracking systems do. A high score reads as comfortable coverage. A low one usually means the resume and the posting are about different work, which is reported as that rather than as a number to chase.
Nothing withholds a build over a score. It is an estimate of how a keyword filter is likely to read the document, not a prediction of what any particular employer's system or recruiter will do, and it is never shared with an employer. It does not guarantee interviews or any hiring outcome.
Limits
The limits you are most likely to meet. Some are settings on your account, so your own numbers can differ; the connector reports your remaining daily builds with every build.
| Limit | Value |
|---|---|
| Builds | 20 per day, counted from midnight UTC |
| Stored resume documents | 3 per account. Saving another removes the oldest that is not active |
| Stored build PDFs | 20, the newest kept and tied to their applications. Older PDFs are deleted permanently; the history entries stay |
| Download link lifetime | 1 hour. The PDF itself stays stored: the dashboard and the tracked application mint fresh links at any time |
| Bullets per job | 7, which is what the page layout fits |
| Summary length | 75 words |
A build refused by validation still counts against the daily limit. Scoring a draft does not, so there is no cost to scoring again after a fix.
Your data
The privacy policy is the full account: what is collected, who processes it, where it lives, and how long it is kept. In short, your resume content is used to serve you and nothing else. It is never used to train models, never shown to another user, and never sold or shared for advertising. Extracting a resume from a PDF and tailoring inside the web app send your resume text and the job description to an AI provider, which the privacy policy sets out in detail.
You can edit anything, delete individual items, and delete your whole account from account settings. Account deletion is immediate and unrecoverable. The terms of service cover the rest of the arrangement.
Support
Email support@reqline.app with a question, a bug, or a resume that came out wrong. Errors from the connector name what to fix, and support can walk through anything they do not. Reqline is a free service run by one developer, so replies come as fast as one person can manage rather than on a support contract.
Data requests, corrections, deletions, and privacy complaints go to privacy@reqline.app instead, and are answered on the timelines set out in the privacy policy.