# Credential URIs

## What are LearnCard URIs?

The LearnCard URI is a [URI](https://en.wikipedia.org/wiki/Uniform_Resource_Identifier) that allows a Universal Wallet to resolve a credential. It is freely extensible and any plugin can add to it in any way. However standard plugins will adhere to a format of `lc:${method}:${location}`. For example, the Ceramic plugin adds `lc:ceramic:${streamID}` URI support.

## Why use LearnCard URIs?

Verifiable Credentials need to be stored somewhere. LearnCard does not dictate *where* they can be stored. So, *LearnCard URIs* (often referred to as just URIs) were devised to be able to seamlessly retrieve credentials that can be stored anywhere a plugin allows

## When would I use a LearnCard URI?

For the most part, URIs get used by Read, Store, and Index Control Planes. Basically, Verifiable Credentials are converted into a URI by the Store Plane, saved in the holder's list with the Index Plane, then later read from the holder's list and resolved back into a Credential with the Read Plane.

However, URIs can also be very useful whenever you need to transport a credential and you know that LearnCard is being used, such as between your own networked systems.

## How can I use URIs?

Simply use `lc.store.upload` to convert a Verifiable Credential into a URI that you can then do things with, such as store and send. To get the Verifiable Credential back, use `lc.read.get` on the URI.


---

# 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.learncard.com/core-concepts/credentials-and-data/uris.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.