> 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/es/introduction.md).

# Comenzar

- [¿Qué es FlyCode?](https://docs.flycode.com/docs/es/introduction/what-is-flycode.md): Qué es FlyCode: recuperación de pagos fallidos con IA para suscripciones de Stripe, Shopify, Braintree y PayPal, entrenada con datos de la red Visa y Mastercard, con precio basado en resultados.
- [¿Qué causa los pagos fallidos y el churn involuntario?](https://docs.flycode.com/docs/es/introduction/what-causes-payment-failures-and-involuntary-churn.md): Las causas de los pagos fallidos de suscripciones: fondos insuficientes, rechazos genéricos, credenciales de tarjeta desactualizadas y reglas de riesgo del emisor, y por qué la mayoría se pueden recuperar.
- [Cómo gestionan los equipos los pagos fallidos antes de FlyCode](https://docs.flycode.com/docs/es/introduction/how-teams-handle-failed-payments-before-flycode.md): Por qué los reintentos fijos y el dunning centrado primero en email rinden por debajo de lo esperado: los bancos y las redes de tarjetas califican cada transacción de forma distinta, así que una sola regla para cada fallo hace perder ingresos.
- [Churn involuntario y pagos fallidos](https://docs.flycode.com/docs/es/introduction/involuntary-churn-and-failed-payments.md): Explicación del churn involuntario: cómo los pagos fallidos cancelan a clientes que sí pagan, cuánto ingreso cuesta y cómo el motor de recuperación de FlyCode lo reduce.
- [Analiza tu churn de suscripción (informe gratuito)](https://docs.flycode.com/docs/es/introduction/analyze-your-subscription-churn-free-report.md): Obtén una auditoría gratuita de pagos fallidos: mira qué tipos de rechazo te cuestan más, tu tasa de recuperación actual y cuánto recuperaría un mejor momento de reintento.


---

# 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/es/introduction.md?ask=<question>&goal=<user_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.