> For the complete documentation index, see [llms.txt](https://docs.idlayr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idlayr.com/guides/all-guides.md). # All guides Each guide walks through a **complete, runnable integration** — not a pattern snippet. Reader leaves with a working build, including all the code, expected outcomes, edge cases, and common pitfalls. ## Getting started * [**Your first IDlayr API call**](/guides/your-first-api-call.md) — a five-minute cURL smoke test that verifies your credentials, OAuth2 flow, and a real API response. Use as a sanity check before integrating any product. ## Migration * [**Migrate from v0.x to v1**](/guides/migration.md) — what changed in v1, the product rename map, API and SDK breaking changes, the deprecation policy for legacy v0.x, and a suggested migration order. ## Cross-product * [**High-assurance signup with Eligibility, SIM Swap, and Secure SNA**](/guides/high-assurance-signup.md) — the most comprehensive integration. Gate with Eligibility, screen for fraud with SIM Swap, prove possession with Secure SNA. *** More guides — per-product recipes, fallback patterns, callback handling — are in the works. They'll appear here as they're finalised. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.idlayr.com/guides/all-guides.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.