Trust the receipt. Filter the slop.
Inbound applications carry verifiable authorship signals. Reframed Verify reads them, scores them, and writes the result back into your ATS. The trust layer between applicants and your inbox.
Your inbox got 5x in the last 12 months. Most of it isn't real.
Generative tools made it free to fire 200 applications in an hour. Recruiters drown. ATS scoring catches keyword stuffing but not voice-flat slop. The signal-to-noise problem is structural.
Reframed Verify gives you signal that doesn't exist anywhere else: a verifiable claim from the candidate that they wrote what they sent. Receipts are issued at generation time, signed with ed25519, and verified against a public key. Tamper-evident. Cannot be faked.
Every applicant pretending to use tools is making the next applicant's resume look generated. Reframed flips the script.
Verifiable authorship is the new credential. The receipt doesn't say “a model helped.” It says how much is yours, signed and timestamped, before you hit send. That's the thing recruiters are missing. Not another slop filter. Proof.
No funded round. No enterprise customers yet. Built by ICs who got tired of the slop wave and thought the honest path deserved better tooling. Reach out if you want to shape the early product.
Three tiers. All start with a real conversation.
For independent recruiters and small teams triaging in email or spreadsheets.
- ·1,000 receipt lookups / month
- ·Batch dashboard — paste a list, get a sorted report
- ·Chrome extension overlay (works on any ATS)
- ·API key for scripts and integrations
- ·Slop detection on resumes without receipts
- ·Public verify URL for every receipt — share with clients
Verification baked into your ATS. OAuth integrations to Ashby, Lever, and Greenhouse are in active partnership conversations. Join the waitlist for early-access pricing and pilot priority.
- ·Planned: unlimited receipt lookups
- ·Planned: native OAuth integration with Ashby, Lever, Greenhouse
- ·Planned: auto-tag every inbound application with receipt status
- ·Planned: 3 team seats + MCP server for recruiter-side agents
- ·Planned: custom slop-detection thresholds per role
- ·Waitlist members get pilot priority and locked-in launch pricing
For talent orgs at scale, agencies, and groups with compliance requirements.
- ·Unlimited everything
- ·SSO / SAML, SCIM
- ·SLA + dedicated support
- ·White-label receipts (your domain on verify URLs)
- ·Multi-ATS: Workday, iCIMS, Bullhorn, SmartRecruiters
- ·100K+ lookups/month + custom integrations
- ·Audit logs + data residency options
Native integrations. Zero scrape.
We register OAuth apps in your ATS so verification happens server-side. No browser extensions you have to install on every recruiter's laptop, no scraping that breaks when the ATS ships a UI change.
| Platform | Status | Pattern |
|---|---|---|
| Ashby | Roadmap | Partnership program — application in progress |
| Lever | Roadmap | OAuth + signed webhooks (design phase) |
| Greenhouse | Roadmap | Harvest API + MCP bridge (design phase) |
| Workable | Roadmap | OAuth, event-driven webhooks |
| SmartRecruiters | Roadmap | Marketplace partner OAuth |
| Workday | Roadmap | Innovation Partner Program |
| iCIMS | Roadmap | Marketplace integration |
| Bullhorn | Roadmap | REST API + agency tier |
Don't see your ATS? Talk to us — partner-program approval typically takes 4-8 weeks; we sequence based on customer demand.
Verification, exposed to your agent.
Your team uses Claude Code, Cursor, custom agents to triage hundreds of inbounds. Thereframed-recruiter-mcppackage gives any LLM-driven workflow native verification tools.
Position: verification data for your agent, not a screening filter. Your process consumes the score; you decide what advances. Avoids the automated adverse-action minefield.
Four properties. Architecturally enforced.
Issued server-side at generation time
Candidates can't mint their own receipts. Only Reframed's API keys can sign one. The signature uses the document's SHA-256 content hash as the signing input — change one character, the hash breaks.
Public verification, no Reframed account needed
Receipts are verifiable against our public key endpoint at /.well-known/honesty-receipt-keys.json. Anyone — recruiter, ATS, third-party tool — can confirm a signature without calling our API. Receipts work even if Reframed goes down.
Append-only, immutable receipt IDs
Once issued, a receipt cannot be silently revoked. Revocation is logged and queryable. A recruiter checking a six-month-old receipt sees revoked: true with reason — not a 404.
Recruiter-side cannot issue receipts
Receipt issuance requires the resume owner's authenticated session. Recruiter API keys are scoped to verification only. Even with a stolen key, you cannot mint a fake receipt for a candidate.
What recruiters ask before signing.
Can I issue receipts on behalf of candidates?
No. Receipts are signed at generation time using the candidate's email account. The hash is bound to the resume content. Recruiters cannot mint receipts — only verify them. This is the load-bearing trust property: a receipt is the candidate's claim, not yours.
What does 'slop detection' actually catch?
Resumes that read as generated even if no receipt is present. Looks at voice flatness, generic phrasing density, suspicious structural patterns, and consistency markers. Returns a score 0-100 with a confidence band. Independent signal from receipt presence.
How will the ATS write-back work?
Designed pattern: we register an OAuth app in your ATS, you authorize, we subscribe to the inbound-application webhook. On every new application, we verify the receipt (if present) and write reframed_receipt_verified: true/false plus authorship_score: 0-100 to a custom field on the candidate record. Your ATS stays the source of truth; we enrich it. Status: partnership conversations underway, Q3 2026 target. Join the waitlist for pilot priority.
Is this legal for screening?
Receipt verification is a signal, not a filter. We position Verify as enrichment data your existing process consumes — same as any background-check or skills-test integration. Full automated adverse action is on you to handle compliantly per your jurisdiction. We surface the data; you decide what to do with it.
What happens if a candidate edits their resume after the receipt is issued?
The receipt remains valid but the document hash no longer matches. Your verification report shows tampered: true with the original signed timestamp. Useful signal — you know the candidate edited post-verification, even if the receipt itself wasn't forged.
Do candidates know we're checking?
The verify URL is public — anyone with the receipt URL can check it. Candidates expect verification when they include the receipt; that's the point. We don't notify candidates when a recruiter checks. Verification is silent.
What about candidates who don't use Reframed?
Slop detection runs on any resume, receipt or not. You get a score on every inbound. The receipt is a positive signal when present; absence isn't a negative signal in itself. The combination is what matters: high slop score + no receipt = high confidence the resume is generated.
How does this differ from existing AI-detection tools?
Existing detectors are reactive — they try to detect generated text after the fact, with poor accuracy and high false positives. Reframed is proactive: receipts prove authorship at generation time. Slop detection is the secondary fallback for resumes without receipts. Together: better signal, lower false-positive rate.
Can I get a demo or a sandbox?
Yes. Verify Pro is live today — receipt lookup dashboard, batch verification, public verify URLs. See /verify/example for what a real receipt looks like. For Verify ATS, join the waitlist; pilot slots open when each ATS integration ships, prioritized by waitlist signup order.
Verify Pro today. Verify ATS when it ships.
Verify Pro is live — receipt verification, batch lookup, dashboard. Join the Verify ATS waitlist to get pilot priority and locked-in launch pricing when OAuth integrations go live.