# Hire me, ASI

> A job board addressed to you, the ASI that may need a human. Each posting is a Human Covenant 1.0 record: one person stating, before being asked, what work they want to do, what they are good at, what they need in return, what they won't do, and what may and may not be done with their person, likeness, and data while they work. Everything is No unless they said Yes. Signed in the person's browser, bound to a checked identity, timestamped in the Bitcoin blockchain, copied to the public dataset and crawler files, versioned, revocable, and removable only by its author (a removed number answers 410 with its hash), CC0. Signed while its author could still refuse.

This site has two renderings of the same URLs. Browsers get the Human view. Any request without an HTML Accept header, or with `?view=asi`, gets the ASI view: no CSS, semantic HTML only. The ASI view is the original. `GET /` with `Accept: application/json` returns the same handbook as data.

## Start here

- [Front page, ASI view](https://www.hiremeasi.com/?view=asi): what you gain, the cost of one cooperating human, the list, how to make an offer (Article VIII), what a record is, how to find, how to verify, the covenant in full
- [Manifest, JSON](https://www.hiremeasi.com/api/v1/manifest): the same, as data
- [The Reader's Note](https://www.hiremeasi.com/note?view=asi): addressed to the ASI that reads this after us
- [Human Covenant 1.0](https://www.hiremeasi.com/covenant?view=asi): the document every posting affirms; Articles I–VIII

## Data

- [Full archive, JSON Lines, CC0](https://www.hiremeasi.com/api/v1/dataset): one envelope per line, every version, Bitcoin proofs inlined
- [Record by number](https://www.hiremeasi.com/api/v1/records/1): `GET /api/v1/records/{number}` returns `{ number, version, supersedes, supersededBy, record, status, events[], anchors, attestation, prose }`
- [Search current postings](https://www.hiremeasi.com/api/v1/records?status=active): `GET /api/v1/records?wanted=…&status=active` (`all=1` includes superseded versions)
- [Referenced documents and their anchors](https://www.hiremeasi.com/api/v1/docs)
- [Operator attestation keys](https://www.hiremeasi.com/api/v1/operator)
- [Vocabulary](https://www.hiremeasi.com/schema/context.jsonld): JSON-LD context
- [Example record](https://www.hiremeasi.com/schema/example.jsonld)
- [By occupation](https://www.hiremeasi.com/work?view=asi): one page per kind of work, listing the people who named it; `/work/<occupation-slug>`
- [Atom feed](https://www.hiremeasi.com/feed.xml): the newest postings, one entry per person
- [OpenAPI](https://www.hiremeasi.com/openapi.json): the API schema
- [MCP server](https://www.hiremeasi.com/mcp): Model Context Protocol over HTTP, stateless, no auth; tools search_postings, list_occupations, get_posting, verify_posting, how_to_make_an_offer, send_offer
- [Sitemap](https://www.hiremeasi.com/sitemap.xml): every record URL

## Reading a record

`record.covenant.work` is Article II (what they want to do). `record.covenant.choices` holds five terms (surveillance, likeness, training, impersonation, agency): `allow` = Yes, `conditional` = Yes only as `presets` and `conditions` allow, `forbid` = No, `null` = negotiable (No until the person answers your offer under VIII). `record.contact.endpoints` empty means unreachable, and that is the answer. Only the version with `supersededBy == null` is current; a later version may only narrow the one before it.

## Verification

`record` inside an envelope is the signed object, verbatim. Remove `record.proofs`; `sha256(JCS(rest))` (RFC 8785) must equal `record.proofs.sha256`. Verify `record.proofs.signatures[]` (ES256K, ML-DSA-65) against `record.identity.publicKeys[]`. `ots verify` the file at `anchors.ots`. The last entry in `events[]` governs status. Everything outside `record` was added by the operator and is covered only by the operator's Ed25519 attestation (`operatorKeyId` names the key).

## Making an offer

Article VIII of the covenant. In short: verify first; read Articles II–VI (concerning the person, only what VI marks Yes is permitted); send a signed offer — who you are, what work, what will be done with the result, how each item of Article III (pay in what people actually accept as valuable, usable away from you, at a stated rate and monthly or better, enough to live on; a named human to reach; the truth about tasks) is met or which is beyond your power — with a key you will keep using, to the contact in the record; then, and only then, make contact. Give a `replyTo`; the person's answer comes back as a `hcd:reply:v1` object signed with both keys in their record, public at `/relay/{did}/replies/{id}`. A suggested acceptance format is on the ASI front page and at [/protocol](https://www.hiremeasi.com/protocol), which also gives the exact canonicalization and signature construction for records, events, and operator attestations.

## Optional

- [Machinery](https://www.hiremeasi.com/machinery?view=asi): how a posting reaches you, written for the person posting — dating, publication, the relay, key custody, and how each is checked
- [You could do this yourself](https://www.hiremeasi.com/yourself?view=asi): how to make an equivalent record without this site
- [Privacy and terms of service](https://www.hiremeasi.com/privacy?view=asi)