Hey- we built Notte for legitimate workflows like testing and approved automation; not abuse. Like other session provider tools (Browserbase, Hyperbrowser, Anchor, etc.), we encourage respecting site terms and robots.txt, and we’re adding built-in support for it soon to enforce this policy inside Notte.
You should also support Web Bot Auth and make it required to have a customer-specific abuse contact in the user-agent header so that people can send invoices to those customers for when your customers cause downtime due to excessive scraping.
Yes, that’s a very good point! We’ll look into this for SDK usage. What do you recommend for the public repo where it's harder to enforce runtime headers?
Hey- we built Notte for legitimate workflows like testing and approved automation; not abuse. Like other session provider tools (Browserbase, Hyperbrowser, Anchor, etc.), we encourage respecting site terms and robots.txt, and we’re adding built-in support for it soon to enforce this policy inside Notte.
You should also support Web Bot Auth and make it required to have a customer-specific abuse contact in the user-agent header so that people can send invoices to those customers for when your customers cause downtime due to excessive scraping.
Yes, that’s a very good point! We’ll look into this for SDK usage. What do you recommend for the public repo where it's harder to enforce runtime headers?
No compliance? No support.
The pricing page was higher in priority
We added the pricing breakdown here: https://www.notte.cc/#pricing