docs: exclude pay per event + usage Actors from agentic payment eligibility - #2872
Draft
marcel-rbro wants to merge 2 commits into
Draft
docs: exclude pay per event + usage Actors from agentic payment eligibility#2872marcel-rbro wants to merge 2 commits into
marcel-rbro wants to merge 2 commits 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 |
The eligibility list was duplicated verbatim on three pages and was missing two criteria, so developers hit ineligibility unexpectedly. - Add the KYC requirement. Without identity verification, none of a developer's Actors are eligible, regardless of pricing model. - Drop the stale "Standby support is coming later" sentence. - Replace the three copies of the list with a shared partial, so the next change to the criteria only has to be made once. Closes #2892 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Closes #2892
The agentic payments eligibility criteria were incomplete and duplicated verbatim on three pages, so Actor developers kept hitting ineligibility unexpectedly.
What changed
sources/_partials/_agentic-payments-eligibility.mdx, replacing the three verbatim copies (x402, Skyfire, monetization), so the next change to the criteria only has to be made once.Each page keeps its own lead-in sentence. The KYC criterion is phrased as a separate sentence rather than a bullet, because it's a property of the developer, not of the Actor.
Verified locally
pnpm buildpasses; the partial renders on all three pages and the#verify-your-identityanchor resolves..mdoutput flattens the partial correctly on all three pages - no duplication or misattached content.markdownlintclean; Vale reports 0 errors and 0 warnings on the new partial.Open question for reviewers (carried over, still unresolved)
The x402 page 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 a shared criteria list - happy to handle that as a follow-up.