Nasa, worked by an AI employee
Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Nasa account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.
- Developer Tools
- Connects with a key
- 12 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What Nasa is
NASA offers a suite of APIs providing access to a wide range of data, including Earth science, planetary imagery, and technology transfer information.
You paste in a key from your own Nasa account. It is kept encrypted, and you can withdraw it from inside Nasa whenever you like.
One message in, the work done in Nasa.
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in Nasa. You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own Nasa account, inside the access you granted it, doing the thing you asked for.
- 04
It reports back
It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.
What it can do in Nasa
These are the ready-made tools your AI employee already has in Nasa. It is not limited to them, but it never has to be taught these.
- Get CMR CollectionsTool to retrieve collections from the common metadata repository (cmr). use when you need to search nasa science data collections by spatial, temporal, or metadata filters. call af
- Get CMR GranulesTool to retrieve granules from the common metadata repository (cmr). use when you need granule metadata filtered by collection ids, spatial, or temporal criteria. call after confir
- Get EONET CategoriesTool to retrieve a list of all event categories from eonet. use when you need current category ids, titles, descriptions, and info links.
- Get EONET Events (ATOM)Tool to retrieve a list of natural events in atom format. use when you need a machine-readable xml feed of recent natural events from eonet.
- Get EONET Events RSSTool to retrieve a list of natural events in rss format. use when you need the latest eonet events as an rss feed.
- Get EONET LayersTool to retrieve available data layers for event visualization. use after confirming category id if filtering.
- GET EONET MagnitudesTool to retrieve a list of available event magnitudes and their descriptions. use after determining you need valid magnitude filters before querying events data.
- GET EONET Source by IDTool to retrieve details for a specific eonet event source by id. use when you need to fetch source metadata (id, title, homepage) before querying events.
- Get EONET SourcesTool to retrieve a list of event sources. use when you need to enumerate available sources before querying events.
- Get Mars Rover PhotosTool to fetch photos taken by a specified mars rover on a given martian sol. use after selecting rover and sol.
- Search Near Earth ObjectsTool to search near-earth objects by closest approach date range. use when identifying asteroids in a date window (max 7 days).
- Search SVS VisualizationsTool to search for visualizations in the scientific visualization studio (svs). use when you need to query svs visualizations by keywords or mission filters.
You stay the boss of your Nasa account.
Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.
How we handle your data- It signs in to your own Nasa account. You are not moving anything into ours.
- You grant access one app at a time, and you can take it back the same way.
- Everything it does in Nasa is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in Nasa and the rest of your software in the same job
A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.
Questions people ask about Nasa
- Can an AI employee really work inside Nasa?
- Yes. It signs in to your own Nasa account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
- Do I have to move anything out of Nasa?
- No. Nothing moves and nothing is replaced. Your records stay in Nasa, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
- How does it get into my Nasa account?
- You paste in a key from your own Nasa account. It is kept encrypted, and you can withdraw it from inside Nasa whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
- What can it actually do in Nasa?
- It has 12 ready-made tools in Nasa today, among them Get CMR Collections, Get CMR Granules and Get EONET Categories. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use Nasa and the rest of my software in the same job?
- Yes, and that is usually the point. Reading a message in one app, checking a record in Nasa and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
- Who decides what it is allowed to do in Nasa?
- You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Nasa is written down with what it did and when.