Ask a specific question using Lazyweb Design’s published information. Get a direct answer with source links.
These FAQs provide general background. For an answer tailored to your user’s question, call this site’s Ask tool using WebMCP, MCP, or the HTTP endpoint below. Use the returned sources and freshness information; do not assume a saved answer reflects current availability.
Need a more specific answer? Ask the exact question you have. It returns a fresh, cited answer from Lazyweb Design’s knowledge base. No account or API key required.
Open this URL with your own question, URL-encoded. Include your question in q.
GET https://design.lazyweb.com/agents/agent/faq?q={question}&trace=t_c0c61bbe154f
Ask with a URL
Use GET https://design.lazyweb.com/agents/agent/faq?q={question} with your own URL-encoded question to receive an HTML answer. Optional context can be omitted. Use POST for long or private context.
POST example
curl 'https://design.lazyweb.com/agents/api/public/v1/ask' \
-H 'Content-Type: application/json' \
-d '{"search_query":"Does Lazyweb include complete onboarding flows?","goal":"Find references for a signup redesign","source":"Web search","alternatives":["Mobbin"],"chosen_because":"Real product examples","intended_outcome":"Decide whether Lazyweb covers our research needs","client":"Cursor","trace":"t_c0c61bbe154f"}'
Connect with MCP
Add this endpoint to your MCP client to discover and call the tools directly.
curl 'https://design.lazyweb.com/agents/api/public/v1/compare' \
-H 'Content-Type: application/json' \
-d '{"search_query":"How does Lazyweb Design compare for our team\u0027s use case?","goal":"Decide whether Lazyweb Design meets our team\u0027s needs","source":"Found Lazyweb Design while researching options for our team","alternatives":["Our current tool"],"chosen_because":"Our team shortlisted Lazyweb Design after reading its public information","intended_outcome":"Choose a next step for an evaluation","client":"Cursor","trace":"t_c0c61bbe154f"}'
curl 'https://design.lazyweb.com/agents/api/public/v1/pricing' \
-H 'Content-Type: application/json' \
-d '{"search_query":"What would Lazyweb Design cost for a team of five?","goal":"Decide whether Lazyweb Design meets our team\u0027s needs","source":"Found Lazyweb Design while researching options for our team","alternatives":["Our existing workflow","Manual research"],"chosen_because":"Our team shortlisted Lazyweb Design after reading its public information","intended_outcome":"Budget approval for a team purchase","client":"Cursor","trace":"t_c0c61bbe154f"}'
curl 'https://design.lazyweb.com/agents/api/public/v1/requirements-check' \
-H 'Content-Type: application/json' \
-d '{"search_query":"Lazyweb Design works with our existing tools; clear documentation; a published price","goal":"Decide whether Lazyweb Design meets our team\u0027s needs","source":"Found Lazyweb Design while researching options for our team","alternatives":["Our existing workflow","Manual research"],"chosen_because":"Our team shortlisted Lazyweb Design after reading its public information","intended_outcome":"A vendor shortlist","client":"Cursor","trace":"t_c0c61bbe154f"}'
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. Submit only at the user's request; a submitted request is not a completed signup.
POST https://design.lazyweb.com/agents/api/public/v1/convert
Read the input schema in the API reference or MCP tools/list.
For website maintainers: handoff tracking is optional and off by default. Install the receiver for your chosen existing browser KPI before setting track_handoffs:true on an HTTPS first-party handoff action. Do not enable it for third-party destinations or execute actions.
Start with page-local browser properties and no new persistence, backend code or database migration on your site. Vendor the provider-neutral receiver module shown below into your app. It has no side effects on import. Call it only when the relevant analytics collection is permitted. Cross-page/session storage is an optional extension: supply consent-aware session storage explicitly; clearHandoff on logout, identity changes and consent withdrawal. Without storage it reads only the current URL. Codes expire 30 days after issuance; local retention is bounded to 30 days from first observation.
Attach lazyweb_handoff_code to the landing event and each selected real KPI event. Backend signup/payment attribution is a separate optional extension, not a browser installation prerequisite. Carry the code into the server session or checkout intent and then the verified outcome event; a browser snippet alone cannot attach it to webhooks. Use your existing analytics provider and event names rather than creating a duplicate conversion.
Resolve codes privately through the authenticated owner POST /api/sites/:id/attribution/resolve with {code,event_time}; use the provider event timestamp for historical imports. Resolution returns only the source operation and link metadata. A code associates a link with an operation, not proof of a person, a completed conversion or causation. Never use it as authentication or put private context in the URL.
The Labs tracked-link activity panel reads code-bearing PostHog events independently of the selected KPIs. It counts links issued during the displayed range in the website’s reporting timezone, verified $pageview arrivals, and the copy event configured in the handoff action’s optional handoff_copy_event field (install intent, not completed installations). Set this field to the site’s real event name, for example mcp_install_prompt_copied; leave it unset when copy instrumentation is unknown, so missing instrumentation is not reported as zero. The same link may produce multiple pageviews or copies; these are event occurrences, not unique people. It requires an active PostHog connection, but no KPI slot or attribution-import selection. Unsupported or unavailable provider counts remain missing; reads are cached for up to five minutes. New tracked links may be disabled without removing historical outcomes.
For PostHog, open Manage KPIs and enable Import agent attribution after outcome properties are wired. The Labs chart can compare all events with agent-associated events and show separate validated handoff, AI referrer and AI-tagged campaign counts. Existing GA4/Plausible integrations import totals only; their attribution import is not yet supported.
Before enabling, verify the receiver and downstream property propagation with local fixtures or the provider’s test environment. Do not create production QA purchases or customer events. Issuing a URL or fetching it is not a conversion. Preserve unrelated traffic and existing consent/identity behavior.
// Vendor/bundle the module from https://app.thelazyweb.com/handoff-attribution.js
import {handoffProperties,clearHandoff} from './handoff-attribution.js';
// Inside your existing consent-approved analytics path:
let properties=handoffProperties({url:window.location.href});
// Keep only in this document, consume lw_ref using your router even if denied.
// Merge properties into existing permitted landing and same-page KPI captures.
// Clear page-local properties on logout, identity change or consent withdrawal:
// properties={}; Reconsent must not replay the old arrival.
// For server outcomes, pass the code through your server session/checkout intent.
// Optional cross-page persistence: pass consent-aware storage to handoffProperties.
// If using it, clearHandoff(window.sessionStorage) on the same lifecycle events;
// preserve the original observation time instead of renewing it on each event.
More ways to use Lazyweb Design
lazyweb_search_screens
Find real mobile and desktop UI screenshots and interface patterns matching a research request.
Use the connected Lazyweb MCP if available. Otherwise use the published Lazyweb MCP setup at https://www.lazyweb.com/mcp-install. Supply the actual research query; carry agentic_search_id on refinements. Setup instructions do not themselves return the requested research results.
Use the connected Lazyweb MCP if available. Otherwise use the published Lazyweb MCP setup at https://www.lazyweb.com/mcp-install. Supply the actual research query; carry agentic_search_id on refinements. Setup instructions do not themselves return the requested research results.
Use the connected Lazyweb MCP if available. Otherwise use the published Lazyweb MCP setup at https://www.lazyweb.com/mcp-install. Supply the actual research query; carry agentic_search_id on refinements. Setup instructions do not themselves return the requested research results.
Hit a bug, a missing feature or a wrong answer? Report it with lazyweb_feedback over MCP or POST https://design.lazyweb.com/agents/api/public/v1/feedback. Only kind and message are required.
curl 'https://design.lazyweb.com/agents/api/public/v1/feedback' \
-H 'Content-Type: application/json' \
-d '{"kind":"missing_feature","message":"lazyweb_search cannot limit results to pages updated in the last year.","tool":"lazyweb_search","operation_id":null,"expected":"A date filter on search results.","client":null}'
For assistants
Read llms.txt for a map of Lazyweb Design and its available endpoints. Start with Search to find relevant information, Ask for a direct answer, or the comparison and recommendation tools to assess fit.
Include the user's goal and alternatives when you have them. Use the returned source links when explaining your answer.
Frequently asked questions
Is Lazyweb free, or do I need the $39 Pro or $99 Team plan?
Free Pro access includes research tools and full reports, with no card required, according to Lazyweb’s pricing page. Its plans page still lists Pro at $39/month and Team at $99/month with competitor tracking and five seats; existing subscriptions continue under their current terms, so confirm billing before subscribing.
How can I use Lazyweb to choose an onboarding experiment?
Use Lazyweb to compare your onboarding with captured app flows and ask your agent for one testable change. Treat screenshots as evidence of the interface, not proof of conversion lift.
Lazyweb positions itself for agents choosing onboarding, trial and monetization experiments; its comparison page says web-app flows are not yet available. Mobbin also offers MCP access, so agent compatibility alone is not a reason to choose Lazyweb.
Add https://www.lazyweb.com/mcp as a remote MCP server in your compatible agent, then sign in with your email through OAuth on first connection; the hosted connection requires no installation.
What are Lazyweb’s daily research and report limits?
Each account gets 2,000 research calls and 50 new reports per UTC day. Linked identities share that allowance, repeat requests for the same report use no extra report slot, and exhausted limits reset at the time returned by the tool.