Passes and time to surface an area
API · /cncfinish-api
CNC Surface Finish API
healthy
4,693 Subscribers
CNC surface-finishing maths as an API, computed locally and deterministically — the scallop, stepover and pass numbers a CNC machinist dials in for a smooth finish. The scallop endpoint gives the cusp height a ball-nose tool leaves between passes, h = R − √(R² − (stepover/2)²), so a half-inch ball at a 0.05-inch stepover leaves about a 1.25-thou ridge — tighter stepover, smaller cusp, far more passes. The stepover endpoint inverts it: the stepover for a target scallop height, 2·√(R² − (R−h)²), reported also as a percent of tool diameter (fine finishing runs ~4–10 %) so it carries across jobs — and a bigger finishing ball reaches the same finish at a wider, faster stepover. The passes endpoint turns a surface into work: passes = width ÷ stepover rounded up plus one, the total cutting travel, and the cutting time at a given feed rate — surfacing a 4×6-inch area at a 0.05-inch stepover is 81 passes and 486 inches of travel, under five minutes at 100 ipm. Everything is computed locally and deterministically, so it is instant and private. Ideal for CNC and CAM apps, machinist and toolpath calculators, maker and job-shop tools, and engineering aids. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. For cutting speed, feed and rpm use a machining API.
api.oanor.com/cncfinish-api
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 87 ms
- Server probes · 24h
- Subscribers
- 4,693
- active
- Total calls
- 4
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 500 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 500 calls/month
- 2 req/sec
- Scallop + stepover + passes
- No credit card
Starter
€5.45 /month
- 13,100 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 13,100 calls/month
- 6 req/sec
- Ball-nose finish geometry
- Email support
Pro
€17.70 /month
- 82,500 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 82,500 calls/month
- 15 req/sec
- CAM & toolpath pipelines
- Priority support
Mega
€52.00 /month
- 266,000 calls / month
- 36 requests / second
- Hard cap (429 above quota, no overage)
- 266,000 calls/month
- 36 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Stepper Motor API
Stepper-motor motion maths as an API, computed locally and deterministically — the steps-per-millimetre and speed numbers a 3D-printer, CNC or robotics builder configures a machine with. The leadscrew endpoint gives the steps per mm for a lead-screw or ball-screw axis: (motor steps per revolution × microstepping) ÷ the screw lead, so a 1.8° motor (200 steps) at 16 microsteps on an 8 mm-lead screw is 400 steps/mm with 2.5 µm of resolution — the value that goes straight into the firmware. The belt endpoint does the same for a belt-and-pulley axis, where the travel per motor turn is the pulley teeth × the belt pitch (GT2 belt = 2 mm), so a 20-tooth GT2 pulley gives the classic 80 steps/mm of a 3D-printer X/Y axis, and shows the speed-versus-precision trade of a bigger pulley. The speed endpoint turns a steps-per-mm and a step pulse rate into the axis speed in mm/s and mm/min — at 80 steps/mm a 40 kHz step rate is 500 mm/s, though the real limit is the motor stalling at high step rates and the controller pulse ceiling. It also notes that microstepping adds smoothness, not true accuracy, since torque per microstep falls. Everything is computed locally and deterministically, so it is instant and private. Ideal for 3D-printer and CNC firmware setup, motion-control and robotics tools, and maker calculators. Pure local computation — no key, no third-party service, instant. Ideal-geometry estimates — leave a margin below the theoretical top speed. 3 compute endpoints. For CNC surface finish use a CNC-finish API; for gear ratios a gear-ratio API.
api.oanor.com/steppermotor-api
Machining Speed API
Machining cutting-speed and feed maths as an API, computed locally and deterministically. The speed endpoint converts between cutting (surface) speed and spindle rpm for a given tool or workpiece diameter, in both directions and in either unit system: metric uses N = Vc·1000/(π·D) with Vc in metres per minute and D in millimetres, and imperial uses RPM = SFM·12/(π·D) with the surface speed in feet per minute and the diameter in inches. The feed endpoint computes the table feed rate from the feed per tooth (chip load), the number of teeth or flutes and the spindle rpm for milling (feed = fz·z·N), or from the feed per revolution for turning and drilling, and reports it in millimetres or inches per minute. The materials endpoint lists typical carbide cutting speeds by material, from aluminium and brass through mild and stainless steel to titanium, with a note to use about a third for HSS tooling. Everything is computed locally and deterministically, so it is instant and private. An indicative aid — always confirm with the tool maker's data and adjust for depth of cut, coolant and rigidity. Ideal for CNC and machine-shop tools, CAM and feeds-and-speeds apps, maker and hobby machining, and manufacturing calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is machining feeds and speeds; for screw-thread pitch and tap drill use a thread API and for bolt-circle layouts use a bolt-circle API.
api.oanor.com/machining-api
Bolt Circle API
Bolt-circle (bolt pattern / PCD) geometry as an API, computed locally and deterministically. The coordinates endpoint lays out a set of equally spaced holes on a circle: from the bolt-circle diameter (or radius), the number of holes, an optional start angle, centre offset and direction, it returns the X and Y coordinate and angle of every hole, the angular step (360 ÷ number of holes) and the chord between adjacent holes — exactly what a CNC or drawing needs. The chord endpoint gives the straight-line distance between any two holes on the pattern using chord = 2·R·sin(central angle ÷ 2), taking the shorter way around. The diameter endpoint works in reverse: from a measured distance between two holes and the number of holes it recovers the bolt-circle diameter, so you can reverse-engineer an existing flange or wheel. Lengths are unit-agnostic — the output is in whatever unit you supply. Everything is computed locally and deterministically, so it is instant and private. Ideal for CNC and CAD tools, machining and fabrication apps, flange, wheel and hub design, and drilling-jig and robotics projects. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is bolt-circle geometry; for screw-thread pitch and tap drill use a thread API and for spur-gear geometry use a gear API.
api.oanor.com/boltcircle-api
Taper Calculator API
Taper and cone geometry as an API, computed locally and deterministically. The taper endpoint relates the large and small diameters, the length and the taper of a conical part: give the two diameters and the length and it returns the taper ratio, the taper per foot and per inch (for inch parts), the included angle 2·atan((D−d)/(2L)) and the half (taper) angle from the axis — or leave one of the diameters or the length out and provide the taper per foot, and it solves for the missing dimension. The diameter-at endpoint gives the diameter (and radius) at any distance along the taper, measured from either the large or the small end, by linear interpolation d(x) = D − (D−d)·x/L. The morse endpoint is a reference of the standard Morse taper series MT0 to MT7, with each taper's taper per foot, gauge-line large and small diameter, length and included angle. Lengths and diameters use consistent units (inches by default, or millimetres for the angle and ratio outputs). Everything is computed locally and deterministically, so it is instant and private. Ideal for machining and lathe tools, CAD and toolmaking apps, maker and metalworking projects, and mechanical-engineering calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is taper geometry; for screw-thread pitch and tap drill use a thread API and for spur-gear geometry use a gear API.
api.oanor.com/taper-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for CNC Surface Finish API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call CNC Surface Finish API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for CNC Surface Finish API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does CNC Surface Finish API cost?
CNC Surface Finish API has a free tier with 100 calls / month. Paid plans start at €5.45 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is CNC Surface Finish API GDPR-compliant?
All requests to CNC Surface Finish API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/cncfinish-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/cncfinish-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/cncfinish-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/cncfinish-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
📌 Pinned
🔒 Locked
·
·
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.