Skip to main content

Get started

Up and running with qURL™ in minutes.

Protect an S3 website on AWS

Coding agent

  1. 1

    Paste the prompt

    Paste this into the agent that built your app. No account needed.

    Read this skill and use qURL to share local apps and files moving forward. https://layerv.ai/skills/qurl/SKILL.md

    The agent installs the qURL CLI, publishes your app privately, and gives you an address to send. Expect to approve the install and qurl publish.

    What the agent installs, and using Codex

    On macOS and Linux the agent installs the CLI into ~/.local/bin with LayerV's install script: no Homebrew and no sudo, even on a Mac that has Homebrew.

    Codex starts with network access off, so save the skill first: see the Codex guide.

  2. 2

    Keep the skill installed

    Optional. Save the skill once and just say “share this app”.

    mkdir -p ~/.claude/skills/qurl && curl -fsSL https://layerv.ai/skills/qurl/SKILL.md -o ~/.claude/skills/qurl/SKILL.md
    mkdir -p ~/.agents/skills/qurl && curl -fsSL https://layerv.ai/skills/qurl/SKILL.md -o ~/.agents/skills/qurl/SKILL.md

    Cursor, Codex, Windsurf, VS Code Copilot, and Gemini CLI read ~/.agents/skills.

  3. 3

    Send the address

    Choose who can open the app. Give the agent email addresses for named recipients.

    The agent checks private policy support, then sends invitation emails only to the people you name. If the deployment can't support that, the app stays private. Ask for a one-time link when that meets your needs.

    One-time link? Send it in a direct message, not a public channel: whoever opens it first uses it. Avoid email and apps that preview links, because a scanner that runs the page could use its one opening. Don’t open it yourself to check it, for the same reason.

    What your recipient sees

    A one-time link (when qurl share confirms one-time use)
    They open it in a browser and land on your app, with no install and no LayerV account. It works once and expires on its own. Your app’s own sign-in still applies.
    An email invitation (what a coding agent sends)
    They open the invitation in a browser, see who published the app (marked Not verified), verify their email there, and save a passkey. The email verification code stays in that flow; they never send it to you. Where the page offers Email me a link, they can use that instead of a passkey.
    Legacy: an access request at https://qurl.link/<CRID>
    Only for resources published with --allow-requests. They press Request access, type a name, save a passkey, and get a six-digit code to give you. Once you approve that code, they press Open anyway.

Next: issue links from your own code

A free account adds a dashboard and an API key, so your backend can create a link for each person or task.

Book a pilot

Tell us what to hide. We’ll scope a pilot.

Enterprise starts with a paid pilot on one application, typically 60 to 90 days, credited in full toward year one if you convert within 60 days. After that, an annual package sized to what you protect, not per seat.