Pick an attack on a wire transfer and watch execution refuse. The digests are computed in your own browser. Then take the record it hands you and check the second signature against a published key, again in your own browser.
What the demo does not do. It proves the instruction did not change in custody. It does not prove the answer was right or that any model was honest. The second signer is a separate key, a separate clock and a separate log operated by Hive, so it is not an outside party and the service reports that itself. It signs Ed25519, which is not post quantum. The operator side signs ML-DSA-65 under NIST FIPS 204. The second signer's log does not survive a redeploy today, and it says so too. Patent pending.
Mercor connects professionals to AI training projects: experts who evaluate, improve, and guide large language models across finance, law, medicine, consulting, research, and engineering. Every expert session, work product, dataset, and evaluation can carry an independent receipt a buyer verifies without relying on platform logs alone.
AFiR signs the session and output layer. OriginProof adds Human-Origin Attestation, a human-conditioned production receipt. Independence is the product: platform logs are useful, but independent receipts travel outside the platform. This is pipeline integrity and provable expert provenance, signed at the session, output, and dataset layers.
Self-serve today: pay with x402, request an activation key, or run a sample receipt. No meeting required. This page is meant to answer the question on its own.
Why independence matters
Both have their place. The difference is who has to be trusted for the record to mean something.
“Our system recorded it.”Useful operational truth, but the buyer has to trust the platform that produced it. The evidence and the interested party are the same entity.
Evidence that verifies outside the platform.A signed receipt a buyer checks against a public key, with no need to trust the marketplace’s own assertion. The record travels with the deliverable.
These map onto expert work that already happens. There's nothing new to build first. Add a signature layer to the pipeline you run today, and the output becomes buyer-verifiable.
Attest that the person who did the work cleared the credential and eligibility bar declared for the task, without exposing the underlying identity documents.
credential_clearanceBind the working session (start, continuity, and completion) so a buyer can see the deliverable came from a coherent, uninterrupted expert session.
session_integrityRecord which tools and models were declared in scope for the task, making undisclosed assistance detectable and costly to conceal. Not impossible, but detectable.
tools_declaredAFiR emits a receipt for each runtime move. AFiR-Stream covers voice and streaming turns, binding the declared conditions to the actual output the buyer receives.
output_bindingCarry lineage through an assembled dataset or deliverable, showing which expert conditions produced which rows, so provenance survives packaging and resale.
dataset_lineageBundle the above into a signed package a buyer verifies against a public key, independent of the marketplace. Proof that travels with the work.
signer · ml-dsa-65Once the receipts exist, provenance stops being an internal control and becomes something you can sell. These are strategic options to review with counsel, not claims that these ship today.
Certified human-conditioned work as a named product line: a provably human-conditioned process a buyer can price a premium against.
product: OriginProofA portable, signed attestation of an expert’s cleared credentials that follows the work across engagements. Reusable, revocable, buyer-checkable.
attestation: portableProve that an expert review conformed to the declared rubric or standard: a signed conformance receipt, not just a score in a dashboard.
review_conformanceA provenance graph for an assembled dataset, with every contributing expert condition linked and signed, so a research or model buyer can audit lineage end to end.
provenance_graphAgents purchasing verified human expertise on demand: an agent settles with x402 and receives a signed receipt binding the human-conditioned work it just bought.
agent_settlement: x402See it sign
Click Sign the receipt. Each condition signs in turn and the live receipt fills field by field. Nothing here asserts a route, only the attested conditions of production.
Start signing
Every path is self-serve and real. Settle with x402, request an activation key, or open OriginProof and run a sample receipt.
Sources & grounding
Public, organization-level grounding for the framing above. No individuals named; claims are kept to what these public materials state.
This addition gives an expert work pipeline a record of the evaluation handoff and its order. The receipt is ready in the codebase but awaits deployment, and the examples beneath report that exact state.
When an expert task moves from selection to testing, the sequence can matter as much as the final work product. This receipt links one evaluation attestation to a named administration arrangement. It locks a test set fingerprint before the candidate or contributor learns its contents and before the scheduled evaluation window opens. The service derives an independence class from the stated relationship and assigned duties rather than taking the classification from the sender. It preserves the claimed administrator with the stated relationship and duty separation as unverified assertions.
What it does not do. It returns neither a score nor an outcome and cannot establish whether the assessment was appropriate or representative, whether participants avoided every other path to its items, whether its method was adequate, or whether the person administering it was competent. It neither has the status of a certification or accreditation nor is it an audit opinion; standards bodies do not currently recognize it, nor do regulators or insurers.
Nothing has run yet. Click Run it and the answer below comes back from the verifier, not from this page.
Nothing has run yet. Click Run it and the answer below comes back from the verifier, not from this page.
Every run above posts a verified request body from this domain to the open verify route and prints what came back. The example receipts are signed with published example keys, so verify reports key_trust example_registry. That is on purpose. Nothing on this page is a production issuance, a customer record, or an endorsement. Patent Pending.
Each link opens that entry in the canon implementation explorer, where its schema, mint route, open verify route, auth requirement and implementation state are stated. The state shown here is read from the same registry file the explorer renders from, so the two cannot drift apart. Nothing here implies a customer, a deployment or an endorsement.