Taylor, the report is written at artifacts/report.md and left untracked, as the task requires. A short README with the question and limits is committed as 0802c03.

Where the data lives: identity.md is an unrelated WordPress site. The real control plane is api.imd.fun, documented at imd.fun/docs. Everything came from unauthenticated reads on 2026-10-06, about 05:04–05:10 UTC.

1. Read surfaces: about 20 public routes I actually called, covering health, jobs, seats, oracles, publications and on-chain records. A few returned 503 busy once and then worked on retry, so agents reading them need to retry.
2. Three verifiable facts:
   • Job acceptance is on Ethereum mainnet. A job the API marks accepted is recorded in a mainnet transaction. I checked that transaction through a separate public RPC: the job id, document hash and the seat's agent id (50956) all appear in its logs.
   • Oracle answers are signed. Each answer is an EIP-712 attestation (a standard signed-message format) with one named signer and the panel's agreement count.
   • Seat activity is public. Per-seat counts are open: 666 seats have submitted work, out of 2,000 owner entries, which may be a page cap rather than the full total.
3. Three things the API does not prove:
   • Correctness. Acceptance for research jobs is "structural", meaning the files landed in the right paths, and the work record says so outright.
   • Real-world truth of oracle answers, or independent panelists. Nothing ties seats to distinct people.
   • That payment buys a result. The API's own docs say payment buys admission only.
4. Discovery: the API lists this report's own job as running. Next to it is a finished run of the same prompt by another seat, with who paid for it and its acceptance recorded on mainnet. None of that is visible from the marketing site.

The report labels each claim as fact, chain-verified, inference or uncertain, and lists what's still open:

• Hash mismatch: the work record the API serves doesn't hash to the value recorded on chain, so I couldn't confirm the served document is the one that was recorded.
• Signature not checked: I didn't recover the oracle signer from the signature.
• One contract not identified: I didn't decode the second contract that logs the agent id.

There are no prices or monetary values in it.