No Man's Glyphs API for developers and partners

No Man's Glyphs has a two-way API: read No Man's Sky systems, regions and glyph addresses, or send your own data to be archived. Keys on request, on Discord.

Is there a No Man's Glyphs API?

Yes, and it works both ways.

Read: everything you see on this site comes out of an API: star systems, regions, portal addresses, galaxy maps, 3D scenes, search.
Write: your catalogue, your bot, or your save parser can send what it finds, and it joins the atlas.

There is no sign-up form and no paid plan. You ask on the Discord, you explain what you are making, and we sort it out together.

Send your data, we archive it

This is the part that matters most. No Man's Glyphs is an atlas of the No Man's Sky universe, and an atlas only grows with what travellers bring back. If you hold No Man's Sky data, the API can take it in.

Hubs and civilizations: your catalogue of systems, kept in sync instead of copied by hand.
Save parsers and tools: the systems and planets your users discover, sent as they find them.
Bots: the glyph codes your community posts every day.
Old spreadsheets and dead wikis: years of records that would otherwise disappear.

What you send is archived the way it should be:

Reviewed before it is published, like every contribution. See Contributing.
Dated and sourced: each record keeps when it was made and where it came from.
Credited: your project, and your contributors if they wish, are named on what they charted. A contributor can ask for their name to be removed at any time.
Never silently overwritten: when a game update changes a place, the earlier reading is kept as a historical record, not deleted. See Why an archive.
Never sold, never used for ads or tracking. See Privacy.

Your format is fine. Tell us what you have, we adapt the door to it, not the other way around.

Who it is for

Developers: a website, an app, a save parser, a spreadsheet, a research project on the No Man's Sky universe.
Discord bots: answer a glyph code with the system behind it, and pass new finds back to the atlas.
Community hubs and civilizations: keep your records next to the shared atlas, and safe beyond the life of your own site.
Researchers and archaeogamers: study the galaxy as data, see Why an archive.

What data you can read

Star systems: name, galaxy, region, portal glyph address, star class, economy, conflict, dominant lifeform, and what the community recorded about them.
Regions: name, coordinates, and the systems they hold.
Portal addresses: any 12-glyph code read back into a galaxy position, and the other way around.
The 256 galaxies: names, types, maps of quadrants, sectors, blocks and cubes.
Predicted systems: what can be computed from the coordinates alone, for systems nobody has written down yet. Predicted values are always labelled as such, never mixed with recorded ones.
Search: by name, by traits, or in plain words.

Every answer is JSON. Addresses use the same form as the site: {galaxy}-{portal code}, for example 1-111111111111 in Euclid. See Use direct URL and Glyphs.

Get an API key

Join the Discord.
Say what you are building, whether you want to read, send, or both, and which galaxies you need.
You get a personal key, sent privately.

A key is free. It is tied to one project, comes with a request rate agreed together, and can be revoked if it leaks or is abused. Keep it out of public repositories and out of browser code.

The documentation comes with the key. A bot can fetch only what changed since its last run, no need to download everything again.

Need something custom?

If no existing route fits, ask. A custom endpoint can be made for a real project, in either direction: a compact answer for a bot, a feed of the systems recorded in one galaxy, a door that accepts the export your tool already writes.

Say what the tool needs, not how the API should look: the answer is shaped around your use.

Please do not scrape

The pages are meant for people. Scripts that crawl system pages one by one get slowed down, then blocked for a while (HTTP 429), and they read HTML that can change at any time.

If you already parse the site, a key is the better way: faster answers, stable JSON, and a rate that matches what you actually need. Always send a User-Agent that names your project.

Ground rules

Credit the source: link back to No Man's Glyphs where the data is shown. Recorded systems were charted by players, see Sources.
Keep predictions labelled: a predicted value is not a recorded one, do not present it as confirmed.
Send what you may share: data you collected or were given to pass on, no personal data about other players.
No resale of the data as such.
Privacy first: the API exposes no personal data, and a key is never used to track you. See Privacy.

FAQ

Is the No Man's Glyphs API free? Yes, both ways. No fee, no ads, no paid tier.

Can I send my own No Man's Sky data? Yes, that is the point. Systems, regions, glyph addresses, a whole catalogue: it is reviewed, credited and archived. See Send your data, we archive it.

What if my own site or wiki closes one day? What you sent stays in the archive, with its date and its source.

Is there an official No Man's Sky API from Hello Games? No. No Man's Glyphs is a fan-made project, not affiliated with Hello Games.

Which galaxies are covered? All 256, from Euclid to Odyalutai. See the galaxies.

How fast will I get a key? It is a one-person project, so by hand and not instantly, but every request is read.

Questions, ideas, a catalogue to bring in: join the Discord.

Last updated: 1 November 2026