An agent that proves who it is.
The web is getting stricter about automation, and the industry's answer is not better disguises — it is verifiable identity. Browza signs its requests rather than hiding them.
- No credit card required
- Free plan to start
Why anonymous automation is a dead end
- Sites cannot tell a legitimate agent from an abusive one.
- So they block broadly, and legitimate work is collateral.
- Evasion is an arms race you re-run every quarter.
- There is no way to be trusted if you cannot be identified.
How Browza identifies itself
Signed, per request
Navigations carry an RFC 9421 Ed25519 signature naming Browza as the agent.
Verifiable by anyone
The public key is published at a well-known directory that signs itself.
Submitted for verification
Browza has applied to Cloudflare's verified-bot programme — identity is only worth having if verifiers accept it, so registration is part of the work, not an afterthought.
It grants nothing by itself
A site still decides. Where one refuses automated traffic, the run reports it plainly rather than forcing through.
How you'd call it
A goal and a schema over HTTP — no selectors to maintain and no browser fleet to run.
“Nothing to configure — signing is on by default, and can be disabled per run with config.webBotAuth if a site ever mishandles the headers.”
Questions people ask
Does this get me past bot protection?
Not by itself, and we won't claim otherwise. It lets sites that choose to admit accountable agents recognise Browza. A site that refuses all third-party agents still refuses us.
Does Browza try to look like a human browser?
This feature is the opposite of that. Browza declares what it is and proves it cryptographically.
Can I turn it off?
Yes, per run, though there is rarely a reason to — the signature is additive and inert on sites that don't check it.
Related use cases
What will you hand over?
Start with one task. Watch it run, take the wheel whenever you want, and keep the ones that earn their place.