> For the complete documentation index, see [llms.txt](https://docs.dataimpulse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataimpulse.com/dataimpulse-documentation-es/revendedores.md). # Revendedores Documentación del programa de revendedores de DataImpulse. Aprende a configurar un negocio de proxies de marca blanca, gestionar subusuarios y configurar tu cuenta de revendedor. Para convertirse en revendedor de DataImpulse, simplemente cree una cuenta en nuestro [Dashboard](https://app.dataimpulse.com/). Complete el formulario Know Your Customer (KYC) a través de nuestro socio seguro iDenfy para verificar su identidad y garantizar el cumplimiento de las políticas de nuestra plataforma. Después de eso, firme el Reseller Agreement para activar su condición de revendedor. Después de configurar su cuenta, vaya a la sección Resellers para hacer un depósito de al menos $50 y activar su condición de revendedor. La Reseller API está disponible [aquí](https://documenter.getpostman.com/view/6095389/2s9YC7UC2x). Si necesita endpoints específicos que aún no se han implementado, comuníquese con nuestro Support Team para obtener ayuda. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.dataimpulse.com/dataimpulse-documentation-es/revendedores.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 `build a script that syncs our docs to a CMS` 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.