> For the complete documentation index, see [llms.txt](https://developer.kizen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.kizen.com/docs/apps-and-integrations/integrations/nipr.md).

# NIPR

Connect NIPR to Kizen to work with live NIPR data in real time. Build Agentic Workflows to look up producer NPNs from basic identifying information.

{% hint style="success" %}
**Audience:** Admins, Developers, Solution Architects

**Purpose:** Explains what the NIPR integration is, when to use it, and how it works within your <code class="expression">space.vars.automations</code>
{% endhint %}

## Overview

Connect NIPR to <code class="expression">space.vars.Kizen\_company\_name</code> with the NIPR integration. Look up the National Producer Number (NPN) for any insurance producer in the National Insurance Producer Registry and use this information in your <code class="expression">space.vars.automations</code> in <code class="expression">space.vars.Kizen\_company\_name</code>.

### What Is the NIPR Integration?

The NIPR integration adds the following action step to the <code class="expression">space.vars.automation</code> builder:

* **Lookup NPN:** Finds the NPN of the specified producer in NIPR

You configure the connection to the production environment in NIPR once, as an integration secret in <code class="expression">space.vars.Kizen\_company\_name</code>. The integration also supports a separate connection to the beta environment for testing, which you set up as a different integration secret. See [Set Up NIPR in Kizen](https://developer.kizen.com/docs/apps-and-integrations/integrations/nipr/set-up-nipr-in-kizen.md) for details.

### When to Use the NIPR Integration

Use the NIPR integration when you want to build <code class="expression">space.vars.automations</code> to access live NIPR data. If you need to ensure that every producer <code class="expression">space.vars.entity</code> in <code class="expression">space.vars.Kizen\_company\_name</code> has an up-to-date NPN, for example, this integration can help.

***

## How the NIPR Integration Works

Before you configure and use the NIPR integration, it's important to understand how it functions.

### Connection Model

To connect to NIPR from <code class="expression">space.vars.Kizen\_company\_name</code>, you must provide your own NIPR business account, which you must configure with API access to the services that the integration uses. Then, to access live NIPR data, you must have a valid API login to the NIPR production environment. If you prefer to build your <code class="expression">space.vars.automation</code> using test data first, you can set up a separate connection to NIPR's beta environment, which requires a different API login. <code class="expression">space.vars.Kizen\_company\_name</code> stores your login credentials for both environments as integration secrets in the Secret Manager.

The integration connects to NIPR at the business level. Therefore, every user in your <code class="expression">space.vars.Kizen\_company\_name</code> business who installs the integration can access the configured NIPR environment and run queries against NIPR databases. However, the integration only connects to one environment at a time. It can't connect to both simultaneously. You must manually configure the integration to query either production or beta from the app settings before you run your <code class="expression">space.vars.automation</code>. If you ever need to change environments, you must reconfigure the integration.

For more information on connecting to NIPR, see [Set Up NIPR in Kizen](https://developer.kizen.com/docs/apps-and-integrations/integrations/nipr/set-up-nipr-in-kizen.md).

### Authentication

NIPR authenticates you by your user name and password, not by OAuth or a similar protocol, so there's no API access token to refresh. If you change your password, you must update your integration secrets for the production and beta environments. Otherwise, the NIPR steps in your <code class="expression">space.vars.automations</code> fail.

For more information, see [Set Up NIPR in Kizen](https://developer.kizen.com/docs/apps-and-integrations/integrations/nipr/set-up-nipr-in-kizen.md).

### Fees

NIPR bills your account directly to run reports and set up alerts on their Producer Database (PDB) according to the pricing and terms in your NIPR agreement. However, NPN lookups in the production environment, including from the Lookup NPN action in this integration, and all requests on the beta environment are always free of charge.

### Rate Limits

NIPR doesn't impose rate limits on the APIs that the integration uses, and <code class="expression">space.vars.Kizen\_company\_name</code> doesn't throttle NIPR calls. Therefore, you shouldn't experience rate-limiting issues with the integration.

### Timeouts

Requests to NIPR time out after 20–30 seconds. NIPR steps in an <code class="expression">space.vars.automation</code> don't retry automatically, so a timeout or temporary NIPR outage causes the step to fail.

### Privacy

The integration doesn't log a producer's Social Security number or Taxpayer Identification Number if it uses this information to look up an NPN. Other methods of NPN lookup don't require a Social Security number or Taxpayer Identification Number at all.

For more information, see [Work with NIPR Data in an Agentic Workflow](https://developer.kizen.com/docs/apps-and-integrations/integrations/nipr/work-with-nipr-data-in-an-agentic-workflow.md).

***

## How to Use the NIPR Integration

For step-by-step instructions on using the NIPR integration, see the following topics:

* [Set Up NIPR in Kizen](https://developer.kizen.com/docs/apps-and-integrations/integrations/nipr/set-up-nipr-in-kizen.md)
* [Work with NIPR Data in an Agentic Workflow](https://developer.kizen.com/docs/apps-and-integrations/integrations/nipr/work-with-nipr-data-in-an-agentic-workflow.md)
* [Troubleshoot NIPR](https://developer.kizen.com/docs/apps-and-integrations/integrations/nipr/troubleshoot-nipr.md)

***

## What's Next

Continue to [Set Up NIPR in Kizen](https://developer.kizen.com/docs/apps-and-integrations/integrations/nipr/set-up-nipr-in-kizen.md) to configure the connection.&#x20;

<details>

<summary><strong>Related Topics</strong></summary>

* [Set Up NIPR in Kizen](https://developer.kizen.com/docs/apps-and-integrations/integrations/nipr/set-up-nipr-in-kizen.md)
* [Work with NIPR Data in an Agentic Workflow](https://developer.kizen.com/docs/apps-and-integrations/integrations/nipr/work-with-nipr-data-in-an-agentic-workflow.md)
* [Troubleshoot NIPR](https://developer.kizen.com/docs/apps-and-integrations/integrations/nipr/troubleshoot-nipr.md)

</details>

***

*NIPR is a trademark of the National Insurance Producer Registry. Kizen's NIPR integration is not affiliated with, endorsed by, or sponsored by the National Insurance Producer Registry.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.kizen.com/docs/apps-and-integrations/integrations/nipr.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
