> For the complete documentation index, see [llms.txt](https://docs.flycode.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flycode.com/docs/introduction.md). # Get started - [What is FlyCode?](https://docs.flycode.com/docs/introduction/what-is-flycode.md): What FlyCode is: AI failed payment recovery for Stripe, Shopify, Braintree and PayPal subscriptions, trained on Visa and Mastercard network data, priced on results. - [What causes failed payments and involuntary churn?](https://docs.flycode.com/docs/introduction/what-causes-payment-failures-and-involuntary-churn.md): The causes of failed subscription payments: insufficient funds, generic declines, outdated card credentials and issuer risk rules, and why most are recoverable. - [How teams handle failed payments before FlyCode](https://docs.flycode.com/docs/introduction/how-teams-handle-failed-payments-before-flycode.md): Why fixed retries and email-first dunning underperform: banks and card networks score each transaction differently, so one rule for every failure loses revenue. - [Involuntary churn and failed payments](https://docs.flycode.com/docs/introduction/involuntary-churn-and-failed-payments.md): Involuntary churn explained: how failed payments cancel paying customers, how much revenue it costs, and how FlyCode's recovery engine reduces it. - [Analyze your subscription churn (free report)](https://docs.flycode.com/docs/introduction/analyze-your-subscription-churn-free-report.md): Get a free failed payment audit: see which decline types cost you most, your current recovery rate, and how much smarter retry timing would recover. --- # 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.flycode.com/docs/introduction.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.