That being said I think the emphasis on APIs might be wrong in the long term. I think having an intake agent sitting on a side channel apart from HTTP/HTML on your product waiting to interact with external agents might be a better analogy. Maybe using just a mix of free text and fixed schemas with access to the product tools, who knows. Really excited to see developments on this area.
This shows we need to build better approaches to agent interactions that are not at the level of "run a virtual browser", but that encodes much more of the workflows available than raw API's do today.
Netlify is forcing Starter team plan users to move to the new Free Plan
You choose the behavior that fits your usecase:
Free plan: no accidental bills, but your site may be suspended if you go over the limits. Starter plan: free as long as you stay under the limits, but you'll get billed for overages.
I spotted Little Workshop when I saw https://equinox.space/ on Hacker News and noticed it was running on Netlify. Loved the fluidness, speed and art direction of a game running directly in the browser and working smoothly on my phone.
Immediately thought of them when we started thinking about a 5 million developer celebration and reached out. Love the result :)
We're using them for deploy previews. Does anyone have recommendations on alternatives?
We've had a few open source plan since the early days and it's not going anywhere.
1. Would Netlify forgive the bill if this didn't go viral?
2. How do you plan to address this issue so that it never happens again?
Everyone here knew someone from Netlify would come and say OP wouldn't have to pay. That was a given. Now we want to know the important answers.
2. While I've always favored erring towards keeping people's sites up we are currently working on changing the default behavior to never let free sites incur overages
But, parsing documentation? And, believing it blindly? hah. Maybe ressurect Semantic web as well..
This shows we need to build better approaches to agent interactions that are not at the level of "run a virtual browser", but that encodes much more of the workflows available than raw API's do today.