Nasa Gov TechPort

Name: TechPort API
Brand: NASA TechPort
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsProject Managementnone3 EndpointsREST

Install Jentic One Beta

Connect the TechPort to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TechPort, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with TechPort API.

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

GET STARTED

Start building with TechPort API

Explore with Jentic

View OpenAPI Document

For Agents

Search NASA's repository of funded technology projects and retrieve detailed project metadata via three read-only endpoints.

Use for: List all NASA technology development projects in TechPort, Retrieve detailed metadata for a specific TechPort project ID, Search NASA-funded projects in a given technology area, I need to fetch the TechPort project list as JSON

Not supported: Does not handle satellite imagery, asteroid tracking, or astronomical observation data - use for NASA TechPort project metadata only.

Use Cases

Patterns agents use TechPort API for, with concrete tasks.

★ 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.

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.

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.

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.

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

3 endpoints — jentic publishes the only available openapi specification for the nasa techport api, keeping it validated and agent-ready.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using TechPort API through Jentic.

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.