The promise of an agent browser is simple: open a page, name the outcome, and get on with your day. It should be useful in its first minute, not only after a new user has navigated a maze of model names, prices, and key screens.
Choice stays at the centre
Skylark is built around choice. You can bring your own API key from the provider you already trust, use a local model, or connect another compatible service. That does not change. A default should be a good place to begin, never a lock-in.
The first tab should prove the point
Skylark puts an agent on the page: it can work on the live tab, remember useful context, and keep every move visible. None of that matters if a new user has to make an infrastructure decision before they have seen a single useful result.
A default provider can make that first run coherent: a model suited to browser work, sensible limits, reliable availability, and a clear route to bring your own key later.
We are looking for a supporter
We would love to work with a provider that wants to support the project and be offered as Skylark’s default. The fit is straightforward: help people experience a capable browser agent without taking away their choice of provider.
If that sounds like your team, we would like to talk about what a useful default could look like together.