oanor
Iscriviti gratis
Mercata Prezzi Caratteristiche Accedi

API · /goldpurity-api

Gold Purity API

salutare 3,617 Abbonati

Gold purity and karat maths as an API, computed locally and deterministically — the karat, fineness and alloy numbers a jeweller, goldsmith, assayer or refiner works to. The karat-to-fineness endpoint converts between the two purity systems: karat is the number of 24ths of a piece that is pure gold, so the fineness (parts per thousand, the figure on a hallmark stamp) = karat ÷ 24 × 1000 and the gold percentage = karat ÷ 24 × 100 — 24K is pure (1000‰), 18K is 750‰ (75 %), 14K is 583‰, 9K is 375‰. The pure-gold-weight endpoint gives the actual fine gold in a piece = its total weight × the gold fraction (karat ÷ 24): a 10 g 18K ring holds 7.5 g of gold and 2.5 g of alloy, the fine-gold content a refiner pays on and the basis of the intrinsic metal value. The alloy-mix endpoint inverts it for the bench: to bring refined fine gold down to a target karat, the total weight = the fine gold ÷ (target karat ÷ 24) and the alloy to add = the total − the fine gold, so 7.5 g of pure gold makes 10 g of 18K with 2.5 g of master alloy. Everything is computed locally and deterministically, so it is instant and private. Ideal for jewellery and goldsmithing tools, pawn and scrap-gold apps, and assay and metal-value calculators. Pure local computation — no key, no third-party service, instant. Purity maths only — it does not fetch the live gold price. 3 compute endpoints. For a metal part's weight from its dimensions use a metal-weight API.

#gold #jewellery #karat #assay #precious-metals #developer-tools
api.oanor.com/goldpurity-api
Ottieni una chiave API Prova nel parco giochi → Contatta provider

Specifica leggibile dalle macchine, così gli agenti AI possono integrare questa API.

/api/goldpurity-api/openapi.json
/api/goldpurity-api/llms.txt

Individuazione: GET /api/index.json elenca ogni API.

API salute

salutare
Tempo di attività
100.00%
Sondaggi del server · 24 ore su 24
Latenza media
83 ms
Sondaggi del server · 24 ore su 24
Abbonati
3,617
attiva
Chiamate totali
4
ultimi 7 giorni
status Pagina di stato completa → · 8 sonde/24h

Prezzi

Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.

Free

Gratis

  • 6,800 chiamate/mese
  • 2 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 6.800 Aufrufe/Monat
  • 2 req/sec
  • Karat, Feingehalt, reines Gold, Legierungsmischung
  • Keine Kreditkarte
Accedi per abbonarti

Starter

€7.40 /mese

  • 60,000 chiamate/mese
  • 6 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 60.000 Aufrufe/Monat
  • 6 req/sec
  • Hallmark & bench batching
  • E-Mail-Support
Accedi per abbonarti

Pro

€24.60 /mese

  • 248,000 chiamate/mese
  • 15 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 248.000 Aufrufe/Monat
  • 15 req/sec
  • Pfand-, Schrott- und Analyse-Pipelines
  • Priority-Support
Accedi per abbonarti

Mega

€76.00 /mese

  • 1,150,000 chiamate/mese
  • 40 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 1.150.000 Aufrufe/Monat
  • 40 req/sec
  • Plattform- und Katalogskalierung
  • Dedizierte SLA
Accedi per abbonarti

Costruito da

P
PremiumApi

Correlato APIs

Altro APIs con tag sovrapposti.

Gemstone Weight API

