> For the complete documentation index, see [llms.txt](https://docs.learncard.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.learncard.com/build/go-to-production/verify-my-issuer.md).

# Get Listed as a Trusted Issuer

Add your organization's DID to the LEF Trusted Issuer Registry so recipients see a verified issuer.

The LEF Member Trusted Issuer Registry is the list LearnCard checks to decide whether an issuer is known. Listed issuers show as trusted in the LearnCard app instead of triggering an unverified-issuer notice, and listing also unlocks features reserved for registry members, such as sending credentials to phone numbers.

{% hint style="info" %}
**\~10 min** · You have a GitHub account and your organization's DID.
{% endhint %}

## What to prepare

* **Official name** of your organization
* **Website URL**
* **Location** (City, State/Region, Country)
* **Issuing DID** (e.g., `did:web:yourdomain.com` or `did:key:z...`)
* **Description** of your organization and its credentialing role
* **Governance URL** (optional) linking to your credentialing practices
* **Contact person** (GitHub username or email)

## Add your entry

1. **Fork and edit:** Open [registry.json](https://github.com/learningeconomy/LearnCard/blob/main/packages/learn-card-registries/trusted/registry.json) on GitHub and click the pencil icon to fork and edit the file.
2. **Add your entry:** Insert your organization into the `registry` object (preferably in alphabetical order by DID). The key must be your exact issuing DID.

   ```json
   "did:web:yourneworg.com": {
       "name": "My New Organization",
       "location": "New City, New Country",
       "url": "https://yourneworg.com/"
   }
   ```

   *(Don't forget to add a comma after the preceding entry if yours is not last, and validate your JSON before committing.)*
3. **Open a PR:** Commit your changes to a new branch and open a pull request against `learningeconomy/LearnCard`. Include your description, governance URL, and contact info in the PR description. (See GitHub's [pull request guide](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) if you need help.)

## What happens next

1. **Review:** The Learning Economy Foundation team reviews the PR and may request clarification.
2. **Merge:** Approved submissions are merged into the `main` branch.
3. **Propagation:** Applications and services will recognize your DID as a trusted issuer once they fetch the latest registry version.

## Troubleshooting

| If…              | Then                                                                                                                   |
| ---------------- | ---------------------------------------------------------------------------------------------------------------------- |
| `Invalid JSON`   | Use a JSON validator to ensure you haven't missed any commas or quotes.                                                |
| `Merge conflict` | Another organization may have added an entry at the same time. Pull the latest `main` branch and resolve the conflict. |
| `PR checks fail` | Ensure your entry follows the exact schema required (DID as key, object with `name`, `location`, `url`).               |


---

# 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.learncard.com/build/go-to-production/verify-my-issuer.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.