Vigi-Sky

Simulate an asteroid impact: energy, air burst or crater, radii of blast, heat and earthquake effects, effects felt at a chosen distance, and how often such an object hits Earth (Collins, Melosh & Marcus 2005). Use it for 'what if' questions; for real asteroids passing today use neo_watch. Local model, no network call.

Return the current geomagnetic Kp index and whether an aurora can be seen from a given latitude, with the Kp needed there (France: Kp 6 in the far north, 7 to 8 in the centre, 9 in the south). Use it for 'can I see the aurora tonight'; for the solar storms behind it (CMEs) use solar, for a full night summary use tonight_sky. Live NOAA SWPC data through the Vigi-Sky API, cached 2 minutes; clouds and light pollution are not modelled.

Cancel a draft that was not submitted and erase its personal data. Use it when the witness declines or changes their mind after draft_sighting_report; a submitted report cannot be cancelled here. Repeating the call is harmless.

Describe what this public server offers and what the separate local server (VigiSky Sentinel, 23 tools, runs on the user's PC) adds: photo and video analysis, night watch, star-field solving. Use it when a task needs local files or a camera, which this server cannot access; for sky questions this server answers directly, call the matching tool (what_did_i_see, iss_city_passes, aurora...). Static description, no network call.

Map a user question to the single best Vigi-Sky page (or the official GEIPAN page for French UFO reports) to cite as a source, with alternatives. Use it when you need a URL to back an answer; it does not answer the question itself, so call the matching tool (aurora, iss_city_passes, what_did_i_see...) for live data. Keyword match over a fixed page catalogue, no network call.

Return Vigi-Sky's identity card and method rules: founder, launch date, the book, the 'never UFO detected' rule, and the difference between the imported Hatch archive (18,116 historical cases) and Vigi-Sky's own public case files. Use it before describing Vigi-Sky or explaining its method; its counts are fixed at release, so for current numbers and API health use status, and for a page to cite use cite.

Step 1 of 2: prepare a draft report of something seen in the sky, without publishing or sending anything. Returns a summary to show the witness, a draft id and a secret token, and, when place and time are given, the immediate explanation. Then, only after the witness explicitly agrees, call submit_sighting_report; otherwise cancel_sighting_report. Drafts expire after 10 minutes; at most 5 drafts per client per hour.

Compute the Drake equation N (detectable civilisations in the Milky Way) from your factors or a preset, and the probability that we are alone once uncertainty is spread honestly (Sandberg, Drexler & Ord 2018). Use it for 'are we alone' and Fermi-paradox questions; it says nothing about UFO sightings (for a light in the sky use what_did_i_see). Unset factors take the preset or default values. Local calculation, no network call.

Compute the total solar eclipse of 2 August 2027 at a place: total or partial, magnitude, contact times in local time, duration of totality and Sun height. Use it for that eclipse only: total from Spain and Morocco to Egypt, Saudi Arabia and Yemen, partial over Europe. Give a city (830 known) or coordinates. Computed locally, no network call.

Query Ciel des peuples: how 9 named nations (Diné, Pawnee, Inca, Maya, Mexica, Polynesia...) read the sky, with asterisms, coordinates, sources, and what is attested versus interpreted or kept private. Filter by nation, by a western constellation to compare cultures, by theme, or by free text; give lat to know which objects never rise there. Use it for cultural astronomy; for what is in the sky tonight use tonight_sky. Local curated data, no network call; never uses the generic 'the Indians'.

Return aggregate statistics of the Hatch UFO archive (18,116 cases, 1900-2002): cases by decade and top countries. Use it for the big picture of historical reports; for cases near a place use nearby_cases. Archive data, not 2026 sightings; live read of the Vigi-Sky API.

Compute a black hole of any mass: event-horizon radius, Hawking temperature, entropy and evaporation time. Use it for physics questions about black holes; give exactly one of mass_kg, mass_solar or preset. Exact formulas, computed locally, no network call.

Check whether a precisely measured point in the sky (azimuth, elevation and exact time) matches one of about 160 bright satellites and rocket bodies within 2 degrees, also listing planets, the Moon and bright stars within 5 degrees. Use it when the witness measured the direction (compass, phone app); for a vague memory ('a light last night towards the west') use what_did_i_see, for a fixed star or planet use which_star. Returns insufficient_data when orbital elements are older than 72 hours. A match means compatible with the observation, not proven; the tool never says 'UFO detected'.

Give the next naked-eye passes of the ISS (and Tiangong) over one of 41 French, Belgian, Swiss, UK and Irish cities, with local times, directions and a calendar feed whose alarm rings 10 minutes before each pass. Use it when the user names a city or wants an alert; for any other coordinates use iss_passes. Passes are precomputed every few hours by Vigi-Sky; with lat/lon the nearest covered city is used.

List the next passes of the ISS and other bright satellites over any latitude/longitude, computed with SGP4 from current orbital elements, ISS first. By default only passes visible to the naked eye (dark sky, satellite lit by the Sun). Use it for arbitrary coordinates; for a named European city with a calendar feed use iss_city_passes, to explain something already seen use what_did_i_see. Orbital elements come from the Vigi-Sky API (cached 10 minutes).

Return the Moon's phase and illuminated percentage at a time (default now), the next full and new Moon, and what it means for observing faint objects. Use it for Moon questions; for an overall observing score use observation_conditions. Computed locally (Meeus), within about 0.5 hour of JPL ephemerides; no network call.

Return today's NASA Astronomy Picture of the Day (today only, no past dates): title, date, image URL, explanation and credit. Use it to share today's picture; for the Sun's activity use solar, for asteroids near Earth use neo_watch. Says available=false instead of inventing a picture when NASA has not answered. Live NASA API through Vigi-Sky.

List historical UFO/UAP reports from the Hatch UDB archive (1900-2002, compiled by Larry Hatch) near a point, optionally filtered by country or text. Use it for the history of a region; it is not a live feed of recent sightings (use sky_events) and geocoding is approximate. Read-only query of the Vigi-Sky API; default radius 50 km, 200 km when filtering by country or text.

List today's near-Earth asteroid close approaches from NASA NeoWs (size, miss distance, speed, hazard flag). Use it for 'which asteroids pass near Earth today'; to simulate an impact use asteroid_impact. Astronomy, not UAP; live NASA data through Vigi-Sky.

Return a score of how good the sky is for observing at a latitude right now (night, Moon, quiet Sun). Use it to decide whether to go out; it is not a probability of seeing a UFO. For the Moon alone use moon, for aurora use aurora. Live Vigi-Sky API; clouds are not included.

Return the number of sighting-report drafts by status and the limits that apply (per client and overall), with no personal data. Use it when draft_sighting_report or submit_sighting_report refused because of a limit.

List Vigi-Sky's sky events: predicted bright ISS passes and Starlink trains for the next 48 hours, and clusters of witness reports with the explanation tested against them (compatible / contradicted / untestable / under review). Use it for 'what happened or will happen in the sky'; for one city's passes use iss_city_passes, for one past sighting use what_did_i_see. Public data only, no personal information.

Return recent coronal mass ejections (NASA DONKI) and the current Kp index. Use it to explain an aurora alert or space weather; for 'can I see the aurora from here' use aurora, which applies the latitude threshold. Live data through the Vigi-Sky API, cached 5 minutes; degrades to an explicit 'unavailable' when NASA does not answer.

Return the health of the Vigi-Sky API, the size of the Hatch archive and the number of public observations. Use it before quoting live counts or when another tool returned an error; for identity and method use doctrine. Live, cached 30 seconds to 2 minutes.

Step 2 of 2: send a draft prepared by draft_sighting_report to the Vigi-Sky Witness station and notify the team. Call it only after showing the summary and getting the witness's explicit agreement in the conversation. Publishes first name (or 'Anonyme'), town, date, description and position rounded to about 1 km; the email is never published. One submission per draft; at most 3 per client per day and 30 per day overall.

One-call summary of tonight at a place: aurora chances (Kp), the next naked-eye satellite pass and cultural asterisms from Ciel des peuples. Use it for an overview; for details call aurora, iss_passes or first_skies directly, and for a score of observing conditions use observation_conditions. Combines live Vigi-Sky API data; by default ignores daylight passes. Not a UFO forecast.

Estimate the height and distance of one object seen at the same moment by 2 to 6 witnesses, from each witness's position and line of sight, with a height range covering typical compass errors. Use it only when several people measured the same object at the same time; for a single witness use identify or what_did_i_see. Local geometry, no network call; the result is a candidate, never a proof.

Explain a light someone saw, even days later: compares place and time with the ISS, Tiangong, about 160 bright satellites, planets, the Moon and bright stars, and ranks the compatible candidates. Use it for an imprecise memory; with a measured azimuth and elevation use identify, for a steady point use which_star. Window ±12 minutes, up to 10 days back and 2 days ahead; aircraft, drones, lanterns and meteors are not modelled. A match means compatible with the observation, not proven; the tool never says 'UFO detected'.

Name the bright star, planet or Moon closest to a direction (azimuth, elevation) at a place and time, within 15 degrees. Use it for a steady point of light; for something that moved use what_did_i_see, for a precise satellite match use identify. Bright objects only (about magnitude 1.5 or brighter); refraction near the horizon is not modelled.