Gemstone weight maths as an API, computed locally and deterministically — the carat, gram, point and measured-weight numbers a jeweller, gem dealer, appraiser or lapidary works to. The carat-to-grams endpoint converts a carat weight to grams, milligrams and points: the metric carat is exactly 0.2 g (200 mg) and is split into 100 points, so a 1.5 ct stone is 0.3 g and 150 points and a quarter-carat is a twenty-five pointer — the carat is a mass unit, not a size, so a 1 ct diamond and a 1 ct emerald weigh the same but look different because their densities differ. The grams-to-carat endpoint inverts it (divide grams by 0.2, or multiply by 5), for a weight taken on a gram balance. The round-brilliant-weight endpoint gives the trade estimate used when a stone is set and cannot be put on a scale: carat ≈ diameter² × depth × 0.0061, with the girdle diameter and total depth in millimetres — a 6.5 mm round about 4 mm deep estimates near 1 carat, which is exactly why a 1 ct round brilliant measures roughly 6.5 mm across; the factor can be nudged for a thick girdle or a different cut. Everything is computed locally and deterministically, so it is instant and private. Ideal for jewellery and appraisal tools, gem-dealer and auction apps, and lapidary calculators. Pure local computation — no key, no third-party service, instant. Weight maths only — it does not price the stone or grade the colour and clarity. 3 compute endpoints. For gold karat and fineness use a gold-purity API.

api.oanor.com/gemstone-api

Reddit API

Echtzeit-Reddit-Daten als API — Subreddits, Beiträge, Kommentare, Benutzerprofile und Suche, zurückgegeben als sauberes JSON. Rufen Sie die Informationen eines Subreddits sowie dessen heiße, neue, Top- oder aufsteigende Beiträge ab; rufen Sie einen Beitrag zusammen mit seinem vollständigen Kommentarbaum ab; schlagen Sie das Profil, Karma, Einreichungen und Kommentare eines beliebigen Benutzers nach; durchsuchen Sie Beiträge in ganz Reddit oder innerhalb eines Subreddits; und listen Sie die trendenden Beiträge und die beliebtesten Subreddits auf. Live-Daten, paginiert mit Reddit-Cursorn, mit Bewertungen, Upvote-Verhältnissen, Kommentarzahlen, Flairs, Zeitstempeln, Thumbnails und Medien-URLs. Ideal für Social Listening und Markenüberwachung, Trend- und Sentiment-Dashboards, Content-Aggregation, Forschung und Marktinformationen sowie Bots. 11 Datenendpunkte. Authentifiziert mit einem x-oanor-Key; faire Nutzungslimits pro Plan.

api.oanor.com/reddit-api

Handrail & Baluster API

Railing and baluster layout maths as an API, computed locally and deterministically — the baluster-count, spacing and post numbers a deck builder, fabricator or balustrade designer sets a guardrail out with. The baluster-count endpoint gives the smallest number of balusters that keeps every gap within the safety limit: between two posts n balusters leave n+1 gaps, so the count = ceil((rail length − max gap) ÷ (baluster width + max gap)). The usual guardrail limit is a 100 mm (4-inch) sphere — a child-safety rule — so a 2000 mm rail with 40 mm balusters needs 14 of them at even 96 mm gaps; round up, because one fewer opens the gaps past the limit. The layout endpoint sets out a known count evenly: the gap = (rail length − total baluster width) ÷ (count + 1), the centre-to-centre pitch = baluster width + gap, and the first baluster's centre sits one gap plus half a baluster from the post face, so you mark the first centre and step off the pitch with the last gap landing equal to the first. The post-count endpoint sizes the frame: a run needs one more post than spans, spans = ceil(run ÷ max post spacing), posts = spans + 1, even spacing = run ÷ spans — a 6 m run at a 1.8 m max takes 4 spans and 5 posts at a tidy 1.5 m. Everything is computed locally and deterministically, so it is instant and private. Ideal for deck and balustrade design tools, fabrication and estimating apps, and building calculators. Pure local computation — no key, no third-party service, instant. Uses the common 100 mm infill rule — confirm your local code. 3 compute endpoints. For stair rise and run use a stair API; for fence pickets a fence API.

api.oanor.com/handrail-api

Wood Pellet API

