API · /knifesharp-api

Knife Sharpening API

salutare 3,532 Abbonati

Knife-sharpening maths as an API, computed locally and deterministically — the bevel and angle numbers a sharpener, cook or knifemaker sets a stone to. It uses the symmetric V-edge model: the bevel endpoint takes the blade thickness and a per-side (or inclusive) angle and returns the bevel face width = (thickness ÷ 2) ÷ sin(per-side angle), with the inclusive angle as twice the per-side — so a 2 mm blade ground at 15° per side has a 3.86 mm bevel and a 30° edge, and at a 40° inclusive (20° per side) a 2.92 mm bevel. The angle endpoint runs it in reverse for the marker (Sharpie) method: colour the edge, take one stroke, measure the shiny bevel, and per-side angle = asin((thickness ÷ 2) ÷ bevel width) tells you the angle you are actually holding. The recommend endpoint gives sensible inclusive-angle ranges by use — about 12–17° for razors, 20–30° for Japanese kitchen knives, 30–40° for Western chef’s and EDC, 40–50° for outdoor and hard use, 45–65° for axes — and converts any chosen inclusive angle to per-side and back. Everything is computed locally and deterministically, so it is instant and private. Ideal for knife, kitchen, EDC, bushcraft, woodworking and sharpening app developers, sharpening-jig and edge-geometry tools, and maker software. Pure local computation — no key, no third-party service, instant. Symmetric V-edge model, mm and degrees. Live, nothing stored. 3 compute endpoints.

api.oanor.com/knifesharp-api
Ottieni una chiave API Prova nel parco giochi → Contatta provider

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

/api/knifesharp-api/openapi.json
/api/knifesharp-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
81 ms
Sondaggi del server · 24 ore su 24
Abbonati
3,532
attiva
Chiamate totali
4
ultimi 7 giorni

Prezzi

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

Free

Gratis

  • 6,850 chiamate/mese
  • 2 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 6.850 Aufrufe/Monat
  • 2 req/sec
  • Bevel + Winkel + empfohlene Winkel
  • Keine Kreditkarte
Accedi per abbonarti

Starter

€4.32 /mese

  • 55,200 chiamate/mese
  • 6 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 55.200 Aufrufe/Monat
  • 6 req/sec
  • Marker-Methode Winkel, pro Seite ↔ inklusive
  • E-Mail-Support
Accedi per abbonarti

Pro

€11.85 /mese

  • 227,000 chiamate/mese
  • 15 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 227.000 Aufrufe/Monat
  • 15 req/sec
  • Sharpening-jig & edge-geometry Pipelines
  • Priority-Support
Accedi per abbonarti

Mega

€36.90 /mese

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

Costruito da

Correlato APIs

Altro APIs con tag sovrapposti.

Candy Temperature API

Candy-making maths as an API, computed locally and deterministically — the sugar-syrup stage numbers a confectioner reads a thermometer by. As sugar syrup boils it passes through named stages, each a temperature window with its own texture and uses, and getting within a few degrees is the difference between fudge and toffee. The stage endpoint names the stage for a temperature: 238 °F is the soft-ball stage (fudge, fondant, pralines), 305 °F is hard-crack (toffee, brittle, lollipops), and it handles °F or °C and the off-the-chart cases — still a thin syrup below thread, or darkening to burnt past caramel. The range endpoint gives the temperature window and uses of a named stage, from thread (223–234 °F) through soft-ball, firm-ball, hard-ball, soft-crack and hard-crack to caramel (320–350 °F), in both °F and °C. The altitude endpoint applies the rule that matters in the mountains: cook to 1 °F lower for every 500 feet of elevation, since water boils cooler, so a 300 °F hard-crack recipe is done at 290 °F at 5,000 feet. Everything is computed locally and deterministically, so it is instant and private. Ideal for baking, confectionery, recipe and kitchen app developers, candy-thermometer and timer tools, and cooking-class software. Pure local computation — no key, no third-party service, instant. Use a calibrated thermometer. Live, nothing stored. 3 compute endpoints.

api.oanor.com/candytemp-api

Window Tint API

