Metacentric height GM
API · /shipstability-api
Ship Stability API
Ship initial-stability maths as an API, computed locally and deterministically — the metacentric-height, righting-moment and rolling-period numbers a naval architect, ship officer or marine-surveyor judges a vessel by. The metacentric-height endpoint gives GM = KM − KG, the single most important stability figure: the height of the metacentre (set by the hull form and draught) above the centre of gravity (set by how the ship is loaded), with a classification from a dangerous negative GM, through tender and comfortable, to a stiff GM that rolls violently — naval architects aim for the middle, because too little is unsafe and too much is hard on cargo and crew. The righting-moment endpoint gives the small-angle righting arm GZ ≈ GM · sin(heel) and the righting moment (GZ × displacement) that pushes the ship back upright, valid up to roughly 7–10° before the true GZ curve bends away. The roll-period endpoint gives the natural transverse rolling period T = 2π·k / √(g·GM) from the GM and beam — the same relation sailors run in reverse as the rolling-period test, where a suddenly longer roll warns that GM has dropped. Everything is computed locally and deterministically, so it is instant and private. Ideal for naval-architecture and ship-design tools, marine-surveyor and loading-software utilities, maritime-training apps and stability dashboards. Pure local computation — no key, no third-party service, instant. Initial-stability estimates — use full KN cross-curves for large angles. 3 compute endpoints. For hull speed and design ratios use a sailing API.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 85 ms
- Server probes · 24h
- Subscribers
- 3,377
- active
- Total calls
- 76
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 4,500 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 4,500 calls/month
- 2 req/sec
- GM + righting moment + roll period
- No credit card
Starter
€13.80 /month
- 49,000 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 49,000 calls/month
- 6 req/sec
- Stability classes & rolling-period test
- Email support
Pro
€41.50 /month
- 213,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 213,000 calls/month
- 15 req/sec
- Ship-design & loading-software pipelines
- Priority support
Mega
€129.00 /month
- 1,130,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 1,130,000 calls/month
- 40 req/sec
- Fleet & classification scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Sailing & Hull Design API
Sailing and naval-architecture maths as an API, computed locally and deterministically — the hull-speed and design-ratio numbers a sailor, boat-shopper or yacht designer sizes a boat with. The hullspeed endpoint gives the theoretical displacement speed limit from the waterline: hull speed = 1.34 × √LWL (feet) in knots, so a 25-foot waterline tops out around 6.7 knots (7.7 mph, 12.4 km/h) — with a tunable coefficient up to about 1.5 for light, easily-driven hulls, since planing boats leave the formula behind entirely. The ratios endpoint computes the two classic performance numbers: the Sail Area/Displacement ratio, SA/D = sail area ÷ (displaced volume in ft³)^⅔ using displaced volume = displacement ÷ 64 lb/ft³ for seawater — around 16–18 is a typical cruiser and 20-plus is sporty — and the Displacement/Length ratio, DLR = (displacement in long tons) ÷ (0.01 × LWL)³, where under 200 is light and over 300 is heavy, each returned with a class label. The ballast endpoint gives the ballast ratio = ballast ÷ displacement × 100, a rough proxy for stiffness and sail-carrying power that most cruisers hit near 35–45 %. Everything is computed locally and deterministically, so it is instant and private. Ideal for sailing, boating, marine, yacht-brokerage and boat-design app developers, boat-comparison and rig-sizing tools, and naval-architecture calculators. Pure local computation — no key, no third-party service, instant. Imperial units. Live, nothing stored. 3 compute endpoints. Design-ratio estimates, not a velocity prediction program.
api.oanor.com/sailing-api
Froude Number API
Froude-number hydrodynamics as an API, computed locally and deterministically. The number endpoint computes the Froude number Fr = v/√(g·L) — the dimensionless ratio of inertial to gravitational forces — from a velocity and a characteristic length, classifies the flow as subcritical (Fr<1, tranquil), critical (Fr=1) or supercritical (Fr>1, rapid), and returns the critical velocity √(g·L) at which Fr=1; the velocity endpoint inverts it to v = Fr·√(g·L). The channel endpoint gives the open-channel Froude number from a flow velocity and depth, the flow regime, and the critical depth y_c = (q²/g)^(1/3) for the unit discharge q = v·y — the boundary between tranquil and shooting flow used in spillway and weir design. The hull-speed endpoint computes the displacement hull speed of a boat from its waterline length, v = 1.34·√(L_wl in ft) knots, the wave-making speed limit where the bow and stern waves equal the hull length, returned in knots, m/s and km/h with the corresponding Froude number — a 10 m waterline gives about 7.7 knots. Gravity defaults to 9.80665 m/s². Everything is computed locally and deterministically, so it is instant and private. Ideal for naval-architecture, marine, hydraulics, civil-engineering, river-modelling and fluid-mechanics-education app developers, spillway, weir and hull-design tools, and simulation software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is the Froude number and flow regime; for Manning open-channel discharge use a Manning API.
api.oanor.com/froude-api
Marine & Surf Forecast API
Marine and surf forecasts as an API, powered by Open-Meteo — clean JSON, no key. Get the current sea state and the hourly and daily wave forecast for any coastline by latitude/longitude or simply by place name: significant wave height, period and direction, plus the swell and wind-wave components broken out separately, and daily maxima and dominant directions. A built-in geocoding helper turns a place name into coordinates. Forecasts run up to ten days ahead. Live forecast data straight from Open-Meteo's marine model. Ideal for surf-report apps, sailing and boating tools, coastal and marine-operations dashboards and beach widgets. 4 data endpoints. Authenticated with an x-oanor-key; fair-use rate limits per plan.
api.oanor.com/marine-api
Sea Horizon API
Sea-horizon and visibility maths as an API, computed locally and deterministically — the distance-to-horizon, geographic-range and dip numbers a mariner, coastal navigator or marine app works sightings with. The horizon endpoint gives the distance to the sea horizon ≈ 1.169·√(height of eye in feet) nautical miles, including the standard atmospheric refraction that bends the line of sight a little past the geometric edge — at 9 ft of eye height the horizon is about 3.5 nm off — together with the dip, how far below true horizontal that watery edge lies (≈ 0.97′·√h), the correction subtracted from a sextant altitude shot to the sea horizon. The geographic-range endpoint gives how far off a light or landmark first peeps over the horizon = the sum of two horizon distances, your own plus the object's: 1.169·(√h_eye + √h_object), so a 100 ft lighthouse from a 9 ft cockpit lifts above the sea at about 15 nm — purely geometric, before the light's own luminous range and the visibility. The object-height endpoint inverts it: how tall a tower, light or headland must stand to break the horizon at a target range, or how close you must be before a known landmark appears. Everything is computed locally and deterministically, so it is instant and private. Ideal for marine-navigation and chartplotter apps, coastal-pilotage and lighthouse tools, and sailing utilities. Pure local computation — no key, no third-party service, instant. Geometric/refraction model. 3 compute endpoints. For great-circle distance use a geo-distance API; for set & drift a set-and-drift API.
api.oanor.com/horizon-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Ship Stability API?
What's the rate limit for Ship Stability API?
How much does Ship Stability API cost?
Can I cancel my subscription anytime?
Is Ship Stability 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/shipstability-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/shipstability-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/shipstability-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/shipstability-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.