docs: exclude pay per event + usage Actors from agentic payment eligibility - #2872
Draft
marcel-rbro wants to merge 1 commit into
Draft
docs: exclude pay per event + usage Actors from agentic payment eligibility#2872marcel-rbro wants to merge 1 commit into
marcel-rbro wants to merge 1 commit into
Conversation
…bility Actors that pass platform usage costs on to users are not eligible for agentic payments, but the criteria lists did not say so. Add the missing criterion to the x402, Skyfire, and monetization pages.
Contributor
|
✅ Preview for this PR (commit |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Actors with the Pay per event + usage option switched on aren't eligible for agentic payments, but none of the eligibility lists said so, so Actor developers kept hitting it unexpectedly. Adds the missing criterion to the x402, Skyfire, and monetization pages.
One open question for reviewers: the x402 page now documents the prepaid-token flow, where the resulting token behaves like a regular API token. If the pricing-model and Standby restrictions don't apply on that path, the Supported Actors section on that page needs a rewrite rather than an extra bullet - happy to handle that as a follow-up.