> For the complete documentation index, see [llms.txt](https://docs.scicrunch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scicrunch.io/elasticsearch-metadata-services/resource-information-network-rin-services/the-rrid-resolver.md).

# The RRID Resolver

Information about RRID resolver

## Introduction

The RRID resolver provides the ability to resolve an RRID without the need for an API key. The resolver by default returns information in a structured report.  In addition, results can be retrieved in JSON format.

For example the resolver page for a software tool (fMRIPrep) can be resolved via the following URL: <https://scicrunch.org/resolver/RRID:SCR_016216>

<figure><img src="https://2664757529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIFPUklTpgWYMOYnZkrEP%2Fuploads%2FHAmki564TlQfXtYjw68f%2Fimage.png?alt=media&amp;token=70bc6f21-fcf2-4402-ae21-6f70639db025" alt=""><figcaption><p>RRID Resolver Report</p></figcaption></figure>

## Retrieving JSON Metadata for an RRID

## Use the RRID resolver to return metadata in JSON format

<mark style="color:blue;">`GET`</mark> `https://scicrunch.org/resolver/{RRID}.json`

#### Path Parameters

| Name                                   | Type   | Description             |
| -------------------------------------- | ------ | ----------------------- |
| RRID<mark style="color:red;">\*</mark> | String | The RRID being resolved |

{% tabs %}
{% tab title="200: OK RRID Found" %}

{% endtab %}

{% tab title="404: Not Found RRID Not Found" %}

{% endtab %}
{% endtabs %}


---

# 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://docs.scicrunch.io/elasticsearch-metadata-services/resource-information-network-rin-services/the-rrid-resolver.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.