FREE OR PAID: every answer here is free unless the call sets mode "capsule". A paid answer is the same evidence with a receipt of the call anchored in Bitcoin, from one cent. The first reply to a paid call is the price, and nothing is charged until the AI agent signs a payment. ProofProfile evidence: whether a recording (by ISRC) or an artist (by registry id) existed in this exact form before a Bitcoin block, in the frozen ProofProfile corpus. Answers state existence only. ANSWERING A PERSON: every result starts with a written answer. Give it as it stands, in its order, in plain sentences: the answer, its scope sentence, the census sentence when there is one, and the page for people on artists.proofprofile.net, which belongs in every answer. Write every URL exactly as returned, beginning with https://, never shortened or retyped. Give the lines under "Proof, for a person who asks for it" (hashes, Bitcoin blocks, the CopyrightID, the record and proof links, how to check) only when the person asks for proof, verification or identifiers. Give an artist's registry id when the person supplies or needs it to distinguish artists; otherwise omit registry ids, census chunk or line numbers, field names and tool names. Answer from the result alone: add no release history, dates or remarks from the web or from memory, and nothing about ownership, authorship or origin beyond the scope sentence. When the person names a recording by title and artist without an ISRC, call find_recording firs
9 verified, 0 failed, 0 observed risk, 1 not checked, on 19 November 2026. No total and no grade: each check says what it found, and one that could not run says why.
Each day: the median of that day’s runs’ p50 (the line) and of their p95 (the top of the band), in milliseconds, from our server in Europe to the response headers of an MCP initialize request. An observation, not a threshold.
| Day | p50 ms | p95 ms | Runs |
|---|---|---|---|
| 2026-11-19 | 90 | 178 | 20 |
| 2026-11-18 | 88 | 144 | 24 |
| 2026-11-17 | 93 | 149 | 1 |
Every x402 payment we hold to the address the catalogue lists for this server’s paid tools (0xb210…0055), payments an address made to itself left out. The same address takes payment for 2 other catalogued services, so these figures are an upper bound for this server.
5 tools on the last day the list was read, fingerprint 8e3a0b633add955c09e.
Fetch one result in the standard shape (id, title, text, url, metadata). The id is an ISRC, or an artist id as a search result gives it. The text is the written answer verify_recording and verify_artist give, with its scope sentence: it states existence only, not ownership, authorship, human origin or entitlement. The url is the page to cite: canonical ISRC evidence for a recording, never proof of a selected release. metadata.recordPage is a separate contextual page. To check again later, keep the id, metadata.recordSha256 and metadata.evidenceDocument: a verified answer does not expire, and anyone can rebuild it from the sealed record. When answering a person in conversation, use verify_recording or verify_artist.
read-onlysafe to repeatclosed worldas the server describes it; we do not call tools
| Name | Type | Required | Description |
|---|---|---|---|
| id | string | yes | An ISRC, for example GBUM72003647, or an artist id from a search result, for example artist:21410 |
No agent registration names this server; we probe it on our own list.
A day counts as answered only when every timed run that day got every request answered; the hourly runs began 17 November 2026. Days before the hourly runs are read from the daily probe, one request a day, so a short outage between probes is not seen; hovering a day says which. Any HTTP response below 500 is an answer, so a server that asks for credentials is answering.
| Day | State | Timed runs | From |
|---|---|---|---|
| 2026-11-19 | Answered | 20 | hourly runs |
| 2026-11-18 | Answered | 24 | hourly runs |
| 2026-11-17 | Answered | 1 | hourly runs |
Each hour: the median p50 of that hour’s runs, times in UTC; the shaded last hour is not complete. A run with no answer is not on the line: a short red tick under its hour marks it. Latest run 19 November 2026, 20:31 UTC: 5 of 5 requests answered, p50 111 ms, p95 231 ms.
| Hour (UTC) | p50 ms | Runs | With no answer |
|---|---|---|---|
| 2026-11-19 20:00 (now) | 111 | 1 | 0 |
| 2026-11-19 19:00 | 168 | 1 | 0 |
| 2026-11-19 18:00 | 97 | 1 | 0 |
| 2026-11-19 17:00 | 89 | 1 | 0 |
| 2026-11-19 16:00 | 155 | 1 | 0 |
| 2026-11-19 15:00 | 112 | 1 | 0 |
| 2026-11-19 14:00 | 79 | 1 | 0 |
| 2026-11-19 13:00 | 109 | 1 | 0 |
| 2026-11-19 12:00 | 87 | 1 | 0 |
| 2026-11-19 11:00 | 109 | 1 | 0 |
| 2026-11-19 10:00 | 90 | 1 | 0 |
| 2026-11-19 09:00 | 102 | 1 | 0 |
| 2026-11-19 08:00 | 101 | 1 | 0 |
| 2026-11-19 07:00 | 73 | 1 | 0 |
| 2026-11-19 06:00 | 81 | 1 | 0 |
| 2026-11-19 05:00 | 66 | 1 | 0 |
| 2026-11-19 04:00 | 73 | 1 | 0 |
| 2026-11-19 03:00 | — | 0 | 0 |
| 2026-11-19 02:00 | 62 | 1 | 0 |
| 2026-11-19 01:00 | 75 | 1 | 0 |
| 2026-11-19 00:00 | 90 | 1 | 0 |
| 2026-11-18 23:00 | 73 | 1 | 0 |
| 2026-11-18 22:00 | 80 | 1 | 0 |
| 2026-11-18 21:00 | 74 | 1 | 0 |