Cable length from span & sag
API · /catenary-api
Catenary Cable API
Catenary (hanging-cable) maths as an API, computed locally and deterministically. The sag endpoint solves the exact catenary for a cable hung between two level supports: from the span, the weight per unit length and either the horizontal tension or the sag, it returns the catenary parameter a = H/w, the sag a·(cosh(L/2a) − 1), the cable length 2a·sinh(L/2a), the minimum tension (the horizontal tension at the lowest point) and the maximum tension at the supports (H·cosh(L/2a)), plus the slack over the straight span. The parabolic endpoint gives the shallow-sag parabolic approximation — sag = w·L²/(8·H) — that is standard for overhead utility lines, and converts between sag and tension either way. The length endpoint returns the cable length for a given span and sag, with the parabolic value alongside for comparison. Forces and lengths are unit-agnostic but must be consistent (for example newtons, newtons per metre and metres). Everything is computed locally and deterministically, so it is instant and private. Ideal for power-line and transmission tools, zip-line and rigging apps, suspension and surveying calculators, and physics and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is hanging-cable catenary maths; for rigging working load limits use a rigging API and for beam deflection use a beam API.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 79 ms
- Server probes · 24h
- Subscribers
- 4,761
- active
- Total calls
- 76
- 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)
- Exact catenary sag between level supports
- Horizontal & support tension output
- 2 requests/sec, JSON responses
Starter
€9.00 /month
- 20,000 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- Sag, tension and arc-length endpoints
- Distributed-load (self-weight + ice) support
- Deterministic results, no rate spikes
- Email support
Pro
€24.00 /month
- 120,000 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- Unleveled-support and multi-span solving
- Batch cable runs in one call
- SI + imperial unit handling
- Priority support & 99.9% uptime
Mega
€74.00 /month
- 639,000 calls / month
- 60 requests / second
- Hard cap (429 above quota, no overage)
- High-volume CAD/structural pipeline use
- Full tension envelope & safety-factor output
- Highest concurrency (60 rps)
- Dedicated support & SLA
Built by
Related APIs
Other APIs with overlapping tags.
Wire Gauge API
AWG (American Wire Gauge) maths as an API, computed locally and deterministically. The awg endpoint returns the physical properties of a gauge — the diameter, 0.127·92^((36−n)/39) mm, the cross-section area, the DC resistance per kilometre and per 1000 ft for copper or aluminium, and the Preece fusing current (the point at which the wire melts, far above any safe operating ampacity). The fromdiameter endpoint goes the other way, giving the nearest AWG for a measured diameter or cross-section area, n = 36 − 39·log₉₂(d/0.127). The resistance endpoint gives the resistance of a wire run from its gauge, length and material, R = ρ·L/A. Gauges 0/0 (1/0), 00 (2/0) and 000 (3/0) are entered as −1, −2 and −3. Everything is computed locally and deterministically, so it is instant and private. Ideal for electronics, electrical and maker app developers, wiring and cable-selection tools, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is wire-gauge geometry and resistance; for cable voltage drop over a circuit use a voltage-drop API.
api.oanor.com/wiregauge-api
Knitting Gauge API
Knitting and crochet gauge maths as an API, computed locally and deterministically. The stitches endpoint turns a gauge — the standard stitches and rows per 10 cm measured from a tension swatch — into the number of stitches to cast on for a target width and the number of rows for a target length; at 22 stitches and 30 rows per 10 cm, a 50 cm wide by 60 cm long piece needs 110 stitches and 180 rows. The gauge endpoint works backwards from a measured swatch, converting a count over a measured distance into stitches (or rows) per 10 cm, per centimetre and per inch — 33 stitches over 15 cm is a gauge of 22 per 10 cm. The convert-pattern endpoint re-scales a pattern written for one gauge to your own gauge so the finished garment keeps its intended size: your count = pattern count · (your gauge / pattern gauge), so a 100-stitch cast-on at a 20-per-10 cm pattern becomes 110 at your 22-per-10 cm tension. Dimensions are in centimetres. Everything is computed locally and deterministically, so it is instant and private. Ideal for knitting, crochet, pattern-design, craft-marketplace and maker app developers, gauge and tension calculators, and yarn-shop tools. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is gauge and stitch maths; works for crochet too by using your stitch gauge.
api.oanor.com/knitting-api
Railway Tractive Effort API
Railway train-performance maths as an API, computed locally and deterministically — the tractive-effort, resistance and adhesion numbers a railway engineer, train planner or rail-sim developer rates motive power with. The tractive-effort endpoint gives the pulling force a locomotive develops = 375 × horsepower × efficiency ÷ speed (mph), the classic hyperbolic curve where a constant-power loco pulls hardest at low speed and tapers as it accelerates — 4,000 hp at 25 mph and 82 % efficiency is about 49,200 lbf at the rail. The resistance endpoint gives the forces a train fights: grade resistance ≈ 20 lb per ton per 1 % of grade (the weight component along the slope, the dominant force on a hill — a 5,000-ton train on a 1 % grade fights 100,000 lbf) plus curve resistance ≈ 0.8 lb per ton per degree of curve from flange friction. The adhesion endpoint gives the hard ceiling: however much power a loco has, it can only pull as hard as the wheels grip — maximum starting tractive effort = the adhesion coefficient (≈ 0.25 dry, more with sand) × the weight on the driving wheels, so 200 tons on the drivers is about 100,000 lbf before slip. Everything is computed locally and deterministically, so it is instant and private. Ideal for rail-operations and motive-power planning tools, train-simulator and railfan apps, and transport-engineering utilities. Pure local computation — no key, no third-party service, instant. Excludes the speed-dependent Davis rolling/air resistance. 3 compute endpoints. For highway curve geometry use a horizontal-curve API.
api.oanor.com/railway-api
Worm Gear API
Worm-gear engineering maths as an API, computed locally and deterministically — the ratio, lead-angle and efficiency numbers a machine designer or millwright sizes a worm drive with. The ratio endpoint gives the reduction = wheel teeth ÷ worm starts, so a single-start worm on a 40-tooth wheel is a big 40:1 reduction in one compact stage — the high ratio in a small package is the whole appeal of a worm drive. The geometry endpoint gives the lead (= starts × axial pitch, with axial pitch = π × module) and the lead angle = atan(lead ÷ (π × worm pitch diameter)), and tests for self-locking: a small lead angle (roughly under 5–6° for typical steel-on-bronze) means the wheel cannot back-drive the worm — invaluable for hoists and holding loads, at the cost of efficiency. The efficiency endpoint gives the mesh efficiency when the worm drives = tan(lead angle) ÷ tan(lead angle + friction angle), which is low for the small lead angles that give big ratios — often 50–70 %, which is why worm gears run warm and need good lubrication — while high-lead multi-start worms reach 90 %+; when the lead angle drops to the friction angle the drive becomes self-locking. Everything is computed locally and deterministically, so it is instant and private. Ideal for mechanical-design and gearbox tools, machine-building and CAD utilities, and engineering calculators. Pure local computation — no key, no third-party service, instant. Confirm self-locking dynamically — vibration can unlock a marginal pair. 3 compute endpoints. For spur gears use a spur-gear API; for a general ratio a gear-ratio API.
api.oanor.com/wormgear-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Catenary Cable API?
What's the rate limit for Catenary Cable API?
How much does Catenary Cable API cost?
Can I cancel my subscription anytime?
Is Catenary Cable 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/catenary-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/catenary-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/catenary-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/catenary-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.