Overview

Each user authorizes your product once, on a page WOOL hosts called the connect page. After that, your product sends a prompt, WOOL runs an agent in the cloud inside that user's account on the website they authorized, and you get back the result, or the reason the run failed. Nothing runs on the user's computer, and your product never sees their password. WOOL handles the whole range, from a single lookup to chained, multi-step automation and monitoring, on one website or across several sites the user has connected. Your product coordinates work across sites by sending a separate run to each site's connection.

1. Once
   1. 1Your applicationQuickstart
2. Once per user
   1. 2User permissionConnect
   2. 3Website accountAccounts
3. Every prompt
   1. 4Cloud executionExecutions
   2. 5Result or failureResults

Build with a coding agent

These docs are written to be read whole by a coding agent, and the line below tells it where to start. Paste it into Claude Code, Cursor, or whichever agent you use, and it reads the docs and the API contract, then sets up the connect flow and executions in your project. For coding agents lists everything it reads.

Isn't this just ChatGPT agent, or Grok?

Those are agents a person runs on their own accounts, from a chat window. WOOL lets your users authorize your product to run agents on their accounts, through an API. Without that layer, an agent gets into someone else's account the way a stranger would, with their password. You would have to store that password, the user could not limit or revoke it, and nothing would record what the agent did in their name. With it, the user connects an account the way they'd "Sign in with Google", your product receives a token for that one connection, and every agent you run with the token acts as that user, in an isolated session, with evidence of what it did.

Most websites have no API. Your users' bank, email, supplier portal, and team tools each have a login page and nothing else. WOOL is how your product works inside those accounts with the user's permission, without holding their credentials, and with confirmation that the agent did what you asked.

What you can rely on

• The user is in control. They authorize your product on connect.trywool.com, sign in there themselves, and can revoke the connection at any time. Your product never receives their password.
• Successful connections help later users. WOOL reuses routes to a website's sign-in flow across applications, reducing repeated discovery work when the page still matches. See Faster sign-in discovery over time.
• Every agent runs isolated, in the cloud. An agent acts only as the connected account, on the connected website, in a session that exists for that run alone.
• A run succeeds or fails, and says why. WOOL confirms every result against the page before it calls the run a success. A failed run tells you the reason, and every result includes evidence: the pages the agent visited and the actions it took.
• An agent won't cross lines. It doesn't sign in, doesn't solve CAPTCHAs, and doesn't reach for sites or accounts the user didn't connect.

Connect, exchange, and run

1. Connect. Send the user to the auth link, a URL on connect.trywool.com carrying your client_id and the website to connect. On the connect page it opens, they approve your product and sign in to the website, and WOOL redirects back to you with a code.
2. Exchange. Trade the code at POST /v1/oauth/token for a connection access token, plus a connection_id and a user_id to keep.
3. Run. Start an execution with a prompt and poll it until it's COMPLETED or FAILED. A completed run holds the result, and a failed one holds the reason.

The three objects

Where to go next

Start with the Quickstart for a browser or native app, or the server-side quickstart for a backend that can keep a secret.