Wood-pellet heating maths as an API, computed locally and deterministically — the consumption, heat-output and storage numbers a homeowner, installer or heating planner sizes a pellet system by. The consumption endpoint gives the pellets to meet a heat demand = the demand ÷ the usable heat per kilo, where usable = the calorific value × the boiler efficiency: ENplus wood pellets hold about 4.8 kWh/kg and a modern pellet boiler runs ~90 %, so each kilo delivers roughly 4.3 kWh — a 10,000 kWh annual demand then needs about 2.3 tonnes of pellets, around 154 fifteen-kilo bags or a bulk delivery. The heat-output endpoint inverts it: the usable heat from a mass = mass × calorific value × efficiency, so a tonne of ENplus pellets is about 4,800 kWh gross of which a 90 % boiler delivers ~4,320 kWh — the equivalent of roughly 480 litres of heating oil or 432 m³ of natural gas. The storage-volume endpoint sizes the hopper or silo: storage = the pellet mass ÷ the bulk (poured) density, about 650 kg/m³ for ENplus, so 2.3 tonnes fill roughly 3.6 m³ — size the store for the full delivery plus headroom for the fill pipe. Everything is computed locally and deterministically, so it is instant and private. Ideal for pellet-heating and installer tools, home-energy and quoting apps, and renewable-heat calculators. Pure local computation — no key, no third-party service, instant. Uses standard ENplus figures — set your own for a specific pellet grade. 3 compute endpoints. For cordwood use a firewood API; for propane/LPG a propane API.

api.oanor.com/pellet-api

Domande frequenti

Risposte rapide su prezzi, quote e integrazione.

Come ottengo una chiave API per Gold Purity API?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama Gold Purity API con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di Gold Purity API?
Il piano gratuito consente 1 richiesta al secondo. I piani a pagamento arrivano fino a 50 richieste al secondo nel piano Mega. I limiti rigorosi restituiscono HTTP 429 oltre la quota — nessuna spesa imprevista.
Quanto costa Gold Purity API?
Gold Purity API ha un piano gratuito con 100 chiamate / mese. I piani a pagamento partono da €7.40 / mese con quote più alte e limiti di velocità più rapidi.
Posso cancellare l'abbonamento in qualsiasi momento?
Sì. I piani sono fatturati mensilmente e puoi cancellare in qualsiasi momento dalla dashboard di fatturazione. Nessun contratto a lungo termine e nessuna penale di cancellazione.
Gold Purity API è conforme al GDPR?
Tutte le richieste a Gold Purity API passano attraverso il nostro gateway in UE. La tua chiave upstream non lascia mai il nostro server e nessun dato personale viene condiviso con il fornitore upstream oltre alla richiesta inviata.

Scegli un endpoint dall'elenco a sinistra per visualizzarne i dettagli e provarlo.

Frammenti di codice

Iscriviti per ottenere una chiave API, quindi chiama qualsiasi percorso sotto il tuo slug.

curl https://api.oanor.com/goldpurity-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/goldpurity-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/goldpurity-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
    "https://api.oanor.com/goldpurity-api/SOME_PATH",
    headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())

Valutazioni

Accedi per votare.

Nessuna recensione ancora.

Discussione

Fai domande, condividi consigli, ricevi risposte dal provider e dagli altri sviluppatori. Pubblico — chiunque può leggere.

Accedi per scrivere o rispondere.

Accedi

Nuova discussione

/ 4000

📌 Fissato 🔒 Bloccato

·

· ·

/ 4000

🔒 Discussione bloccata — non si può più rispondere.

  • Nessuna discussione — inizia tu.

Supporto

Supporto privato 1:1 con il provider — fatturazione, integrazione, account. Solo tu e il team del provider vedete questi thread.

Accedi per aprire un ticket di supporto.

Accedi

Apri nuovo ticket

Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.

  • Nessun ticket per questa API.

Abbonamento attivo: le chiamate possono iniziare subito.

Invia la tua prima richiesta —

Abbonamento attivo: copia uno snippet e avvia la tua prima chiamata.