# Unregister

In the initial research phase of an NRN integration, it is very likely that we will test an architecture setup that does not work that well. As such, it is advised that game studios unregister their architecture to remove any unused architectures/clutter.

To unregister, admins only need to provide the `architectureId` as an input.

{% hint style="info" %}
Developers can unregister their models in a no-code environment on our [dashboard](https://arcagents.ai)
{% endhint %}

## Javascript

As mentioned in the register section, there is currently no GUI for registration, so admins will have to execute code as follows to unregister a model architecture:

```javascript
const { Registry } = require('nrn-agents');

Registry.setApiKey("my-admin-api-key");
const registry = new Registry("my-game-id");

await registry.unregister("my-first-model)
```

## Unity

To unregister, admins will need to add the "Registration" component as defined [here](/admin/register.md#unity).

At the bottom of the component, admins will be able to enter the `architectureId` of the model architecture that they wish to remove.

<figure><img src="/files/36nD1nY2CZcEanA0Dq5o" alt="" width="326"><figcaption></figcaption></figure>

## Unreal

Not yet implemented. The NRN team will handle unregistering for the time being.

{% hint style="danger" %}
Unregistering active model architectures may break existing pipelines. Always ensure no current models are running on an architecture that you plan on unregistering.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nrnagents.ai/admin/unregister.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.