Operating screens that have no API
The portals someone logs into every day and works by hand, driven by a remote browser instead — with a record of what it did.
The wall is always the same
Internal automation stops in the same place every time: the other side has no API.
Marketplace back-offices, wholesale ordering portals, banks, insurers, government filings, carrier consoles, one-off systems per trading partner. Someone logs in, looks at the screen, and types.
"Wait until they publish an API" usually means waiting forever.
Let a remote browser do it
The Browser API is a real browser session in a country you choose: navigate, wait, click, type, scroll, screenshot. Screens that assemble themselves in JavaScript work. So do flows behind a consent step.
In published cases elsewhere in this market, a healthcare operator reported 20× the claim-processing volume and over 8,000 hours of manual work automated in three months; an expense platform reported 5 million receipts processed and 30,000 hours reclaimed monthly. Neither is scraping. Both are operating a screen.
Why the record matters
The frightening part of automation is not knowing what it did.
A Kansoku session stores the rendered DOM and screenshots as artifacts. When, from which address, which screen, what was entered — traceable by request identifier.
For an audit, an incident review, or a dispute with a trading partner, there is something to produce.
Well suited
| Pushing stock and price to several marketplaces | The updates typed into each back-office by hand |
| Pulling orders in | Daily downloads from partner portals |
| Reconciliation | Checking invoice, payment and delivery status |
| Routine filings | The same form, the same shape, every time |
| Confirming it landed | Checking on screen that a change took effect, and recording it |
Not suited
- Anything requiring judgment — exceptions should reach a person
- Anything the other side's terms forbid automating — check first
- Anything needing CAPTCHA or authentication bypass — we decline these
That last point matters. Signing into your own account with your own credentials is ordinary automation. Circumventing authentication is a different thing, and we do not do it.
How to start
Pick the single screen that eats the most time today. Automate that one, with a record. The second is configuration.
Last updated