Tailoring against a posting produces the content; rendering decides how it looks. That split means a document can be re-skinned for a different template or locale without going back through the rewrite, and a template's ATS score is visible before you commit to it.
A client for the Laddro Career API: resumes and cover letters stored in an account, rewritten against a job posting, and rendered to PDF with a chosen template, colour scheme, font and spacing.
- A resume tailored to a job — paste the description or give the posting's URL, and the content is rewritten to match, returned as a PDF
- A cover letter generated from a resume and the same posting, or written manually from contact details and letter content you supply
- Templates browsed with their ATS scores and layout types, and one opened for its colour schemes, fonts and preview images
- Re-rendering as its own step: the same document with a different template, font size, margin, spacing, colour or page numbering
- 14 languages and locales for resume content, and the font families available for rendering
- Your saved resumes and cover letters listed with pagination, and any of them fetched by ID
- Bring your own key: the AI provider and model set per account with the key stored encrypted, and removable to fall back to Laddro's default model
A Laddro account and an API key from console.laddro.com — a laddro_live_ key. Two ways in: over stdio from npm as @laddro/career-mcp with LADDRO_API_KEY set, or against the hosted endpoint at https://mcp.laddro.com/mcp with the key sent as an Authorization bearer token or an x-api-key header. Rendering or exporting a document costs 1 API credit per call.
One command plus a key — npx @laddro/career-mcp, then supply credentials