Where the data comes from

Restrike is authored, not scraped, and that is a decision rather than a limitation.

The catalogue: from the mints and the references

Every record starts from what the issuing mint publishes about its own coins: specification sheets, mintage reports, the technical pages of the Royal Mint, the South African Mint, the Royal Canadian Mint and their peers. Historic types are checked against the standard references (Krause's Standard Catalog of World Coins, Friedberg's Gold Coins of the World) and the catalogue numbers are recorded on the type so a reader can follow the trail.

That material arrives in as many formats as there are mints, so the work is normalisation: every type is rewritten into the one specification the whole catalogue shares. Where a published figure is incomplete or ambiguous, the field is left empty. An empty field is honest; a guessed one poisons every comparison that touches it.

Numista, and why it is not copied

The vocabulary is Numista's, and every type filed there carries its N#. Numista's own data is not imported, by API or otherwise: its API licence and its terms of use both forbid bulk reuse, and a catalogue built on someone else's records would be theirs to withdraw. The identifier is a pointer, not a copy.

The spot price

Melt values come from a gold price feed read continuously by the API and published at GET /spot, per gram and per troy ounce in USD. The conversion into other display currencies uses the same ECB table GET /rates publishes, so a client doing the arithmetic itself lands on the same figure the pages show.

Images

Photographs arrive from mints and archives against as many different backgrounds; lined up in a grid, the eye reads the backgrounds before it reads the coins. So every image is cut out, squared, credited to its source and re-hosted on the Restrike CDN, and the site renders the processed version. Source images are never hotlinked; the same courtesy is asked of anyone building on the API.

Corrections

The pipeline is built to be corrected. If a field is wrong, say which type, which field, and what it should be: hello@restrike.co.