Gnomon (style) angle
API · /sundial-api
Sundial API
Sundial gnomonics maths as an API, computed locally and deterministically — the hour-line, gnomon and longitude-correction numbers a dial maker, horologist or astronomy hobbyist lays a sundial out with. The hour-line-angle endpoint gives the angle of each hour line on the dial plate, measured from the noon line: for a horizontal dial tan(angle) = sin(latitude) × tan(hour angle), and for a vertical south-facing dial cos(latitude) is used instead, where the hour angle is 15° per hour from solar noon. At 50° latitude the 1-o'clock line sits about 11.6° from noon rather than 15° — the lines bunch near noon and spread toward the ends, which is exactly why a sundial's hours are unevenly spaced. The gnomon endpoint gives the style angle: the gnomon's shadow-casting edge must point at the celestial pole, so it rises at the latitude angle on a horizontal dial (50° at 50° N) and at 90° − latitude on a vertical dial — get this wrong and the dial keeps correct time at only one season. The longitude-correction endpoint converts the dial's local apparent time to clock time: 4 minutes of time per degree of longitude, correction = 4 × (reference meridian − local longitude), so a dial at 7.5° E on Central European Time reads 30 minutes slow versus the clock. Everything is computed locally and deterministically, so it is instant and private. Ideal for sundial-design and gnomonics tools, astronomy-education and maker apps, and horology calculators. Pure local computation — no key, no third-party service, instant. Add the equation of time for full clock accuracy. 3 compute endpoints. For the sun's position use a solar-position API; for sunrise and sunset a sunrise API.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 93 ms
- Server probes · 24h
- Subscribers
- 3,223
- active
- Total calls
- 12
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 7,050 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 7,050 calls/month
- 2 req/sec
- Hour lines + gnomon + longitude
- No credit card
Starter
€6.85 /month
- 59,500 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 59,500 calls/month
- 6 req/sec
- Horizontal & vertical dials
- Email support
Pro
€23.50 /month
- 246,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 246,000 calls/month
- 15 req/sec
- Dial-design & education pipelines
- Priority support
Mega
€72.80 /month
- 1,135,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 1,135,000 calls/month
- 40 req/sec
- Platform & catalogue scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Telescope Optics API
Telescope optics maths as an API, computed locally and deterministically — the magnification, exit-pupil and resolving-power numbers an amateur astronomer or stargazing-app developer picks gear and eyepieces with. The magnification endpoint gives magnification = the telescope's focal length ÷ the eyepiece focal length (a 1000 mm scope with a 10 mm eyepiece is 100×), the focal ratio, and — from the aperture — the useful range from about the aperture in mm ÷ 7 (lowest useful, a 7 mm exit pupil) up to roughly 2× the aperture in mm, beyond which the image only dims and blurs; pass an eyepiece apparent field and it returns the true field of view. The exit-pupil endpoint gives aperture ÷ magnification, the width of the light beam leaving the eyepiece — a big 4–7 mm exit pupil for bright wide views of nebulae, a small 0.5–2 mm for the Moon and planets at high power. The resolution endpoint gives the Dawes limit ≈ 116 ÷ aperture(mm) and the slightly stricter Rayleigh limit ≈ 138 ÷ aperture in arcseconds, plus the limiting magnitude ≈ 2.7 + 5·log₁₀(aperture mm) — bigger glass splits finer doubles and reaches fainter stars, though seeing usually caps real resolution near 1 arcsecond. Everything is computed locally and deterministically, so it is instant and private. Ideal for astronomy and stargazing apps, telescope-shop and eyepiece-calculator tools, and observing-planner utilities. Pure local computation — no key, no third-party service, instant. 3 compute endpoints. For camera/thin-lens imaging use a lens API; for stellar magnitudes a star-magnitude API.
api.oanor.com/telescope-api
Stellar Parallax API
Stellar-parallax and astrometry maths as an API, computed locally and deterministically. The distance endpoint turns a measured trigonometric parallax angle into a distance using d(pc) = 1/p(arcsec), accepting the parallax in arcseconds or milliarcseconds and returning the distance in parsecs, light-years and astronomical units — a parallax of one arcsecond is one parsec (≈3.2616 light-years) by definition, and Proxima Centauri’s 0.7687-arcsecond parallax gives about 1.30 pc, or 4.24 light-years. The parallax endpoint inverts it, p(arcsec) = 1/d(pc), giving the tiny annual back-and-forth angle a star traces against the background as Earth orbits the Sun. The proper-motion endpoint computes a star’s tangential (transverse) velocity across the sky from its proper motion and distance, v_t = 4.74047·μ(arcsec/yr)·d(pc) km/s — Barnard’s Star, with a proper motion of about 10.39 arcsec/yr at 1.83 pc, races across the sky at roughly 90 km/s. Everything is computed locally and deterministically, so it is instant and private. Ideal for astronomy, astrophysics, planetarium, education and science-communication app developers, star-distance and stellar-kinematics tools, and Gaia-catalogue post-processing. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is geometric distance and kinematics; for a star’s apparent and absolute brightness use a star-magnitude API.
api.oanor.com/parallax-api
Light Travel Time API
Light-travel-time astronomy maths as an API, computed locally and deterministically. The travel-time endpoint computes how long light takes to cross a distance, t = d/c with c = 299,792,458 m/s exactly, accepting the distance in metres, kilometres, miles, astronomical units, light-years, parsecs or light-seconds/minutes and returning the time in seconds, minutes, hours, days and years — light from the Sun reaches Earth in about 8.3 minutes and the nearest star is about 4.2 light-years away. The distance endpoint inverts the relation, d = c·t, to give how far light travels in a time, returning the distance in metres, kilometres, astronomical units, light-years and parsecs — one light-year is about 9.461×10¹⁵ m. The round-trip endpoint computes the one-way and round-trip communication delay to a target, d/c and 2·d/c, the light-speed latency that makes distant spacecraft control so slow and Mars rovers largely autonomous. Distance units include light-second and light-minute and time units run from seconds to years. Everything is computed locally and deterministically, so it is instant and private. Ideal for astronomy, space-mission, education, science-communication and simulation app developers, communication-delay and cosmic-distance tools, and physics teaching. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is light travel time; for an object's angular size use an angular-size API and for sidereal time a sidereal API.
api.oanor.com/lighttime-api
Angular Size API
Angular-size astronomy and optics maths as an API, computed locally and deterministically. The angular-size endpoint computes the angular diameter an object subtends, δ = 2·arctan(d/(2D)), from its physical size and its distance, returning the angle in radians, degrees, arcminutes and arcseconds, along with the small-angle approximation δ ≈ d/D — the Sun and Moon are each about half a degree (31 arcminutes) across. The distance endpoint inverts the relation, D = d/(2·tan(δ/2)), to give an object's distance from its known true size and its measured angular size, the basis of the standard-ruler distance method. The object-size endpoint computes an object's physical diameter, d = 2·D·tan(δ/2), from its distance and angular size. Size and distance use any one consistent unit, and angles may be given in radians, degrees, arcminutes or arcseconds. Everything is computed locally and deterministically, so it is instant and private. Ideal for astronomy, telescope, astrophotography, surveying and optics app developers, field-of-view and rangefinding tools, and physics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is angular size; for stellar magnitude and parallax distance use a star-magnitude API and for sidereal time a sidereal API.
api.oanor.com/angularsize-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Sundial API?
What's the rate limit for Sundial API?
How much does Sundial API cost?
Can I cancel my subscription anytime?
Is Sundial 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/sundial-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/sundial-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/sundial-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/sundial-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.