Get a spot-based quote for your gold and coins

What we buy

If you're not sure whether something qualifies, send it in with the form. A quick look at the photos usually answers it.

Good to know: gold-plated, gold-filled and costume jewelry usually carry little or no precious metal value. Send photos and markings and we'll tell you honestly. Only categories listed above are covered by this page. For anything else, ask us before sending it.

How quotes are determined

We don't publish fixed prices or payout percentages, because anyone who does can't honestly stand behind them. Here is what actually drives your number.

Why a quote is only confirmed after testing: photos and stamps can't show true weight or purity. Some pieces are plated, filled, hollow or mismarked. So your first quote is an estimate from the information you provide, and the final figure is confirmed only once items are weighed and tested. If the verified result differs, we'll explain why before anything moves forward. You're never obligated to accept.

Frequently asked questions

Operator runbook (debug mode only)

0. Send the request to the Board and get their written wording

This page cannot send the request or receive the reply for you. Use the buttons below to copy the text or open it as an email draft, address it to the Board yourself, send it, then tick the box in section 4. When the written reply arrives, paste each answer unchanged into the FACTS object in the script at the bottom of this file.

Copy-ready request (review before sending) Subject: Written wording needed for our website Hello, We are publishing a small "verified details" section on our precious-metals page and want to use your exact wording, unedited. Please reply in writing with the text you approve for each item below: 1. Business name (as it should appear publicly) 2. Vermont location or meeting area 3. Licensing (licenses held, as you confirm them) 4. Payment methods accepted 5. Turnaround after items are received 6. Insured shipping details We will paste your wording unchanged. If an item is not confirmed yet, please say so and we will leave it off the page rather than guess. Thank you, Julien julien@relaycairn.com Copy request Open as email draft

1. Board-confirmed facts status

A fact is shown to visitors only when its value in the FACTS object is non-empty. Paste the Board's exact written wording; do not paraphrase, and do not add price, percentage, "above spot" or speed guarantees. Until the Board's text arrives, leave the field empty. A "REVIEW" flag means the pasted text contains wording (a price, percentage, guarantee or speed claim) that needs a compliance check before it goes live. It is still displayed, because the text must stay unchanged, so decide whether to publish that fact at all.

2. n8n setup for Test B (do this in the workflow, not on this page)

Add an IF node directly after the Webhook node, before any step that stores or forwards the lead:

Condition (String, equals):
  Value 1: {{ $json.body.fs_test_case }}
  Value 2: B

TRUE branch  -> Respond to Webhook
  Respond With: JSON
  Response Code: 500
  Body: {"ok":false}
  Headers: Content-Type: application/json
           Access-Control-Allow-Origin: (same origin as the success node)

FALSE branch -> existing lead flow -> Respond to Webhook (200, {"ok":true})

If your n8n version exposes form fields at the top level instead of under body, use {{ $json.fs_test_case }}. Routing B before the storage step keeps test B out of the CRM. Make sure the workflow is saved and active, and that the form posts to the production /webhook/ URL (a /webhook-test/ URL only works while the editor is listening).

3. Endpoint tests

Label for the next test submission Test A: success branch Test B: failure branch Test C: CORS / non-allowed origin

In debug mode each submission is tagged: the message starts with "[FS-TEST]" and the fields fs_debug=1 and fs_test_case are added, so test leads are easy to find and delete. No conversion event fires. After each submit the diagnostics line prints a PASS/FAIL verdict, and the tracker below records the latest result for A, B and C. Results and ticks are kept for this browser tab session (per origin), so they survive a reload. Test C runs from a different origin, so its result is recorded in that origin's tab.

• NOT RUN – Test A (success)
• NOT RUN – Test B (failure)
• NOT RUN – Test C (CORS)

1. A (success): submit a realistic test lead. Expect HTTP 200, a JSON content type, body {"ok":true}, the confirmation screen, and in DevTools > Network an Access-Control-Allow-Origin header on the response (page scripts cannot read that header, so check it by hand).
2. B (failure): expect a 4xx/5xx status, the error message on the page, and no confirmation screen. If B reports a network/CORS failure instead, the failure response is missing the CORS header.
3. C (CORS): submit from an origin not on the allow list (for example open a saved copy of this page from a file:// path or another host while Allowed Origins is set to the real site only). Expect "Network/CORS failure", the error message, and no confirmation.
4. Delete all [FS-TEST] leads from the CRM afterwards. Search for the exact text "[FS-TEST]" in the message field. Test C in particular may still reach the CRM, because Allowed Origins only controls response headers and does not stop n8n from processing the request.

4. Manual sign-off

Not detectable by the page. Ticks are remembered for this tab session only.

• Request sent to the Board
• n8n IF node added (fs_test_case == B returns 500 {"ok":false} with the CORS header) and workflow saved and active
• Access-Control-Allow-Origin confirmed in DevTools > Network for Test A
• All [FS-TEST] leads deleted from the CRM

Reset tracker and ticks