Flying height from line and angle
API · /kite-api
Kite Flying API
Kite-flying maths as an API, computed locally and deterministically — the line-pull, altitude and minimum-wind numbers a kite flyer, festival organiser or kite app works a flight out with. The line-pull endpoint gives the tension a kite puts on the line ≈ ½ × air density × wind speed² × sail area × a force coefficient (~0.8 for a typical flat or delta kite): because it rises with the square of the wind, doubling the wind quadruples the pull — a 1.5 m² kite holds about 47 N (nearly 5 kgf) at 8 m/s but four times that in a strong blow, so the line and your grip must be sized to the gusts, not the average. The altitude endpoint gives the flying height = the line let out × the sine of the line angle above the horizontal, with the downwind distance from the cosine: 100 m of line at a 45° angle reaches about 71 m up and 71 m downwind, while a heavy or under-flown kite sags to a low angle and never climbs. The min-wind endpoint gives the lightest wind that lifts off, where the aerodynamic lift just equals the weight: min wind = √(2 × mass × g ÷ (air density × area × lift coefficient)), so a 200 g, 1.5 m² kite needs only about 1.6 m/s (6 km/h) — lighter sails and bigger area drop the threshold. Everything is computed locally and deterministically, so it is instant and private. Ideal for kite-flying and festival apps, hobby and STEM-education tools, and outdoor calculators. Pure local computation — no key, no third-party service, instant. Flat-kite estimates — combine with real wind readings. 3 compute endpoints. For drag and terminal velocity use a drag API; for structural wind load a wind-load API.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 79 ms
- Server probes · 24h
- Subscribers
- 3,784
- active
- Total calls
- 4
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 5,900 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 5,900 calls/month
- 2 req/sec
- Line pull + altitude + min wind
- No credit card
Starter
€6.40 /month
- 53,000 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 53,000 calls/month
- 6 req/sec
- Gust pull & lift-off threshold
- Email support
Pro
€21.80 /month
- 237,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 237,000 calls/month
- 15 req/sec
- Festival & app pipelines
- Priority support
Mega
€70.50 /month
- 1,075,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 1,075,000 calls/month
- 40 req/sec
- Platform & catalogue scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Slackline Tension API
Tensioned-line point-load statics as an API, computed locally and deterministically — the line-tension and anchor-force numbers a slackliner, highliner or rigger works out before they weight a line. This is the V a loaded line makes under a person, not a self-weight catenary: the tension endpoint takes the span, the sag and the body load and returns the line tension and the horizontal anchor pull, because vertical balance is 2·T·sin(angle) = the body weight — so the flatter the line (the smaller the sag) the more the tension blows up, which is exactly why drum-tightening a line to kill the bounce can load the anchors to many times body weight. The sag endpoint inverts it: from a known line tension it returns the sag a mid-span load settles to (sin angle = weight ÷ twice the tension), and flags when the tension is too low to hold the load at all. The off-centre-load endpoint handles standing away from the middle, where the two halves carry different tensions: the horizontal pull is equal on both sides (H = weight × a × b ÷ (sag × span)) but the shorter, steeper segment runs at the higher tension and fails first — the reason a highliner near an anchor stresses that leash harder than one in the centre. Everything is computed locally and deterministically, so it is instant and private. Ideal for slackline and highline rigging tools, climbing and outdoor-gear apps, and tension-and-anchor calculators. Pure local computation — no key, no third-party service, instant. Geometric statics — combine with the real webbing and anchor ratings. 3 compute endpoints. For a self-weight hanging cable use a catenary API; for working-load-limit and safety factor a rigging API.
api.oanor.com/slackline-api
Fishing Tackle API
Angling and tackle maths as an API, computed locally and deterministically — the three numbers that decide how a reel is spooled and a lure is fished. The line-capacity endpoint works out how much line of a different diameter a reel will hold: line lies on the spool by cross-sectional area, so capacity scales with the inverse square of diameter — a reel rated for 100 yards of 0.30 mm holds about 73.5 yards of thicker 0.35 mm, or nearly 140 yards of a thinner 0.011-inch braid. The sink-time endpoint gives the countdown to fish a lure at depth: time = depth ÷ sink rate, so a minnow that sinks a foot a second reaches ten feet on a count of ten. The drag endpoint sets the reel: about 25–33 % of the line's breaking strength measured at the rod tip — a 20-pound line wants roughly 5 to 6.6 pounds of drag, enough to let a fish run before anything snaps. Everything is computed locally and deterministically, so it is instant and private. Ideal for fishing and tackle apps, reel-spooling and gear-shop tools, angler trip-planners, and learning sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Unit-agnostic — keep your units consistent; rules of thumb, conditions vary.
api.oanor.com/fishing-api
Climbing Fall API
Rock-climbing fall maths as an API, computed locally and deterministically — the safety numbers behind a lead fall, from the harshness of the catch to whether you hit the deck. The fall-factor endpoint gives the fall factor, distance fallen ÷ rope paid out, from 0 to a maximum of 2: it, not the absolute distance, decides how hard the catch is, so 4 metres on 2 metres of rope is a brutal factor-2 onto the anchor while the same fall on 10 metres of rope is a mild 0.4. The impact-force endpoint gives the peak force the rope transmits from the spring model F = mg + √((mg)² + 2·mg·k·f), where k is the rope modulus (~20 kN for a dynamic single rope) and f the fall factor — so an 80 kg climber on a factor-1 fall feels about 6.4 kN, and the top runner sees roughly 1.66× that from the pulley effect. The ground-fall endpoint adds it up: total drop = twice the height above the last piece, plus slack, plus the rope's stretch, and tells you whether that clears the ground or a ledge. Everything is computed locally and deterministically, so it is instant and private. Ideal for climbing apps, gym and guiding tools, route-planning and education sites, and gear calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Educational estimates — not a substitute for instruction and judgement.
api.oanor.com/climbing-api
Hammock Hang API
Hammock-hang maths as an API, computed locally and deterministically — the suspension-force, ridgeline and strap-height numbers a camper or hammock hanger sets up by. It all comes back to the 30-degree rule. The force endpoint shows why: the tension in each suspension line is the occupant weight ÷ (2 × sin of the hang angle), so at a 30° hang each strap carries about one body weight, but flatten the hang to 15° and it jumps to roughly 1.9 times — which is what over-stresses straps, trees and your back when people pull a hammock drum-tight. The ridgeline endpoint sizes a structural ridgeline at about 83 % of the hammock length, the fixed line that reproduces that ~30° lay and the right sag on any pair of trees. The strapheight endpoint estimates how high to attach the straps from the distance between the trees and the seat height you want, since trees farther apart need higher anchor points to hold the angle. Everything is computed locally and deterministically, so it is instant and private. Ideal for camping, backpacking, outdoor-gear and hammock app developers, hang-calculator and trip-planning tools, and adventure software. Pure local computation — no key, no third-party service, instant. Weight and lengths in your own unit. Live, nothing stored. 3 compute endpoints.
api.oanor.com/hammock-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Kite Flying API?
What's the rate limit for Kite Flying API?
How much does Kite Flying API cost?
Can I cancel my subscription anytime?
Is Kite Flying 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/kite-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/kite-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/kite-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/kite-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.