A1 Verified — 11 document-backed · 2 attestedA1 Verified ✓11 document-backed · 2 attested

A1 Verified Prep

The authenticity layer under A1's recruiter workbench, hiring-manager portal, and portable badge. A tamper-evident, candidate-consented record of where every tailored line came from: traced to the CV file the candidate uploaded, or marked as the candidate's own word. The same graded evidence powers the ranking recruiters see, the shortlist hiring managers review, and a signed badge any ATS or portfolio can render and re-verify.

Evidence-grounded

Every tailored line is checked against the CV file the candidate uploaded and labelled: document-backed, or the candidate's own word. Fabrications are flagged, never counted as backed — and no line is ever folded into a score.

Candidate-consented

The badge only resolves while the candidate has opted to share it for that application. Turn sharing off and the endpoint returns 404 — no data, no trace.

Tamper-evident

Each payload is canonicalised (JCS) and signed with HMAC-SHA256. Change one character and the signature no longer verifies.

Revocable

A cached badge can be re-checked at any time. If the candidate later withdraws consent, verify reports consent_still_active: false.

What each label means

The signature proves the record wasn't altered. This explains what the labels mean — the record carries the counts behind them, so it's never a black box, and never a score.

Every tailored line is checked against the CV file the candidate uploaded — the evidence ledger — and lands in one of four states:

  • Grounded — read straight from the uploaded file.
  • Reframed — the same facts, re-emphasised for the role; still defensible from the file.
  • Unsupported — not found in the file; the candidate must confirm it or remove it before sending.
  • Couldn't verify — reported as such, never silently promoted.

What leaves A1 is the composition: how many lines are document-backed (grounded or reframed) and how many are the candidate's own word — supplied by the candidate, who vouches for them, and not found in the file. The signed payload carries authenticity_composition, authenticity_grade_counts and bullets_graded — so a recruiter or ATS sees “11 document-backed · 2 candidate-attested”, and can go and read those lines. There is no number to argue about and no number to game.

Candidate attestation. A claim the model can't find in the file isn't silently promoted. Where the candidate personally vouches for it, it's disclosed as attested — the candidate's word, clearly labelled, never passed off as document-backed. The model's only job is to label each line; when it isn't sure, it defaults to unsupported (conservative by design).

Where Verified Prep shows up

The badge is the portable edge of it. The same graded evidence runs through the recruiter product end to end.

Evidence-cited ranking

Candidates are ranked with semantic skill matching, and every match quotes the exact CV line behind it — no unsourced scores.

Weighted requisition skills

Recruiters weight each required skill 1–5; the ranking re-computes live so the shortlist reflects what the role actually needs.

Hiring-manager portal

"Submit shortlist to hiring managers" opens a revocable, anonymised, evidence-cited portal at /client-pack/<token>/ — the client reads the evidence, not the person.

For candidates — add your badge

Show recruiters your prep is honest. Drop it in your portfolio, LinkedIn featured section, or email signature.

  1. On your send-pack page, click “Create my shareable verified link”.
  2. Copy the URL under “Your shareable pack link” — it looks like https://scout.a1ergo.tech/verified-prep/<token>/. Share that page as-is, or take the token from it for the badge snippet below.
  3. Changed your mind? Click “Stop sharing this link” — the page goes offline immediately and the badge stops resolving.

The YOUR_TOKEN below is the UUID from your shareable pack link (the part after /verified-prep/).

<a href="https://jobs.a1ergo.tech/api/v1/verified-prep/YOUR_TOKEN/">
  <img src="https://jobs.a1ergo.tech/api/v1/verified-prep/YOUR_TOKEN/badge.svg"
       alt="A1 Verified" height="20">
</a>

The badge renders inline as an SVG — no scripts, no tracking, CSP-safe. It shows how many of your lines are document-backed and how many are your own word. Stop sharing the pack link and the badge stops resolving too.

For ATS & platform integrators

Render the badge as a trust layer and re-verify it yourself. CORS is open (Access-Control-Allow-Origin: *) and responses are cacheable (max-age=3600).

GET/api/v1/verified-prep/<token>/

Returns the signed JSON-LD badge for an application (application/vnd.a1jobs.verified-prep+json; v=1): pseudonymous aliases, the per-line provenance counts and the prep facts — never PII, never a score. The @context points at the schema below.

POST/api/v1/verified-prep/verify

Re-validate a payload you cached. Re-computes the HMAC and re-checks consent. Returns { valid, verified_at, stale, consent_still_active }.

GET/schema/verified-prep/v1

The JSON-LD @context document — stable, referenced by every payload. View the schema →

Quick start

# Fetch a signed badge
curl https://jobs.a1ergo.tech/api/v1/verified-prep/<token>/

# Re-verify later — checks the signature AND that consent is still live
curl -X POST https://jobs.a1ergo.tech/api/v1/verified-prep/verify \
  -H 'Content-Type: application/json' \
  --data @badge.json

Verifying the signature yourself

Don't want a round-trip? Verify offline:

  1. Take the payload and remove the signature key.
  2. Canonicalise the remainder with JCS (RFC 8785).
  3. Compute HMAC-SHA256(key, canonical_bytes), base64url-encode, and compare (constant-time) to signature.value.
  4. The signature.key_id names the key that signed it — pin verification to it. (v1 publishes a single key; key_id is the hook that keeps old badges verifiable if we rotate keys.)

The privacy gate returns 404 for any token that isn't a live, consented application — it never reveals whether an application exists (no 401/403). Integer probes 404 too; tokens are opaque UUIDs.

Production integrations & API keys

Anonymous access works out of the box for evaluation — it stays consent-gated but is rate-limited per IP. Production integrators authenticate with an API key for higher limits and a stable, accountable identity:

curl https://jobs.a1ergo.tech/api/v1/verified-prep/<token>/ \
  -H 'Authorization: Bearer vp_your_key'

Keys look like vp_… and are also accepted as an X-API-Key header. A key raises your rate limits — it never bypasses candidate consent. A presented key that is invalid or revoked returns 401 rather than silently falling back to anonymous, so misconfigurations surface immediately. The badge SVG stays public for embedding. Request a key at partnerships@a1ergo.tech.

Become a launch integration partner

Render “A1 Verified” in your ATS or job board and give every candidate a portable, tamper-evident honesty signal. We'll help you wire it up.

See it on your own roles

A 20-minute walkthrough: rank a real candidate, open the evidence, share a hiring-manager portal. No slides.

We'll only use this to arrange your demo. No spam.