> For the complete documentation index, see [llms.txt](https://docs.sylvera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sylvera.com/carbon-markets/carbon-markets/ratings.md).

# Ratings

Independent assessments of carbon credit quality across the full project lifecycle—from pre-issuance ratings to issuing and beyond.

Sylvera Ratings help carbon markets function by giving participants transparent, independent insight into project quality. Quality varies significantly across the market, adding complexity and holding back scale and adoption. By giving participants a common, objective language for comparing carbon credits across standards and methodologies, our Ratings highlight risk and build confidence in the credits behind every deal.

Sylvera’s Ratings are **independent assessments**, not self-reported scores. Sylvera analysts apply the framework to each project using their own data collection and analysis. The rating is Sylvera’s view, not the project developer’s or the registry’s.

### Who uses Sylvera Ratings today?

* **Carbon credit buyers** use Ratings to compare projects, set minimum quality thresholds for procurement, and justify purchasing decisions to internal stakeholders.
* **Investors** use Ratings to screen portfolios, monitor credit quality over time, and price permanence and additionality risk.
* **Project developers** use Ratings to benchmark their projects, identify weaknesses before going to market, and demonstrate quality to potential buyers.

## User Guides

Explore our range of Ratings Products and how to interpret them.

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3>Full Rating</h3></td><td>Our most rigorous due diligence product, built to support purchase and investment decisions.<br></td><td><a href="/carbon-markets/carbon-markets/ratings/full-ratings.md">Full Ratings</a></td></tr><tr><td><h3>Estimated Rating</h3></td><td>Our lighter-touch due diligence product, built to support prioritization and triage of projects within a portfolio.</td><td><a href="/carbon-markets/carbon-markets/ratings/estimated-ratings.md">Estimated Ratings</a></td></tr></tbody></table>

## Technical Documentation

Deep dive into methodology and project type specific approaches

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Project Type Frameworks</td><td><a href="/carbon-markets/carbon-markets/ratings/technical-documentation/project-type-frameworks.md">Project Type Frameworks</a></td></tr><tr><td>Rating Methodology</td><td><a href="/carbon-markets/carbon-markets/ratings/technical-documentation/rating-methodology.md">Rating Methodology</a></td></tr></tbody></table>


---

# 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.sylvera.com/carbon-markets/carbon-markets/ratings.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.
