> ## Documentation Index
> Fetch the complete documentation index at: https://develop.cotality.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Product lifecycle and status

> How Cotality labels product maturity — Alpha, Private preview beta, Public preview, and GA — and what each stage guarantees for stability, support, and production use.

## Why lifecycle labels exist

This portal spans mature GA data APIs and brand-new AI agents under active development.
Lifecycle labels set the correct expectation for **stability, support, and SLAs** before
you invest in an integration.

## The four phases

<CardGroup cols={2}>
  <Card title="Alpha" icon="flask-vial">
    First testable version, available for internal evaluation and select design-partner pilots.
    Known issues may exist. API contracts will change. Not for production use.
  </Card>

  <Card title="Private preview beta" icon="lock">
    Stable version for friendly early-adopter customers. Minimal breaking changes; requires
    explicit enablement by Cotality. Suitable for controlled production pilots.
  </Card>

  <Card title="Public preview" icon="eye">
    Feature-complete and open for public opt-in testing. Suitable for pre-production
    integrations. Performance and scale validation in progress.
  </Card>

  <Card title="GA — General availability" icon="circle-check">
    Official, fully supported, and enterprise-ready. Versioned with a deprecation window.
    Covered by standard SLAs. Safe for customer-facing production use.
  </Card>
</CardGroup>

## What each phase guarantees

| Phase                    | Breaking changes               | Support       | Production use         |
| ------------------------ | ------------------------------ | ------------- | ---------------------- |
| **Alpha**                | Any time, no notice            | Best-effort   | No                     |
| **Private Preview Beta** | With advance notice            | Standard      | Controlled pilots only |
| **Public Preview**       | Rare, coordinated              | Named contact | Pre-production         |
| **GA**                   | Versioned + deprecation window | Full SLA      | Yes                    |

## How status appears in the docs

Each product and solution page carries a status badge. When a page has no badge, treat the
capability as GA unless the page notes otherwise.

| Badge                                              | Color  | Meaning                                                      |
| -------------------------------------------------- | ------ | ------------------------------------------------------------ |
| <Badge color="purple">Alpha</Badge>                | Purple | Design-partner access only — do not build production systems |
| <Badge color="orange">Private Preview Beta</Badge> | Orange | Early-adopter pilots — stable but evolving                   |
| <Badge color="blue">Public Preview</Badge>         | Blue   | Pre-production safe — GA coming                              |
| <Badge color="green">GA</Badge>                    | Green  | Production-ready                                             |

## Current capability status

| Capability                                          | Status                              |
| --------------------------------------------------- | ----------------------------------- |
| Property Characteristics MCP                        | <Badge color="green">GA</Badge>     |
| Climate Risk Analytics MCP                          | <Badge color="green">GA</Badge>     |
| Market and Trend Analytics MCP                      | <Badge color="green">GA</Badge>     |
| CLIP Tools MCP                                      | <Badge color="green">GA</Badge>     |
| Valuation AI Agents (Appraisal, Vendor, Compliance) | <Badge color="purple">Alpha</Badge> |
| Credco EPC Credit MCP                               | <Badge color="purple">Alpha</Badge> |

## Versioning and deprecation

* GA APIs are versioned (e.g., `/v1/`). Breaking changes ship under a new version.
* Deprecations include a migration guide and a minimum advance-notice window.
* MCP tool names and schemas follow the same versioning discipline once a server reaches GA.

<Tip>
  For AI agents: pin to a specific API version in production and monitor the `messages`
  array in the [response envelope](/reference/response-envelope) — deprecation notices
  surface there before a breaking change ships.
</Tip>