> 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/actualizacion-del-calculo-del-deposito.md).
# Actualización del cálculo del depósito
Comprende la actualización del cálculo del depósito para revendedores de DataImpulse. Aprende cómo se calculan los depósitos para tus subusuarios y cómo funciona la facturación para revendedores.
Hemos introducido un sistema basado en coeficientes para gestionar con precisión los depósitos entre diferentes pools proxy.
Anteriormente, los cálculos de depósito solo se aplicaban al pool residencial. Con la adición de los pools Mobile y Datacenter, ahora están en vigor los siguientes coeficientes:
Residential: x1
Datacenter: x0.5
Mobile: x2
Premium Residential: x5
**Proceso de depósito**
El proceso de depósito permanece sin cambios:
Un depósito de $50 proporciona 50 GB de tráfico.
La fijación de precios personalizada continúa funcionando como se definió previamente.
**Asignación a subusuarios**
Cuando los revendedores asignan tráfico a sus subusuarios, el saldo se deduce según la siguiente lógica:
***Residential Pool:***
Request: 10 GB
Deduction: $10 GB from reseller balance
***Datacenter Pool:***
Request: 10 GB
Deduction: $5 GB from reseller balance
***Mobile Pool:***
Request: 10 GB
Deduction: $20 GB from reseller balance
***Residential Premium Pool:***
Request: 10 GB
Deduction: $50 GB from reseller balance
---
# 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.dataimpulse.com/dataimpulse-documentation-es/revendedores/actualizacion-del-calculo-del-deposito.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.