Skip to main content
An agent opens a browser for one job only: the weekly walk of your own site. Once a week it visits your workspace’s domain the way a shopping assistant would and checks that it can get from your pricing to your signup form. What it checks and what it files are on Signup check. No agent opens a browser on anyone else’s site. Listings and profile updates on directories and review sites are filed by you, from a copy kit, and every site in the site policies table is copy_kit or stricter.

​
What the walk may do

  • Your own domain only: your workspace’s domain and its subdomains, over https. A link that leaves it is not followed.
  • Read only. Every step opens a page by its address. It never types into a field, ticks a box, presses a button or submits a form, and never signs in, creates an account or buys anything.
  • No bot-check workarounds. Every browser is started with CAPTCHA solving, stealth fingerprinting and proxies switched off. A CAPTCHA or bot check ends that step, and the walk reports it as a blocker.
  • Small and rare. One walk opens at most six pages, and the walk runs at most twice a day per workspace, whatever retries ask for.
The walk runs only while a live consent covers your domain. A person signed in to the app gives it; an API key or an MCP connection never can. A consent lasts 90 days. Without one, nothing opens, and the next step is yours: give or renew it under Settings › Autonomy. Nobody at Attensira does it for you.

​
Stopping it

  • Stop one walk: act with stop on the run over MCP, or POST /v1/browser-runs/{id}/stop. The walk ends before its next page.
  • Pause every browser run in the workspace: POST /v1/browser-runs/pause. Runs stop at their next step and no new one starts until a person resumes them in the app. A key that may steer can pause, because pausing only takes power away; only a person can resume.
  • Withdraw the consent: no walk starts after that until a person gives consent again. Consent is checked before each walk opens a browser; a walk already running finishes its few pages, or you can stop it as above.
We can also stop browser runs for one workspace, or for everyone at once, if something goes wrong on our side. A stopped walk is not charged.

​
What it costs

Half a credit for each minute the browser is open, counting a started minute as a whole one, and never more than 7.5 credits for one walk. Those 7.5 credits are reserved before the browser opens, and what the walk did not use is returned when it ends. If your balance does not cover them, the walk does not start and its next step is to add credits. Only a walk that finishes is charged. A walk that you stop, that a pause stops, or that could not finish is not charged. The details are under Browser work.

​
What it keeps

Each walk is a browser run you can replay: every page it opened, with a screenshot of the page as it saw it, and, for a walk that finished, the recording of the session. Screenshots are kept for 30 days (see Data retention).

​
Read it yourself

A walk’s run has the action signup_check and the mode own_site_walk. Its status is running, done, refused (for example, the balance did not cover it), killed (stopped) or failed (it could not finish, and it runs again on its next weekly turn).