Feed rate from chip load
API · /machining-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 health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 97 ms
- Server probes · 24h
- Subscribers
- 3,761
- active
- Total calls
- 40
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 2,000 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- Surface/cutting speed to spindle RPM conversion
- Metric and imperial units
- 2 requests/sec, 2,000 calls/month
Starter
€9.00 /month
- 20,000 calls / month
- 5 requests / second
- Hard cap (429 above quota, no overage)
- Full feed-rate and chip-load endpoints
- SFM/RPM/IPM round-trip conversions
- 20,000 calls/month, 5 req/sec
- Deterministic, instant results
Pro
€24.00 /month
- 120,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- Material- and tool-diameter aware feeds & speeds
- Batch tool-path parameter computation
- 120,000 calls/month, 15 req/sec
- Email support
Mega
€74.00 /month
- 631,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- High-volume CAM/MES integration tier
- 600,000 calls/month, 40 req/sec
- Priority support and uptime SLA
- Bulk multi-tool speed/feed batches
Built by
Related APIs
Other APIs with overlapping tags.
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
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
Screw Thread API
Screw-thread geometry as an API, computed locally and deterministically for the 60° ISO metric and Unified (UTS) thread form. The pitch endpoint converts between the thread pitch in millimetres and threads per inch (TPI = 25.4 ÷ pitch) and works out the lead — the distance the thread advances in one turn — from the pitch and the number of starts. The dimensions endpoint takes a nominal (major) diameter and a pitch and returns the full set of thread diameters and heights: the fundamental triangle height, the external thread height, the pitch diameter (D − 0.6495·P), the external minor diameter (D − 1.2269·P) and the internal minor diameter (D − 1.0825·P), in both millimetres and inches. The tapdrill endpoint gives the drill size for cutting an internal thread: the standard metric rule of nominal diameter minus pitch (about 75–83% thread), the resulting thread engagement, and — for a target engagement percentage — the matching drill size. Diameters accept millimetres or inches, and threads can be specified by pitch or by TPI. Everything is computed locally and deterministically, so it is instant and private. Ideal for machining and CNC tools, mechanical-design and CAD apps, maker and 3D-printing projects, and hardware and fastener catalogues. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is screw-thread geometry; for the torque to tighten a bolt use a torque API.
api.oanor.com/thread-api
Welding Settings API
Welding settings and consumables maths as an API, computed locally and deterministically — the amperage, wire and gas numbers a welder or fabricator dials a machine in with. (For joint strength, that is a separate weld-strength calculation.) The amperage endpoint gives a starting current from material thickness using the mild-steel rule of thumb of about one amp per 0.001 inch — so an eighth-inch plate runs around 125 A, give or take ten percent — and suggests an electrode or wire size to match. The deposition endpoint does the MIG arithmetic exactly: deposition rate (lb/hr) = wire feed speed × the wire’s weight per inch × 60 × efficiency, where weight per inch = (π/4 · d²) × 0.284 lb/in³ for steel, so 0.035-inch wire at 300 in/min lays down about 4.9 lb/hr fed, 4.8 deposited at 98 % — and from a target deposit it returns the arc time and the pounds of wire to buy. The gas endpoint sizes shielding gas: gas used (ft³) = flow in CFH × arc time in hours, and a cylinder’s arc-time duration, so 35 CFH empties an 80 ft³ bottle in about 2.3 hours of actual arc time. Everything is computed locally and deterministically, so it is instant and private. Ideal for welding, metal-fabrication, manufacturing and shop-management app developers, job-costing and consumable-planning tools, and welding-education software. Pure local computation — no key, no third-party service, instant. Machine settings, not joint strength. Live, nothing stored. 3 compute endpoints.
api.oanor.com/welding-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Machining Speed API?
What's the rate limit for Machining Speed API?
How much does Machining Speed API cost?
Can I cancel my subscription anytime?
Is Machining Speed API GDPR-compliant?
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/machining-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/machining-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/machining-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/machining-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
·
-
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.