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.

Baking Pan Scaler API

Baking-pan maths as an API, computed locally and deterministically — the area and scale-factor numbers a baker resizes a recipe between pans with. The trick everyone gets wrong is that a recipe scales by the pan’s AREA, not its diameter, so a 10-inch round holds far more batter than a 9-inch. The area endpoint gives the surface area of any pan — round and springform as π/4·d², square as s², rectangle as length × width, and bundt or tube pans as the ring (the outer circle minus the centre hole) — so a 9-inch round is 63.6 in², an 8-inch square 64 and a 9×13 is 117; add a depth and it returns the volume in cubic inches and cups. The convert endpoint gives the scale factor to move a recipe from one pan to another, factor = target area ÷ source area: a 9-inch round to a 9×13 is ×1.84, and two 8-inch rounds really do equal one 9×13. Pass an ingredient amount and it scales it for you, with a note to keep the batter depth similar and adjust the bake time. Everything is computed locally and deterministically, so it is instant and private. Ideal for baking, recipe, meal-prep and kitchen app developers, recipe-scaling and substitution tools, and culinary software. Pure local computation — no key, no third-party service, instant. Inches. Live, nothing stored. 2 compute endpoints. For ingredient unit conversion use a cooking API.

api.oanor.com/panscale-api

Grain Bin API

Grain-Bin-Speichermathematik als API, lokal und deterministisch berechnet – die Scheffel- und Gewichtszahlen, mit denen ein Landwirt oder Elevator die Lagerkapazität bemisst. Der Bushels-Endpunkt misst ein rundes Silo: Grundfläche × Korntiefe ergibt Kubikfuß, und ein Kubikfuß fasst etwa 0,8036 Scheffel, sodass ein 18-Fuß-Silo, das 20 Fuß gefüllt ist, etwa 4.090 Scheffel fasst – und Getreide, das zu einem Kegel aufgehäuft ist, addiert einen Kegel von (1/3) × Grundfläche × Spitzenhöhe, sodass eine 4-Fuß-Spitze etwa 270 weitere Scheffel hinzufügt. Der Weight-Endpunkt wandelt Scheffel in Gewicht um, basierend auf dem Standard-Testgewicht der Ernte – Mais und Sorghum bei 56 Pfund pro Scheffel, Weizen und Sojabohnen 60, Hafer 32, Gerste 48 – also wiegen diese 4.090 Scheffel Mais 229.040 Pfund, etwa 114,5 US-Tonnen oder 104 Tonnen; übergeben Sie ein gemessenes Testgewicht für leichtes oder schweres Getreide. Alles wird lokal und deterministisch berechnet, daher ist es sofortig und privat. Ideal für Entwickler von Apps für Landwirtschaft, Getreideheber, Farmmanagement und Agrartechnologie, für Speicherkapazitäts- und Inventar-Tools sowie Erntesoftware. Reine lokale Berechnung – kein API-Key, kein Drittanbieterdienst, sofortig. US-Einheiten (Fuß, Scheffel, Pfund). Live, nichts wird gespeichert. 2 Compute-Endpunkte.

api.oanor.com/grainbin-api

ADA Ramp API

ADA wheelchair-ramp maths as an API, computed locally and deterministically — the run, landing and slope numbers a builder or accessibility planner sizes a ramp by. The rule the ADA fixes is 1 inch of rise per 12 of run, a maximum 8.33 % slope, so the ramp endpoint turns a rise into the ramp: run = rise × 12 (or × 16 / × 20 for a gentler grade if you have the room), plus the level landings the code requires — a 5-foot landing top and bottom and another between runs whenever the rise exceeds 30 inches — and the total length end to end, so a 24-inch rise needs a 24-foot run and 34 feet overall, while a 36-inch rise breaks into two runs with an intermediate landing for 51 feet. The fit endpoint answers the real-world question: does a ramp for this rise fit the run you have? It returns the minimum run an ADA 1:12 ramp needs, whether your space is enough, and the slope you would actually get if you forced it in — flagging when that exceeds 8.33 % and you need a switchback or a lower rise. Everything is computed locally and deterministically, so it is instant and private. Ideal for construction, accessibility, home-modification and contractor app developers, ramp-estimator and code-check tools, and building software. Pure local computation — no key, no third-party service, instant. Confirm against current ADA and local code. Live, nothing stored. 2 compute endpoints.

api.oanor.com/adaramp-api

Farkle Score API

Farkle-Würfelbewertungsmathematik als API, lokal und deterministisch berechnet – die Punkte, die eine Farkle- (Zilch, Ten Thousand) Bewertungs-App für einen Wurf vergibt. Der Score-Endpunkt nimmt bis zu sechs Würfel entgegen und gibt den Wert nach dem gängigen Regelwerk zurück: eine einzelne 1 ist 100 und eine einzelne 5 ist 50; drei Gleiche ergeben den Augenzahl mal 100 (drei 1er sind die Ausnahme mit 1000); vier, fünf und sechs Gleiche sind 1000, 2000 und 3000; eine 1-zu-6-Straße oder drei Paare sind 1500; und zwei Drillinge sind 2500 – also 1-1-1-5-5-5 ergibt 2500 als zwei Drillinge statt 1100, eine 1-2-3-4-5-6-Straße ist 1500, und 6-6-6-2-3 ist 600 mit den toten 2 und 3. Es kennzeichnet einen Farkle, wenn nichts zählt (man verliert die Punkte des Zuges) und sagt, ob jeder Würfel gezählt wurde – heiße Würfel, die es erlauben, alle sechs erneut zu würfeln. Die Regelwerke variieren, daher bewertet es das weit verbreitete Set und gibt dies an. Alles wird lokal und deterministisch berechnet, also sofort und privat. Ideal für Entwickler von Würfelspielen, Partyspielen und Bewertungs-Apps, Score-Helfer und Spieleabend-Tools sowie Brettspiel-Begleitsoftware. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofort. Bewertet einen Wurf; es würfelt nicht. Live, nichts wird gespeichert. 1 Compute-Endpunkt.

api.oanor.com/farkle-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.