docs(agentic-payments): improve docs about x402 and Skyfire payment providers#2622
Open
stepskop wants to merge 3 commits into
Open
docs(agentic-payments): improve docs about x402 and Skyfire payment providers#2622stepskop wants to merge 3 commits into
stepskop wants to merge 3 commits into
Conversation
- x402: document accessing run/storage with the existing PAYMENT-SIGNATURE - API auth reference: mention agentic payments (x402, Skyfire) - Skyfire: discover payment requirements via X-APIFY-PAYMENT-PROTOCOL header - Drop redundant protocol header once a payment header is present (inferred) - Unify Supported Actors section across x402 and Skyfire - Document allowsAgenticUsers eligibility criteria in monetization docs
stepskop
requested review from
fnesveda,
janbuchar and
marcel-rbro
as code owners
github-actions
Bot
added
the
t-core-services
Contributor
|
✅ Preview for this PR (commit |
stepskop
changed the title
stepskop
commented
Jun 8, 2026
|
|
||
| - Use the [pay per event](/platform/actors/publishing/monetize/pay-per-event) pricing model. Rental and pay-per-usage Actors are not supported. | ||
| - Run with [limited permissions](/platform/actors/development/permissions). Actors that request full permissions are excluded. | ||
| - Not rely on [Standby](/platform/actors/running/standby) mode for now. Standby support is coming soon. |
Contributor
Author
There was a problem hiding this comment.
This is a bummer. We don't want to bring Actor Standby down. Any better ideas? cc @raethlo
stepskop
changed the title
marcel-rbro
requested changes
Jun 11, 2026
| "https://api.apify.com/v2/datasets/<datasetId>/items" | ||
| ``` | ||
|
|
||
| ## Supported Actors |
Contributor
There was a problem hiding this comment.
Suggested change
| ## Supported Actors | |
| ### Supported Actors |
This can be an H3, same as in Skyfire docs.
| To be eligible for agentic payments, your Actor must: | ||
|
|
||
| - Use the [pay per event](/platform/actors/publishing/monetize/pay-per-event) pricing model. Rental and pay-per-usage Actors are not supported. | ||
| - Run with [limited permissions](/platform/actors/development/permissions). Actors that request full permissions are excluded. |
Contributor
There was a problem hiding this comment.
Is limited permissions required? Cause it's not mentioned anywhere on the pages for the specific methods.
Comment on lines
11
to
15
| :::caution Experimental feature | ||
|
|
||
| Agentic payments are experimental and may change as payment protocols evolve. Only Actors with the [Pay Per Event](/platform/actors/publishing/monetize/pay-per-event) pricing model are supported. [Standby](/platform/actors/running/standby) Actors are not supported. | ||
|
|
||
| ::: |
Contributor
There was a problem hiding this comment.
Do we still want to keep this note? We're already mentioning x402 elsewhere in the docs. The info could be moved to the section about supported Actors.
|
|
||
| ## Make your Actor eligible for agentic payments | ||
|
|
||
| [Agentic payments](/platform/integrations/x402) let AI agents discover, run, and pay for your Actor without an Apify account, using protocols such as [x402](/platform/integrations/x402) and [Skyfire](/platform/integrations/skyfire). Eligible Actors are flagged with `allowsAgenticUsers=true` and surface in agentic discovery, for example when [searching the store via API](https://docs.apify.com/api/v2#/reference/store/store-actors-collection/get-list-of-actors-in-store) with `allowsAgenticUsers=true`. |
Contributor
There was a problem hiding this comment.
The first link is generic for Agentic payments, but only links to x402. I'd just not use a link here as the links to x402 and skyfire are there later in the text.
|
|
||
| - Use the [pay per event](/platform/actors/publishing/monetize/pay-per-event) pricing model. Rental and pay-per-usage Actors are not supported. | ||
| - Run with [limited permissions](/platform/actors/development/permissions). Actors that request full permissions are excluded. | ||
| - Not use [Standby](/platform/actors/running/standby) mode for now. Standby support is coming soon. |
Contributor
There was a problem hiding this comment.
Suggested change
| - Not use [Standby](/platform/actors/running/standby) mode for now. Standby support is coming soon. | |
| - Not use [Standby](/platform/actors/running/standby) mode for now. Standby support is coming later. |
Just to be sure
| ```bash | ||
| curl -si \ | ||
| -H 'X-APIFY-PAYMENT-PROTOCOL: SKYFIRE' \ | ||
| 'https://api.apify.com/v2/actors/ACTOR_ID/run-sync' |
Contributor
There was a problem hiding this comment.
x402 uses run-sync-get-dataset-items, here's run-sync. Is that correct?
Contributor
|
Just keep in mind that #2618 will probably be merged before this PR and touches the same documentation. |
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
4 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.
Improves docs around agentic payments (x402 and Skyfire), addressing several issues:
allowsAgenticUsers=trueeligibility criteria in the monetization docs (reported in Slack)/storeendpoint usingallowsAgenticUsers=trueparameter)X-APIFY-PAYMENT-PROTOCOLneeded once a payment header is present).