Amperage from thickness
API · /welding-api
Welding Settings API
healthy
4,220 Subscribers
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
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 79 ms
- Server probes · 24h
- Subscribers
- 4,220
- active
- Total calls
- 4
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 6,600 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 6,600 calls/month
- 2 req/sec
- Amperage + deposition + shielding gas
- No credit card
Starter
€4.48 /month
- 52,800 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 52,800 calls/month
- 6 req/sec
- Wire usage, arc time, cylinder duration
- Email support
Pro
€12.32 /month
- 218,500 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 218,500 calls/month
- 15 req/sec
- Job-costing & consumable-planning pipelines
- Priority support
Mega
€39.20 /month
- 1,290,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 1,290,000 calls/month
- 40 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Weld Strength API
Weld design maths as an API, computed locally and deterministically. The fillet endpoint sizes an equal-leg fillet weld: from the leg size, the weld length and an allowable shear stress it returns the effective throat (leg ÷ √2), the effective area, the load capacity and the strength per millimetre of weld; give a design force instead of a leg and it returns the required throat and leg size, and if you also pass a provided leg it reports the utilization and whether the weld is adequate. The butt endpoint handles a full-penetration butt (groove) weld, where the effective throat equals the plate thickness, returning the area and capacity. The throat endpoint converts between leg and throat — equal-leg (throat = leg ÷ √2), unequal legs (throat = a·b ÷ √(a²+b²)) and throat back to leg. Lengths are in millimetres, stress in megapascals and force in newtons. Everything is computed locally and deterministically, so it is instant and private. An estimating aid, not a code-stamped design — use the allowable stress and electrode from your governing code (AISC, Eurocode). Ideal for structural and fabrication tools, weld-design and estimating apps, maker and metalwork projects, and engineering calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is weld strength sizing; for bolt tightening torque use a torque API and for the weight of the steel use a metal-weight API.
api.oanor.com/weld-api
Sheet Metal API
Sheet-metal bending maths as an API, computed locally and deterministically. The bend-allowance endpoint computes the bend allowance, bend deduction and outside setback for a single bend from the material thickness, the inside bend radius, the bend angle and the K-factor: the bend allowance is BA = θ·(r + K·t), the outside setback is OSSB = (r + t)·tan(θ/2) and the bend deduction is BD = 2·OSSB − BA, with the neutral-axis position reported too. The flat-length endpoint computes the flat blank length you need to cut: from a list of outside (mold-line) flange lengths, or two flanges, or a total, it subtracts the bend deduction for each bend. The kfactor endpoint lists typical K-factors by material — aluminium around 0.33, mild steel 0.44, stainless 0.45 — and estimates a K-factor from the inside-radius-to-thickness ratio. The K-factor can be given directly or chosen by material, and if the inside radius is omitted it defaults to the thickness. Lengths are unit-agnostic — the output matches whatever unit you supply. Everything is computed locally and deterministically, so it is instant and private. Ideal for sheet-metal CAD/CAM and press-brake tools, fabrication and unfolding apps, maker and prototyping projects, and manufacturing calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is sheet-metal bend development; for the weight of the blank use a metal-weight API.
api.oanor.com/sheetmetal-api
Metal Weight API
Metal stock weight and cost as an API, computed locally and deterministically. The weight endpoint computes the mass of a length of metal stock from its shape, dimensions and material: round bar, square bar, flat bar or plate, sheet, hexagonal bar, round tube or pipe and rectangular (box) tube. It works out the cross-sectional area, multiplies by the length and the material density, and returns the weight per piece and the total for a quantity — in kilograms, pounds, grams and tonnes — along with the volume. Material density is looked up from a built-in table of metals (steel, stainless, aluminium, copper, brass, bronze, lead, zinc, titanium, nickel, gold, silver and more) or you can pass an explicit density. The cost endpoint multiplies that weight by a price per kilogram, pound or tonne to give the material cost per piece and in total. The materials endpoint lists the densities. Dimensions accept millimetres, centimetres, metres, inches or feet. Everything is computed locally and deterministically, so it is instant and private. Ideal for metal fabrication and machine-shop tools, engineering and CAD apps, scrap and stock quoting, and shipping-weight estimates. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is metal stock weight from geometry and density; for beam reactions and deflection use a beam API and for live metal spot prices use a commodities API.
api.oanor.com/metalweight-api
OEE Manufacturing API
Overall Equipment Effectiveness (OEE) and lean-manufacturing maths as an API, computed locally and deterministically — the factory-floor productivity metric behind TPM and continuous improvement. The oee endpoint takes the planned production time, downtime, the total and good piece counts and the ideal cycle time (seconds per piece, or an ideal rate in pieces per minute) and returns the three factors and their product: Availability = run time / planned time, Performance = ideal time for the parts made / run time, Quality = good / total, and OEE = Availability × Performance × Quality — the textbook example of a 420-minute shift with 47 minutes down, 19,271 parts and 423 rejects lands exactly on 74.79 % (88.81 % × 86.11 % × 97.80 %). It also breaks out the six-big-losses view: availability loss, performance (speed) loss in parts, quality loss and the fully-productive part count. The takt endpoint gives the takt time = available time / customer demand (the drumbeat the line must match), the required rate, and — given a cycle time or a total work content — the line capacity, utilisation, whether it meets demand and the minimum number of workstations with the line-balancing efficiency. Everything is computed locally and deterministically, so it is instant and private. Ideal for manufacturing, smart-factory, MES, IoT-dashboard and lean/TPM app developers, production-line monitoring and continuous-improvement tools, and industrial-engineering training. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 2 compute endpoints. This is OEE and takt maths; for equipment reliability/MTBF use a reliability API.
api.oanor.com/oee-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Welding Settings API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Welding Settings API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Welding Settings 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 Welding Settings API cost?
Welding Settings API has a free tier with 100 calls / month. Paid plans start at €4.48 / 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 Welding Settings API GDPR-compliant?
All requests to Welding Settings 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/welding-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/welding-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/welding-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/welding-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.