Window-Tint-Mathematik als API, lokal und deterministisch berechnet – die Netto-VLT-Werte, nach denen ein Installateur oder Autobesitzer eine Folie auswählt. Der Haken bei Tönung ist, dass die sichtbare Lichtdurchlässigkeit durch Schichten multipliziert wird: Werksautoglas lässt bereits nur etwa 70–80 % des Lichts durch, daher entspricht die angegebene VLT einer Folie nicht dem, was am Ende herauskommt. Der vlt-Endpunkt multipliziert es aus – netto % = das Produkt der VLT jeder Schicht ÷ 100 – also ergibt eine 35 %-Folie auf 78 %-Werksglas 27,3 %, eine 5 %-Limo-Folie auf demselben Glas 3,9 %, und Sie können mehrere Schichten in einem Aufruf stapeln; er beschreibt auch, wie dunkel das aussieht, von fast klar bis abgedunkelt. Der erforderliche Endpunkt rechnet rückwärts: Um eine Ziel-Netto-VLT durch bekanntes Glas zu erreichen, benötigen Sie eine Folie von Ziel ÷ Glas × 100, also erfordert das Erreichen einer 35 %-Netto-VLT auf 78 %-Glas eine 44,9 %-Folie – und er kennzeichnet den unmöglichen Fall, wenn das Ziel heller ist als das bloße Glas bereits erlaubt. Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für Auto-Tönung, Fahrzeugveredelung, Glas- und Automobil-App-Entwickler, Folienauswahl- und Compliance-Tools sowie Werkstattsoftware. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofort. Gesetzliche Grenzwerte variieren je nach Rechtsordnung – prüfen Sie lokale Gesetze. Live, nichts wird gespeichert. 2 Compute-Endpunkte.

api.oanor.com/windowtint-api

Yahtzee Score API

Yahtzee-Spielstand-Mathematik als API, lokal und deterministisch berechnet – die Kategoriepunkte und Summen, auf denen eine Würfelspiel-Score-App basiert. (Es bewertet einen gegebenen Wurf; es würfelt nicht.) Der Score-Endpunkt nimmt fünf Würfel entgegen und gibt den Wert aller dreizehn Kästchen auf einmal zurück: die oberen Kästchen (Einser bis Sechser) ergeben die Summe dieser Augenzahl, Dreier- und Viererpasch sowie Chance ergeben die Summe aller fünf Würfel, ein Full House ist 25, eine kleine Straße (vier aufeinanderfolgende) 30, eine große Straße (fünf aufeinanderfolgende) 40 und ein Yahtzee (fünf Gleiche) 50 – also ist 3-3-3-5-6 20 Punkte bei Dreierpasch, 4-4-4-5-5 ist ein 25-Punkte-Full House, und es markiert das Kästchen mit der höchsten Punktzahl für Sie. Der Total-Endpunkt addiert eine fertige Karte: den 35-Punkte-Bonus für den oberen Abschnitt, wenn die oberen Kästchen 63 erreichen (und wie viele Punkte Sie noch dafür benötigen), plus 100 für jeden zusätzlichen Yahtzee, um die Gesamtsumme zu erhalten. Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für Entwickler von Würfelspiel-, Brettspiel-Begleit-, Familienspiel- und Scorekeeping-Apps, Scoreblatt- und Turnier-Tools sowie Spielsoftware. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofort. Live, nichts wird gespeichert. 2 Compute-Endpunkte. Für zufällige Würfe verwenden Sie eine Würfel-API.

api.oanor.com/yahtzee-api

Two-Stroke Mix API

Two-stroke premix maths as an API, computed locally and deterministically — the gas-to-oil numbers anyone running a chainsaw, string trimmer, leaf blower, outboard, dirt bike or RC engine mixes fuel by. The mix endpoint gives the oil to add to a tank of fuel at a given ratio: oil = fuel ÷ ratio, so one US gallon at 50:1 needs about 75.7 ml (2.6 fl oz) of two-stroke oil, 40:1 about 94.6 ml (3.2 fl oz) and 32:1 about 118 ml (4.0 fl oz), and it returns the total mix and the oil percentage too, in litres, gallons, millilitres or fluid ounces. The ratio endpoint runs it the other way — measure the fuel and the oil you actually put in and it tells you the real N:1 ratio, the oil percentage and the nearest common ratio, so you can check a mix or reverse-engineer a pre-mixed can. Get it wrong and it matters: too little oil and the engine seizes, too much and it fouls plugs and smokes — so always use the ratio in your tool’s manual. Everything is computed locally and deterministically, so it is instant and private. Ideal for small-engine, outdoor-power-equipment, marine, powersports and DIY app developers, fuel-mixing and shop tools, and maintenance software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 2 compute endpoints.

api.oanor.com/twostroke-api

Domande frequenti

Risposte rapide su prezzi, quote e integrazione.

Come ottengo una chiave API per Knife Sharpening API?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama Knife Sharpening API con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di Knife Sharpening 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 Knife Sharpening API?
Knife Sharpening API ha un piano gratuito con 100 chiamate / mese. I piani a pagamento partono da €4.32 / 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.
Knife Sharpening API è conforme al GDPR?
Tutte le richieste a Knife Sharpening 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/knifesharp-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/knifesharp-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/knifesharp-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/knifesharp-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.