What share of Wield recipes need a login? 41 recipes on 29 sites
In Wield's registry, 7 of 41 recipes need a login, or 17%. The other 34 read public pages without one. Five of the login recipes read data and two write it. All seven are untested. The registry leans toward search, so this share does not describe the whole web.
The 41 recipes by login and effect
| Effect | Login needed | Recipes | Share |
|---|---|---|---|
| Read | No | 34 | 83% |
| Read | Yes | 5 | 12% |
| Write | Yes | 2 | 5% |
The 34 public reads have these statuses: 28 ok, 3 ok in the browser only, 1 ok with an extension start path, and 2 pending extension work (bahn.de search-connections and immobilienscout24.de search-rentals).
What the login recipes are
- Read, with login: doctolib.de/my-appointments, kleinanzeigen.de/my-messages, lieferando.de/order-status, zalando.de/order-status and bahn.de/my-bookings.
- Write, with login: doctolib.de/book-slot and kleinanzeigen.de/message-seller. Each write needs an explicit Allow for every run.
All seven are untested. Each was checked only while logged out. For example, the Doctolib my-appointments recipe answers 401 "User not logged in". The field names for logged-in responses are guesses until a recorded trace exists.
Why the benchmark has none
The benchmark covers 23 tasks on 21 sites, and every task is a public-page read. It says nothing about login recipes. Their success and speed are not measured yet.
What a write needs from you
The two write recipes change data on the site: a booking request and a message. Before the first write request leaves the browser, Wield opens a window that lists every request and its body. Deny is the default. If there is no answer within two minutes, the request is denied. One Allow covers one run, and no setting can turn this check off.
Login recipes add one more point. Wield logs every request on your own computer, with the method, host, path, status and timing. It never logs bodies or query values. The log files stay on the device.
Method and caveats
- Counts come from each recipe's effect and login fields in the registry, as of 7 Nov 2026.
- The registry started with search recipes, so its mix is not a sample of the web.
- Login recipes use the session already in the user's browser. Wield never reads, copies or sends cookies or passwords.
FAQ
How many of Wield's recipes need a login?
7 of 41, or 17%. Five read data and two write it. Every one of the seven is untested.
Can Wield log in for me?
Login recipes use the session you already have in your browser. Wield never reads, copies or sends cookies or passwords, so it does not sign in on your behalf. The recipes marked as needing login stay untested until a logged-in recording exists.
Why are the login recipes untested?
Each one was checked only logged out, which shows the login wall but not the data behind it. Testing the logged-in case needs a recorded trace of a session that is signed in, and none of the seven has one yet.