Nlr Gov NLR API
★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring ObservabilityapiKey3 EndpointsREST
For Agents
Authenticate via /auth/token and read regulatory resource records from the NLR catalog through /resources and /resources/{id}.
Use for: I need to retrieve a regulatory resource record from NLR, Get an access token from the NLR API, List all available NLR resources, Look up a specific NLR resource by its id
Not supported: Does not handle license filing, inspection scheduling, or enforcement action submission — use for read-only NLR resource catalog access only.
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.
Install Jentic One Beta
Connect the NLR API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NLR API, 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.
1
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 | sh2
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 instanceJentic 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 NLR API.
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
Patterns agents use NLR API for, with concrete tasks.
★ 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.
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.
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.
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.
Use Jentic to search 'list nlr regulatory resources', load /resources, and execute it to retrieve the first page of entries
Key Endpoints
3 endpoints — jentic publishes the only available openapi specification for nlr api, keeping it validated and agent-ready.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The NLR X-API-Key is held in the Jentic vault. Token issuance via /auth/token is performed transparently and the resulting bearer is attached to subsequent calls without passing through the agent context.
Intent-based discovery
Agents search by intent (e.g. 'fetch an nlr resource by id') and Jentic returns the matching /resources or /resources/{id} operation with its parameter schema, eliminating manual reading of the NLR developer portal.
Time to first call
Direct integration: half a day to handle X-API-Key exchange, token refresh, and pagination. Through Jentic: under 30 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using NLR API through Jentic.
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 at https://app.jentic.com/sign-up.
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.
GET STARTED