canonical: https://jentic.com/apis/nasa.gov/nasa-techport # Nasa Gov TechPort Jentic publishes the only available OpenAPI specification for the NASA TechPort API, keeping it validated and agent-ready. TechPort is NASA's repository of detailed information on agency-funded technology development projects, including project descriptions, technology areas, work locations, partners, and benefits. The API exposes three GET endpoints that let agents discover the full project list, retrieve metadata for a single project, and query the API root for service metadata. Responses are available in JSON or XML via the {.format} path segment. ## For AI agents Search NASA's repository of funded technology projects and retrieve detailed project metadata via three read-only endpoints. ## Scope Does not handle satellite imagery, asteroid tracking, or astronomical observation data - use for NASA TechPort project metadata only. ## Capabilities - Browse the full list of NASA-funded technology development projects with identifiers and titles - Retrieve full project detail including description, technology areas, partners, and benefits - Choose JSON or XML response formats by setting the {.format} path segment - Query the API root to discover available endpoints and the current service version - Filter project lists in client code by technology area, lead organisation, or work location ## Use cases ### NASA Technology Discovery for Researchers Researchers and grant writers explore NASA-funded technology development to spot collaboration opportunities or build on prior work. Calling GET /api/projects.json returns the master list, and GET /api/projects/{id}.json fetches each project's full description, technology area, lead centre, and partners. The flow needs no authentication so it is well suited to public-facing research tools. Example prompt: Call GET /api/projects.json and filter the returned list for projects whose technology area matches 'TX01 Propulsion Systems', then GET /api/projects/{id}.json for each match. ### Technology Trend Analysis Policy analysts and journalists use TechPort to chart NASA's investment across technology areas year over year. By aggregating /api/projects/{id} responses across the project corpus, an analyst can produce charts of project counts and budgets per technology area. Because the data is open, all analysis happens client-side after a small set of API calls. Example prompt: Iterate the project list, GET /api/projects/{id}.json for each, and group counts by technology area for a 5-year trend chart. ### Public Sector Innovation Catalogue Innovation directories at universities and federal contractors mirror or surface NASA TechPort entries to highlight collaboration opportunities. The simple GET-only API makes it easy to schedule a daily sync that pulls the project list, retrieves full detail for any new IDs, and updates a local catalogue. No auth means no key rotation overhead in a public-sector deployment. Example prompt: Daily, GET /api/projects.json, diff the project IDs against the local mirror, and GET /api/projects/{id}.json for any new IDs to populate the local catalogue. ### AI Agent NASA Research Assistant An AI research assistant invoked through Jentic answers natural-language questions like 'show me NASA projects working on lunar habitats'. The agent searches Jentic for the matching TechPort operation, executes it without any credential setup (TechPort needs no auth), and summarises the structured response into a human-readable list with citations back to NASA TechPort URLs. Example prompt: Search Jentic for 'list nasa technology projects', load GET /api/projects.json, execute it, and summarise projects whose title mentions 'lunar' for the user. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /api/projects{.format} | List NASA TechPort projects (JSON or XML) | | GET | /api/projects/{id}{.format} | Retrieve detailed metadata for a single project | | GET | /api | Service root metadata | ## Key resources - **Projects** — List all TechPort projects and retrieve detail for a specific project ID - **API root** — Service metadata endpoint exposing available routes and versioning ## Why Jentic - **Setup:** Wiring NASA TechPort by hand still means learning its {.format} path convention across the techport.nasa.gov host and handling errors on every project lookup, even with no key to manage. Through Jentic you install once, import TechPort from the API Directory, and your agent calls it. - **Permission scoping:** TechPort puts the project id in the URL path (/api/projects/{id}), so a rule can pin your agent to one project or the read-only project listing. All operations here are reads, so the agent retrieves project metadata and nothing that changes state. - **Credential handling:** TechPort needs no credential, so there is nothing to store: your own Jentic One instance still mediates each call at execution time. No secret ever enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'list NASA technology projects' or 'fetch a TechPort project detail', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **NASA APOD** — Astronomy Picture of the Day metadata feed - **SpaceX API** — Open SpaceX launches, capsules, and rocket data - **Data.gov API** — US government open data catalogue ## FAQ ### Why is there no official OpenAPI spec for NASA TechPort? NASA does not publish an OpenAPI specification for TechPort. Jentic generates and maintains this spec so that AI agents and developers can call TechPort via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the TechPort API use? TechPort is open and requires no authentication. All three endpoints accept anonymous GET requests. When called through Jentic, no vault credential is needed; the agent simply loads the operation and executes it. ### How do I retrieve detailed information about a specific TechPort project? Call GET /api/projects/{id}{.format} with the project ID and a desired format suffix such as .json. The response includes title, description, technology areas, lead centre, partners, and project benefits - the same fields shown on the TechPort web UI. ### Can I get TechPort responses in XML? Yes. The {.format} path segment supports both .json and .xml. For example, GET /api/projects.xml returns the project list in XML, useful for legacy pipelines that consume XML feeds rather than JSON. ### What are the rate limits for the TechPort API? TechPort does not publish formal rate limits in the spec. Because the data changes infrequently (NASA project records update on agency cycles, not real time), agents should cache responses for hours rather than re-querying on every user request. ### How do I list NASA TechPort projects through Jentic? Run jentic.search('list nasa technology projects'), load the GET /api/projects{.format} operation, then jentic.execute with format='.json'. Jentic returns the structured project list and the agent can iterate the IDs to fetch detail with GET /api/projects/{id}.json. ### Can I limit what my agent is allowed to do with the NASA TechPort API? Yes. Because you run Jentic One yourself, your own rules decide which TechPort operations and inputs the agent may use at execution time. Every TechPort endpoint is read-only, so an agent can list projects with GET /api/projects or fetch detail with GET /api/projects/{id} but can never change any data. Since the project id sits in the URL path, you can restrict an agent to a single project or only the read-only project listing.