A résumé that machines
can actually read.
Hiring runs on software now — ATS parsers, AI recruiters, matching bots. They choke on PDFs. cv.json publishes your CV as one live link they read perfectly, while people still see a beautiful page.
Watch a machine read it.
Same person, same facts. One the software has to guess at. One it just knows.
A PDF is a picture of your career. cv.json is the data underneath it — and data is what gets you found.
One link. Everything a résumé can't do.
No app, no export, nothing to configure. You decide exactly what's public.
Create yours — free- 01One stable link, forever.Your CV lives at
/cv.json. Share a URL, not a fresh attachment every time. - 02Always current.Edit once — the link updates the same second. No stale copies in inboxes.
- 03Read perfectly by AI & ATS.Clean structured fields, not a guessed-at PDF. You get parsed right, every time.
- 04Hiring signals, optional.Quietly say you're open, your roles, remote/onsite, visa needs — what matchers actually use.
- 05Privacy you control.Contact details hidden by default. Flip what's public with one toggle.
- 06Yours. Open forever.MIT licensed, not locked to any company. Take it to any builder, any host.
Three steps. Zero tech.
Publish
Your CV gets a permanent home — and a matching /cv.json data version, automatically.
Be discovered
A tiny tag tells machines "the data's here." AI tools and ATS follow it without being told.
Get read
Any tool — a recruiter's AI, an ATS, a matcher — reads the exact same accurate data. No errors.
This is a live cv.json.
Ashley's CV — the data behind her portfolio. Open it, feed it to an AI, point an ATS at it. Always up to date.
A standard, not a product.
Open, versioned, and compatible with what tools already understand. No company owns your career.
An image machines guess at, vs clean data that's always current and parsed perfectly.
Keeps the compatible field names, then adds discovery, versioning, hiring signals, and privacy.
No bloat, no rigidity — a lightweight file ATS and AI actually read, not an EU form.
<link rel="alternate" type="application/json"> + /.well-known/cv.jsonX-CV-Version · Link: rel="describedby" · open CORScvjson.com/schema/v1.jsonnpm i cv-json soon — validate + map to/from JSON ResumeGood to know.
What is cv.json?
An open standard that publishes a CV as structured JSON at a stable URL (e.g. https://yoursite/cv.json), so AI recruiters, ATS systems, and tools read your career data directly instead of parsing a PDF.
How is it different from a PDF résumé?
A PDF is a frozen image machines parse poorly and that goes stale the moment you change jobs. cv.json is live structured data at one link that updates automatically and is read perfectly by AI and ATS — while a matching web page stays readable by people.
Isn't this just JSON Resume?
It keeps JSON Resume's compatible field names for interoperability, then adds what adoption actually needs: a discovery mechanism so machines find your file, versioning, optional hiring signals (open-to-work, roles, work authorization), and a privacy model.
Is it free and open?
Yes — MIT licensed and fully open. Anyone can implement it, no single company owns it, and your data stays portable across builders and hosts.
Résumés are read by machines now, but every format fights them. We made cv.json an open standard so your career data belongs to you — not a platform.