Update pricing details for Lit Actions

[GTC6244]

Clarified the pricing explanation for Lit Actions by adding details about the Base Lit Action Price and real-time pricing calculation.

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[Copilot]

Pull request overview

This PR updates the documentation for Lit Actions pricing by adding important clarification about how costs are calculated. The update explains that a "Base Lit Action Price" serves as a proxy for the average cost before execution, while the actual price is calculated in real-time during execution and billed upon completion.

Key Change:

• Enhanced explanation of Lit Actions pricing calculation by adding details about the Base Lit Action Price mechanism and the timing of price calculation and billing

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The term "real time" should be hyphenated as "real-time" to match the documentation convention used elsewhere in this file (line 10: "real-time prices") and throughout the codebase.

Suggested change

The total cost of a Lit Action is calculated by summing all applicable components based on your action's actual resource usage. Since every Lit Action can be unique, we've included a Base Lit Action Price, which acts as a proxy for the average of all Lit Action Prices, and helps the network account for incoming Lit Actions before they have been executed. Your **actual** price will be calculated in real time as your action is being executed and will be billed when the action is finished.

The total cost of a Lit Action is calculated by summing all applicable components based on your action's actual resource usage. Since every Lit Action can be unique, we've included a Base Lit Action Price, which acts as a proxy for the average of all Lit Action Prices, and helps the network account for incoming Lit Actions before they have been executed. Your **actual** price will be calculated in real-time as your action is being executed and will be billed when the action is finished.

[Copilot]

There are inconsistent spacing issues in this paragraph. After the first sentence ("...actual resource usage."), there are two spaces instead of one. After the second sentence ("...have been executed."), there are three spaces instead of one. Standard convention is to use one space after a period.

Suggested change

The total cost of a Lit Action is calculated by summing all applicable components based on your action's actual resource usage. Since every Lit Action can be unique, we've included a Base Lit Action Price, which acts as a proxy for the average of all Lit Action Prices, and helps the network account for incoming Lit Actions before they have been executed. Your **actual** price will be calculated in real time as your action is being executed and will be billed when the action is finished.

The total cost of a Lit Action is calculated by summing all applicable components based on your action's actual resource usage. Since every Lit Action can be unique, we've included a Base Lit Action Price, which acts as a proxy for the average of all Lit Action Prices, and helps the network account for incoming Lit Actions before they have been executed. Your **actual** price will be calculated in real time as your action is being executed and will be billed when the action is finished.

[glitch003]

So this is saying that they do pay two base prices? But one is charged even if the action doesn't get run?

I don't think we need to explain why we have a base price ("we've included a Base Lit Action Price, which acts as a proxy for the average of all Lit Action Prices")

I think we need to explain why there are two "base prices" for running an action, and that they'll be charged both, or what the difference is.

I don't know, it's just really confusing to have two "base prices" here. it seems like one is the "cost to start to run the action" (products.litAction cost) and the second is the "successful execution cost" (lit action component basePrice) and you do get charged for both. Is this framing incorrect? could we explain it more like this, so it's immediately clear what the difference is?

Like do we need some copy like this?

i.e. "All endpoints require paying the product price at the start of the request. Since Lit Actions can have variable costs, successful execution incurs the costs of all the runtime components including an additional lit action component basePrice"