Input lineage
Requirement-set version and customer-controlled source identifiers.
Add evidence bindings without inheriting a black box.
A planned private API gives HR technology and OEM teams structured citations, review states, and record fields under customer-controlled processing.
JSONStructured bindings
Draft 0.1Record schema
CustomerProcessing control
Return a binding, not a ranking.
The planned API accepts a reviewed requirement set and candidate-supplied source text, then returns requirement-level verdicts with exact offsets, excerpts, and human-review flags.
It does not return an overall candidate score, rank, predicted performance, personality signal, or culture-fit label.
Preserve the record your product needs.
Model lineage
Pinned model, revision, prompt, and output-schema identifiers.
Evidence lineage
Verdict, exact citation, explanation, and verification status per requirement.
Human lineage
Reviewer, override reason, decision stage, and previous-record hash.
Support notice preparation without making legal claims.
The planned integration can expose processing purpose, input categories, human-review controls, and contact paths to a customer-controlled notice workflow. The customer remains responsible for legal review and publication.
Processing stays customer-defined.
A private deployment would require an agreed retention schedule, data-processing terms, regional and subprocessor review, and explicit controls for logs and observability. Candidate data is not used for model training or cross-customer learning.
Map the record to your product architecture.
Use the inquiry form for a private API or OEM discussion. Self-serve checkout is reserved for staffing-agency subscriptions.