ForHosting KIT · Science

Exoplanet calculator

Around a star of one solar mass, a planet at 1 AU completes its orbit in 365.25 days. Enter the star's mass plus either the orbital period in days or the semi-major axis in AU, and get the missing one. Free in your browser.

  • Free
  • Runs in your browser
  • No sign-up
  • Your data stays on your device
Use it from WebAPIEmailTelegramApp soon
If you enter
Stellar mass
1
Semi major axis
1
You get
Period
365.25
Period years
1
Solved
period

Exoplanet catalogs quote an orbital period in days or a semi-major axis in astronomical units, but rarely both at once, and both still need the host star's mass before Kepler's third law closes. This calculator takes a positive stellar mass in solar masses plus exactly one orbital parameter — period in days or semi-major axis in AU — and returns the missing quantity under the standard two-body approximation that the planet is much lighter than the star. The identity is P squared equals a cubed over M when period is expressed in years, axis in AU, and mass in solar masses; days are converted with a Julian year of 365.25 days. Zero or negative stellar mass is rejected as invalid input rather than producing a nonsense orbit.

Kepler's third law for a planet around a star

Kepler's third law relates the time an object takes to complete one closed orbit to the size of that orbit and the mass that sits at the focus. For a planet whose mass is negligible compared with its host star, the convenient astronomical form is P_yr squared equals a_AU cubed divided by M_star, where P_yr is the period in Julian years of 365.25 days, a_AU is the semi-major axis in astronomical units, and M_star is the stellar mass in solar masses.

Rearranged, the period in days is 365.25 times the square root of a cubed over M, and the axis is the cube root of M times P_yr squared. That is exactly the identity this exoplanet calculator applies: you supply the star's mass and whichever orbital number you already know, and the missing number is filled in. A one-solar-mass star with a one-AU orbit recovers a 365.25-day year, which is the textbook sanity check every implementation should pass.

A three-and-a-half-day hot Jupiter around a sun-like star sits near 0.045 AU, which is the scale of the first transiting giants. The approximation drops the planet's own mass; for a Jupiter around a sun that correction is about one part in a thousand, far smaller than typical stellar-mass uncertainty from spectroscopy. Binary stars, circumbinary planets, and comparable-mass pairs belong to a two-mass Kepler solve, not this landing.

Where an exoplanet period–axis calculator earns its keep

Transit surveys such as Kepler, K2, TESS, and PLATO report orbital period in days almost immediately, while the physical separation in AU is what observers need for insolation, equilibrium temperature, and habitable-zone membership. Combining that period with a spectroscopic or isochrone stellar mass is the first Kepler step before a more expensive light-curve model. Radial-velocity teams often start from a period and a stellar mass to quote a minimum a before the eccentricity is fully constrained.

Classroom astrophysics courses assign the same identity with catalog rows — recover Earth's year from one AU and one solar mass, then invert a hot-Jupiter period — and they need an oracle that refuses a zero-mass star instead of returning NaN. Mission-planning notebooks that stack hypothetical planets around nearby bright stars use the same closed form to sketch inner working angles and angular separations. Failed validation does not consume balance.

Keep requests small, pin the rounded solutions in tests, and you get reproducible exoplanet orbits for homework, LMS plugins, and survey reduction without standing up an N-body integrator for a two-body massless-planet problem.

Transit period to physical axis

Convert a TESS or Kepler orbital period in days plus a spectroscopic stellar mass into a semi-major axis in AU for insolation and habitable-zone checks.

Classroom Kepler checks

Recover a 365.25-day year from one solar mass and one AU, then invert catalog hot-Jupiter periods, with zero stellar mass rejected as invalid input.

RV and mission sketching

Turn a radial-velocity period and host mass into an estimated axis, or sketch inner working angles for hypothetical planets around nearby bright stars.

How do I compute an exoplanet orbital period from stellar mass and axis?

The calculator returns period in days from P_yr = sqrt(a³ / M) with a Julian year of 365.25 days.

How do I compute the semi-major axis from period?

The axis in AU is the cube root of M times (period / 365.25) squared.

Why do I need the star's mass as well as the period?

Because Kepler's third law links period and orbit size only through the mass at the centre. The same period around a heavier star means a wider orbit, so a catalog period alone cannot give the distance in AU.

Can I use it for planets in binary star systems?

No. It treats the planet as much lighter than a single host star. Binary stars, planets that circle both stars of a pair and bodies of similar mass need a two-mass calculation instead.

How large is the error from ignoring the planet's own mass?

Very small for typical planets: for a Jupiter around a Sun-like star it is about one part in a thousand, far below the usual uncertainty in a stellar mass measured from spectra.

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

POSThttps://api.kit.forhosting.com/phys/exoplanet

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

curl -X POST https://api.kit.forhosting.com/phys/exoplanet \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"stellar_mass":1,"period":365.25}'
{
  "stellar_mass": 1,
  "period": 365.25
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "phys.exoplanet",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Kepler's third law for a planet around a star

Because the map is a handful of multiplies and a square root or cube root, the result is deterministic floating-point arithmetic with no random seeds, no wall-clock timestamps, and no outbound network: identical input always yields identical JSON, which is what goldens, widgets, and API clients all need.

What you send, what you get, and how errors are raised

Sending both orbital fields is rejected so a stale pair cannot silently overwrite the quantity you meant to solve. Sending neither is also rejected, because there is then nothing to compute. The same positivity rule applies to a supplied period or axis: an orbit with non-positive size or period is not a Kepler ellipse. Wire the free browser form for classroom demos and catalog spot-checks, then call the identical contract from scripts when you reduce a table of transit periods to axes. POST a JSON object with stellar_mass as a finite number of solar masses strictly greater than zero, plus exactly one of period in days or semi_major_axis in AU. Aliases are accepted in the solver: M, mass, m_star, and stellar_mass_msun for the star; P, period_days, and orbital_period for the period; a, sma, and semi_major_axis_au for the axis. Stellar mass that is zero, negative, missing, non-finite, or an empty string fails with invalid_input and a message that names stellar_mass; those failures are not billed. On success the body echoes stellar_mass, period in days, semi_major_axis in AU, and period_years in Julian years, plus solved set to period or semi_major_axis so clients know which field was computed, the formula string P_yr^2 = a_AU^3 / M_star, and method kepler_third_law_exoplanet. A one-solar-mass, one-AU request yields period 365.25 days and period_years 1; inverting that pair recovers the axis 1 AU. Successful API calls use the published base of $0.002 per item; validation failures do not consume prepaid balance.

Where an exoplanet period–axis calculator earns its keep

Because this capability is a pure parse engine, every successful call costs the published $0.002 base price with no model tokens and no outbound network.

What happens if stellar mass is zero or negative?

The task fails with invalid_input. Kepler's third law is undefined for a non-positive central mass, so the call is not billed and no orbit is returned.

Which units does the exoplanet calculator use?

Stellar mass is in solar masses, orbital period in days, and semi-major axis in astronomical units. period_years is also returned using a Julian year of 365.25 days.

What does the exoplanet calculator cost?

The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.

Read the full KIT documentation →