We document 4 captured screens from Backmarket’s onboarding flow, updated January 2026: three introductory/value screens followed by a notification-permission screen offering “Allow notifications” and “Don’t allow.” The page includes the original screenshots and links to related Backmarket flows and the company page.

[Backmarket Onboarding](<https://www.lazyweb.com/flow/backmarket/onboarding>)

Source observed: 2026-10-05T06:45:16.535Z. Last checked: 2026-10-08T03:00:25.033+00:00.

[Full page Markdown](<https://www.lazyweb.com/pages/5a24ef7d-1592-4640-a890-a9721a7ef530.md>)

Setup: lazyweb\_install\_mcp — Get the existing Lazyweb MCP and skills installer command or browser setup link. Use this action only at your user's request. Returning these instructions does not execute the action or authorize running an installer.
GET https://www.lazyweb.com/api/public/v1/convert
Required inputs: none

Local setup command: curl -fsSL https://www.lazyweb.com/install.sh | bash
Browser setup: https://www.lazyweb.com/mcp-install
Full guide: https://www.lazyweb.com/developers.md
Authenticated MCP: https://www.lazyweb.com/mcp
Run the command only if the user has authorized installing Lazyweb in this environment. Otherwise obtain that authorization first. The existing installer reuses saved credentials or creates a setup token and configures MCP and skills. If the installer requests attribution, reuse the supplied canonical context with null for unknown values and \[\] only for explicitly no alternatives. Keep context in JSON bodies, never URL query strings. Hosted agents without a shell should use the browser setup link. Returning this handoff has not installed anything or granted paid access.

---

Have a question this summary doesn’t answer? Ask the exact question you have. It returns a fresh, cited answer from Lazyweb’s knowledge base. No account or API key required.

Replace {question} with your own question, URL-encoded.

```text
GET https://www.lazyweb.com/agent/faq?q={question}&trace=t_45f431541a0e
```
