How WOOL works.

Your user signs in to any website once. WOOL keeps that session in the cloud and runs agents in it from your prompts.

One example, end to end

Tally is an expense app. Every Amazon purchase reaches your bank as a line that says AMZN Mktp and nothing more, Amazon dropped its order history export in 2023, and there is no API for a person’s own orders. So Tally’s user connects their Amazon account once. From then on Tally sends prompts to the WOOL API with a token for that connection, WOOL runs the agent in the cloud inside the user’s session, and every charge comes back as an itemized receipt, ready for the books.

01 · Connect

Your user connects a website once. They sign in on the real site, on WOOL’s connect page, and say yes.

WOOL keeps the signed-in session in the cloud. No password or code ever reaches your app.

[ fig. 01 — what Tally’s user sees ]

02 · Work

You send a prompt. WOOL runs the agent. In the cloud, inside your user’s session, as their account.

One API call with the connection’s token. Amazon has no API for this; WOOL doesn’t need one.

[ fig. 02 — one connection, end to end ]

Tallyregistered
Permissionapproved
amazon.comconnected
Agent runin the cloud
Receiptsitemized

03 · Result

You get back what it did and what it found. In plain JSON, the shape you asked for.

From the same API. Tally files each one against the bank line it matches.

[ fig. 03 — the request and the result ]

“Itemize every order from the last 30 days, with the card charge each one matches.”

requestoutput_schema{ "orders": { "type": "array", "items": {
    "date": "string", "items": ["string"],
    "total": "number", "charged_as": "string" } } }

result.extracteddone{ "orders": [
    { "date": "2026-09-03",
      "items": ["Standing desk mat"],
      "total": 39.99,
      "charged_as": "AMZN Mktp US*2K4X7" },
    { "date": "2026-08-27",
      "items": ["USB-C dock", "HDMI cable"],
      "total": 146.98,
      "charged_as": "AMZN Mktp US*7Q1MZ" }
  ] }

Every AMZN Mktp line on the statement now has its items. The schema is shortened here; the docs show the full form.

04 · Control

Your user stays in control. Every connection is theirs to end.

Revoke at any time, from the app or from WOOL.

[ fig. 04 — what stays with the user ]

Revoke at any timeThe connection ends. Tally’s agent stops.
Credentials never leave the websiteTyped once by your user on amazon.com, never seen by Tally.
Every run is containedAn isolated browser, one connection at a time.

Ready to build? Start with one connection.