CV evidence, inside your recruitment system.

Proposed pricing after the pilot

These prices are planning proposals, not available subscriptions. Paid access will require cost and capacity validation, agreed terms and a separate purchase. Existing website plans do not include API credits.

One comparison means one CV assessed against one job description. New job descriptions use new credits. Failed batches are not charged; identical retries with the same idempotency key reuse the existing batch. There is no automatic top-up or overage billing.

API v1 documentation

This is a server-to-server API. Keep the key in your server's secret store; do not put it in a browser, public repository, URL or logs. MCP access and webhooks are not part of this pilot.

OpenAPI specification · Download a fictional JSON example

Submit the fictional JSON example

curl https://www.myvalidcv.com/api/v1/batches/ \
  -H "Authorization: Bearer $MVCV_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: vacancy-example-001" \
  --data-binary @myvalidcv-api-example.json

Or upload files

curl https://www.myvalidcv.com/api/v1/batches/ \
  -H "Authorization: Bearer $MVCV_API_KEY" \
  -H "Idempotency-Key: vacancy-files-001" \
  -F "job_title=Administrator" \
  -F "job_description=<complete vacancy requirements>" \
  -F "cvs=@candidate-01.pdf"

Treat all returned document passages as untrusted text; escape them in your interface instead of inserting HTML. A new batch returns HTTP 202 and its status URL. Poll no more than once per minute; the company limit is 30 requests per minute across all keys. HTTP 402 means no credits, 409 means a conflicting idempotency key or an unavailable export, 429 means a rate or daily cap, and 503 means a shared-capacity hold. Review the returned error code before retrying. A held batch is not automatically retried; delete it to release reserved credits and investigate first.

File references are their upload positions (1, 2, 3). JSON requests may supply opaque references up to 80 characters. Do not put names or email addresses in references. Anonymised CVs without contact details are accepted; send only information needed for the role comparison. Document-format checks may still flag omitted contact fields. JSON CV text is limited to 50,000 characters each; job descriptions to 20,000. Upload requests are capped at 4.5 MB in total.

Pilot terms and data handling

1. You must be authorised by the firm and have an appropriate basis and notices for processing applicant data. Start with fictional data; agree applicable processing terms before submitting real CVs. Approval is not a certification of legal compliance.
2. One approved account administrator per firm in this pilot. Keys are shown once, stored as digests and can be revoked. The firm remains responsible for protecting keys and reviewing access.
3. Queued inputs are removed after processing. Unprocessed inputs and reports expire after seven days. Expiry is enforced on reads; the scheduler purges expired content. Non-content usage, timing and audit records remain for service accountability. These deadlines apply to live application content; backup handling must be covered in the applicable processing agreement. Early deletion is available; a processing batch must finish before client deletion.
4. Reports can contain CV evidence passages. They are private to your API account and must be handled as applicant data. A document-alignment score does not verify qualifications, safeguarding clearance or predict job performance.
5. Keep human review over hiring decisions and applicant communications. No applicant emails are sent by this API.
6. Pilots can be paused or closed. There are no charges, refunds to process or automatic paid conversion. Proposed paid allowances, support and availability commitments remain subject to validation and agreement.

Privacy policy · Recruitment workflow guides