Developers · Model evaluation

LLM human evaluation with verified people

LLM human evaluation can compare two short model replies or rate one for clarity. This is a small human judgement format, not an RLHF data pipeline. The current developer sandbox returns synthetic answers, so it cannot yet provide live RLHF human feedback.

Last checked

Example pairwise test: Which reply is more useful? A, consider its needs; B, check the soil; 14 of 20 chose B
Pairwise human feedback, the kind used in RLHF, on two model replies. Fictional example.

When LLM human evaluation helps

Once live answering opens, a small human evaluation LLM check could reveal confusing wording, tone problems or a preference between two reply styles before a release decision. Ask which reply is more useful, then read why. That would give a team a concrete issue to inspect, especially when a model score misses the reader’s experience. The example card shows a fictional five-person comparison; it is not a measured product result.

This is a quick judgement format, not a training dataset at scale. It is also a poor fit for harmful outputs, specialist advice or a release gate that needs a representative sample. Do not send sensitive material to members without the agreed controls.

Only quick takes are in scope. A pick-one question can compare two or three options of up to 80 characters each; a longer reply can be uploaded as a screenshot. Pools are 5 to 50 UK adults. The sandbox uses synthetic members and carries no evidence of what real people prefer. Training rights for answers are not settled, so do not treat responses as licensed model-training material.

Comparing model replies in a quick take

Write the prompt without naming the model or signalling which answer you favour. For example: “Which reply is more useful to someone asking how to return this item?” Add two short options, a pool size and an idempotency key. POST /v1/questions returns an ID and cursor; GET /v1/questions/{id} returns the split, reasons and status. For an image, upload PNG, JPEG or WebP first and pass its asset ID. The API reference gives current field names and limits.

Receipts for RLHF human feedback

An answer receipt is a signed ES256 JWS. Its claims bind the question and asset hashes, the answer, status and checks passed, without naming a member. Verify it against the public JWKS for live answers. Synthetic sandbox receipts use a separate key and say so. A valid signature proves the record came from this service; it does not make a five-person sample representative or the judgement correct. See how receipts work.

Example results: A 6, B 14, with reasons such as “B is practical” and “I can act on B”
Human evaluation of LLM replies comes with the reasons behind each pick. Fictional example.

Receipts in the docs

RLHF data limits and pricing

Sandbox requests and synthetic answers are free. During early access, asking is free; paid questions have no start date. The quick-take asker price is planned from 30p an answer plus 50p a question (launch example). Twenty quick takes would cost about £6.50. A sandbox key is available by invitation. There is no separate RLHF human feedback product price, and answer-use rights for model training are unsettled. Check the pricing page for the current launch example.

Man in silver glasses and a denim shirt reviewing charts on a monitor in an open-plan office
RLHF data is only as good as the people behind each answer.

Questions before integrating

What does a human check of model replies measure?
It records how people judge a specific model output or choose between alternatives. A quick take can reveal which short reply feels clearer or more useful, with a reason from each respondent. It does not measure every kind of model quality or predict how all users will respond.
Can I buy RLHF data here?
Not as a large training dataset. The planned live service is for small, quick human judgements with receipts. During early access the developer sandbox uses synthetic answers only. The licence for using future answers in model training has not been settled, so do not assume that right.
How do you stop evaluators using AI?
The member rules forbid AI-written answers, and the planned live checks include a passkey, timing and paste controls, known-answer questions and human review of flagged replies. No service can promise zero AI use. A receipt records checks passed; it is not proof of authorship.
Can evaluators see which model wrote each reply?
The quick comparison should keep model names out of the prompt and options. Members answer blind and do not see earlier answers before they submit. The asker controls the material they upload, so a visible model label in a screenshot could still bias the result.
Can I use answers to train an LLM?
That licence is not settled. Do not use future member responses as model-training data unless the terms explicitly grant that use. The sandbox’s synthetic outputs are for integration tests and provide no human feedback. Contact the team before designing a training pipeline around this service.
How fast are results?
We aim for first live answers within about 15 minutes in UK daytime, but that is an estimate and early access can be slower. The sandbox’s synthetic responses usually arrive within a few minutes. Use a cursor or event stream and allow a decision maker to see when the pool closes.

Get a sandbox key

Use the developer route on the contact page. A real person replies.

Request a sandbox key