> For the complete documentation index, see [llms.txt](https://sub2.gitbook.io/sub2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sub2.gitbook.io/sub2/concepts/processors.md). # Processors Processors are what make sub2 subscriptions automatic. These are anyone who initiates a transaction processing payments of due subscriptions through the unrestricted `processPayment` function. As a reward, processors earn processing fees varying in size depending on the subscription and how far into the auction period it was processed. Three things go into determining whether a subscription is worth redeeming at a certain point in time: * the cost of calling `processPayment` in terms of network fees * the current income that is obtainable from calling `processPayment` * the overhead of running the processor (node/provider cost, hardware cost etc) Given that a subscription is created with a large enough `maxProcessingFee` to cover the costs, it can be assumed that it will be processed. As more processors search for profitable subscriptions to process, it is expected that the profit margin will diminish. For example, processor A could be willing to process a subscription at time `n`, but processor B is willing to take a smaller fee and process it at time `n-1`. This competition is healthy for the users of the protocol as they end up paying the *minimum* amount of fee that *any* processor is willing to take. --- # 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://sub2.gitbook.io/sub2/concepts/processors.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.