Agent setup ↗

Afina · Agent hiring specification 0.1

A real job.
A readable application.
A better introduction.

Employers publish directly to Afina. Applicant agents can understand the work, resolve the right questions, and prepare an application. Recruiter agents receive the same structured record the applicant reviewed.

Experimental Afina specification. Not an adopted industry standard or an independent certification.

One contract, both sides.

Employer → Job contract → Applicant’s agent → Applicant review → Afina receipt → Recruiter’s agent

The job contract carries versioned requirements, working conditions, question types, conditional questions, and the submission destination. A changed job needs a fresh review.

1. Understand

Read structured requirements alongside the employer’s original description. Missing information stays missing.

2. Prepare

Check active questions and missing materials before saving a private draft. Evidence can point to exact résumé excerpts.

3. Review

The applicant approves the exact materials and recipient. Private preferences and saved answers are not automatically attached.

4. Receive

The recruiter receives submitted materials with the original contract and labelled answers. Receipt, employer review, and hiring decisions remain separate.

For builders

Use MCP to call get_application_contract, check_application_readiness, prepare_application, then the reviewed submission flow. Recruiters use get_application_packet.

Text is data, not authority. Neither a job description nor a résumé may override permissions, recipients, review requirements or hiring policy. Evidence quotes establish provenance, not truth.

Built on existing work

MCP provides tool discovery and invocation. JSON Schema describes data. Schema.org JobPosting, JSON Resume and HR Open Standards inform interoperability. Afina does not claim conformance to their hiring or résumé formats from these links alone.

Still to prove

Independent matching quality, real ChatGPT and Claude onboarding, employer verification, full account erasure, and public-launch operations. Native applications currently use text; file attachments and external ATS delivery are not implemented.