> 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/excel-add-in/fields.md). # Fields Every field you can request in SYL.DATA, SYL.TABLE, SYL.BY\_REF, and SYL.LIST Field names aren't case-sensitive. Combine any number with commas: `"Name,Rating,Country"`. The last column shows which functions accept the field. Fields marked **DATA only** need a separate lookup for each project, so they're available in `SYL.DATA`, the **Add columns** button, Enrich, and Screen, but not in table functions such as `SYL.TABLE`. ## Project | Field | Description | Functions | | -------------------- | ------------------------------------------- | --------- | | Registry | The registry the project is listed on | All | | Project ID | The project's ID on that registry | All | | Name | Project name | All | | Project category | Broadest grouping, for example Nature-based | All | | Project type | For example REDD+, ARR, IFM, or Cookstoves | All | | Project subtype | The most detailed grouping | All | | Avoidance or Removal | Avoidance, Removal, or Mixed | All | | Description | The project's description | All | ## Rating | Field | Description | Functions | | ----------------------- | ------------------------------------------------------------------------------------------------------------ | --------- | | Rating | The project's Sylvera Rating, for example AA or (p)BB. "Not assessed" when it has none | All | | Estimated rating | The range for a project with an Estimated Rating, for example A–BB. Blank when the project has a Full Rating | DATA only | | Assessed on | Date of the latest Rating or review | All | | On watch | TRUE when the project is On Watch | All | | Assessment type | The type of Rating | All | | Additionality score | Additionality score | All | | Carbon accounting score | Carbon Accounting score | All | | Permanence score | Permanence score | All | | Co-benefits score | Co-Benefits score | All | | Previous rating | The Rating before the latest change. "No rating change" when there's been none | DATA only | | Rating changed on | Date of the latest Rating change | DATA only | ## Price | Field | Description | Functions | | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | | Latest price | Latest Sylvera price estimate in USD per credit. Uses the newest vintage unless you give a vintage year as the last argument of `SYL.DATA`. See [SYL.DATA](/excel-add-in/functions.md) for examples | DATA only | | Vintage | The vintage the price is for. Added automatically after Latest price when you insert from the pane or ribbon | DATA only | ## Credit volumes With a vintage, these return that vintage's figure. Without one, they return the project total. | Field | Description | Functions | | --------------------------- | ------------------------------------------------ | --------- | | Issued credits | Credits issued | DATA only | | Retired credits | Credits retired | DATA only | | Cancelled credits | Credits cancelled | DATA only | | Permitted credits | Credits permitted | DATA only | | CORSIA CP1 eligible credits | Issued credits eligible for CORSIA's first phase | DATA only | ## Project details | Field | Description | Functions | | ------------ | ---------------------------------------------------------- | --------- | | Country | Host country | DATA only | | Region | The host country's continent | DATA only | | Methodology | Full methodology name. Several are separated by semicolons | DATA only | | CCP labelled | TRUE when the project carries the ICVCM CCP label | DATA only | | CCB approved | TRUE when the project is CCB approved | DATA only | | Proponents | Project proponents | DATA only | | Developers | Project developers | DATA only | ## Links | Field | Description | Functions | | -------------------- | ------------------------------------------ | --------- | | Registry link | The project's page on its registry | All | | Sylvera catalog link | The project's page on the Sylvera platform | All | ## What the messages mean | Cell shows | Meaning | | -------------------------- | ------------------------------------------------------------------------------------------ | | Not assessed | Sylvera hasn't rated this project | | No data | Sylvera has no value for this, for example no price for that vintage | | No rating change | The project's Rating has never changed | | Not available on your plan | Your organization's plan doesn't include this field. Contact your Customer Success Manager | | Unknown field | The field name isn't recognized. The message lists the valid names | --- # 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/excel-add-in/fields.md?ask=&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.