> For the complete documentation index, see [llms.txt](https://docs.complycube.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.complycube.com/documentation/changelog/2022/16-january.md). # 16 Jan: Changelog Launch Our First Public Changelog. Product updates for proof of address beta, refreshed mobile SDKs, AML screening coverage, and migration and integration guides. We’re excited to launch this public changelog as the official source of product updates.\ While we’ve been shipping improvements for years, this page will now provide a clear, consolidated record of new features, enhancements, and documentation changes going forward. ### **New features** * Early access launch of [Proof of Address Checks](/documentation/product-guides/kyc-automation-services/proof-of-address-check.md) (beta) for selected partners. * Released revamped native iOS and Android Mobile SDKs. ### **Improvements** * Expanded AML Screening coverage to additional jurisdictions. * Improved error handling and standardized response codes across the API. ### **Documentation** * Published migration guides from API v1.5.0 → v1.6.0. * Added first set of SDK integration guides for iOS and Android. --- # 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.complycube.com/documentation/changelog/2022/16-january.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.