docs: Update best practices for PPE Actors and mention negative profit#2770
docs: Update best practices for PPE Actors and mention negative profit#2770szaganek wants to merge 6 commits into
Conversation
szaganek
added
documentation
|
✅ Preview for this PR (commit |
lisvrijsen
left a comment
lisvrijsen
left a comment
There was a problem hiding this comment.
Looks and reads really good. Huge improvement!
What do you think about explicitly stating that the developer should test their Actor with an invalid input? Just charging for an invalid input doesn't necessarily cover the entire platform cost. If the Actor takes 10 min to handle the invalid input, and it charges for 1 event only, then the cost is still a lot higher.
stetizu1
left a comment
stetizu1
left a comment
There was a problem hiding this comment.
Sorry I did not say which comments are actually important and which are nits (the most important are the ones that I see something factual is confusing)
- and in some you do have the information that I was missing, it is just more down the document. In these cases, maybe add a link. Thanks.
| - AI/MCP compatibility | ||
| - Predictable user costs | ||
| - Store discounts | ||
| - Standard 20% commission |
There was a problem hiding this comment.
Not sure if this is actually the benefit, but I see it was presented like that 😅
| Limit the number of events. Fewer events make it easier for users to understand your pricing and predict the costs. | ||
|
|
||
| For Actors that produce data, events should map to something concrete in the user's dataset or storage. | ||
| Avoid cases where producing a single result triggers too many events. It makes your Actor more expensive. |
There was a problem hiding this comment.
Hmm, this goes against our google maps scraper 😅 Do we want to present this? It seems like common knowledge.
There was a problem hiding this comment.
Don't underestimate people 🥲
5 participants
Preview: https://pr-2770.preview.docs.apify.com/actors/publishing/monetize/pay-per-event
Closes #2634.