canonical: https://jentic.com/apis/nlr.gov/nlr

# Nlr Gov NLR API

Jentic publishes the only available OpenAPI specification for NLR API, keeping it validated and agent-ready. The NLR API is a small US-government developer endpoint exposing a token-issuing operation and a paginated /resources catalog with detail lookup by id. It is suitable for integrations that need authenticated read access to NLR's published resource records and bearer-token issuance. The current surface is intentionally narrow - three endpoints - and is tagged as nuclear regulatory data in the apis.json index.

## For AI agents

Authenticate via `/auth/token` and read regulatory resource records from the NLR catalog through /resources and `/resources/{id}.`

## Scope

Does not handle license filing, inspection scheduling, or enforcement action submission - use for read-only NLR resource catalog access only.

## Capabilities

- Issue a bearer token from `/auth/token` using a registered API key
- List the full set of NLR regulatory resource records with pagination
- Fetch a single resource record by id from `/resources/{id}`
- Filter or paginate /resources to retrieve catalog subsets
- Provide a structured fallback for agents that need authenticated access to NLR's developer endpoint

## Use cases

### Regulatory Data Sync

Compliance and risk teams need a programmatic feed of NLR-published resource records to keep internal systems aligned with federal source data. The /resources endpoint paginates the catalog and `/resources/{id}` returns the full record, so a nightly sync can detect new or changed entries without scraping. Authentication uses an X-API-Key header exchanged for a short-lived bearer token via `/auth/token.`

Example prompt: POST to `/auth/token` with the registered API key, then GET /resources with pagination params and persist each returned id

### Token Issuance Probe

Operations teams running multi-tenant integrations need to verify that NLR API keys still issue valid tokens before running larger workflows. A simple call to `/auth/token` confirms the key state and returns a fresh bearer token usable by downstream /resources calls. This makes `/auth/token` a reliable health-check entry point for NLR connectivity.

Example prompt: Call `/auth/token` with the X-API-Key header and assert the response contains a non-empty access_token field

### Targeted Resource Lookup

When a downstream system references an NLR record by id, the agent can resolve full metadata via `/resources/{id}` without paging the whole catalog. This is the lowest-cost path to enrich an internal record with the authoritative NLR copy. The lookup is a single GET keyed by the resource id.

Example prompt: Call GET `/resources/{id}` for a known resource id and return the full record body to the calling agent

### AI Agent Compliance Lookup

An agent answering compliance questions can call the NLR API through Jentic to retrieve canonical resource records without managing the X-API-Key directly. Jentic search resolves 'list nlr regulatory resources' to the /resources operation, loads the schema, and executes with credentials injected at call time. Token rotation through `/auth/token` is handled by the same flow.

Example prompt: Use Jentic to search 'list nlr regulatory resources', load /resources, and execute it to retrieve the first page of entries

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/auth/token` | Exchange an API key for a short-lived bearer token |
| GET | `/resources` | List NLR regulatory resource records |
| GET | `/resources/{id}` | Fetch a single NLR resource record by id |

## Key resources

- **Auth Token** — Issue a short-lived bearer token from a registered API key
- **Resources** — List and look up NLR regulatory resource records

## Why Jentic

- **Setup:** Wiring the NLR API by hand means running its token exchange, adding the API key to requests against its host (https://api.nlr.gov), and handling auth refresh yourself. Through Jentic you install once, import the NLR API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** NLR exposes a read-only resource catalog with the resource id in the path (`/resources/{id}`), so a rule can pin your agent to reading resources: it can list resources and fetch one by id and nothing else. You choose the operations it may call, so anything beyond catalog reads is not included unless you add it.
- **Credential handling:** Your NLR API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list NLR resources' or 'fetch a resource by id', and Jentic returns the matching NLR operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Data.gov API** — Data.gov aggregates federal datasets across agencies and complements NLR's narrow regulatory feed.
- **openFDA API** — openFDA is a similarly-shaped US-government developer endpoint exposing pharmaceutical and device records.
- **Census Bureau API** — Census Bureau exposes demographic and geographic data useful for siting and impact analysis alongside NLR records.

## FAQ

### Why is there no official OpenAPI spec for NLR API?

NLR does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call NLR API 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 NLR API use?

NLR uses an API key passed in the X-API-Key header. Calls to `/auth/token` exchange the key for a bearer token used by /resources and `/resources/{id}.` Through Jentic the X-API-Key is stored in the vault and never exposed to the agent.

### Can I list all available NLR resources with the NLR API?

Yes. GET /resources returns the catalog of NLR resource records with pagination. Use `/resources/{id}` for the full record body of a specific entry.

### What are the rate limits for the NLR API?

The OpenAPI spec does not declare specific rate limits. Treat the service as conservatively rate-limited typical of US-government developer endpoints, and let Jentic handle 429 backoff.

### How do I retrieve an NLR resource record through Jentic?

Run pip install jentic, search Jentic for 'fetch an nlr resource by id', load the `/resources/{id}` operation schema, supply the id, and execute. Jentic injects the API key and handles token issuance against `/auth/token.`

### Is the NLR API free to use?

The NLR API is a US government developer endpoint and access typically requires a free API key registered at developer.nlr.gov. Pricing is not declared in the spec; check the NLR developer portal for current terms.

### Can I limit what my agent is allowed to do with the NLR API?

Yes. Because you run Jentic One yourself, your own rules decide which NLR operations and credentials the agent may use. Since the NLR API is a read-only catalog, you can pin the agent to reading records only, so it may list entries with GET /resources and fetch one by id with GET `/resources/{id}` and nothing more. Any operation you do not grant, including token issuance through `/auth/token`, stays unavailable to the agent.