Skip to main content

Use cases

Let AI agents create and read your app links

An assistant can create a link for a user, share it, and read how it performed, through 47 MCP tools or the REST API. Dry runs preview a change, idempotency keys make retries safe, and error responses carry a fix and a docs link. The links open your app and count clicks and installs like any other.

How it works

  1. Connect the assistant

    Point an MCP client at https://api.warplink.app/mcp and sign in once in the browser, or pass an API key for non-interactive use. Claude Code and other MCP clients connect the same way.

  2. Give the assistant an app

    Links belong to an app. The assistant calls list_apps to find one, or create_app when the organization has none yet.

  3. Preview with a dry run

    create_link with dry_run set to true returns the result without saving it, so the person can approve the link before it exists.

  4. Create the link safely

    Send an idempotency_key with create_link. The key is kept for 24 hours, so a retry after a dropped connection does not create a duplicate.

  5. Mark the source

    Set utm_source to the assistant, for example assistant, and add a tag such as agent. Clicks from agent-made links are then easy to separate in analytics.

  6. Read the results

    get_link_analytics and query_analytics return clicks and installs. An AI assistant breakdown shows the clicks that arrive from assistants, matched by referrer host first and utm_source second.

Create, then read

What you get

Linking
Links an agent creates open your app through Universal Links and App Links, with the same iOS, Android and web routing, UTM fields and previews as links made by hand.
Attribution
Installs that follow a tap on an agent-made link, in any channel, are matched back to that link like any other install.
Analytics
Link analytics are available to the assistant over MCP and REST, including an AI assistant breakdown for clicks that arrive from assistants.

Common questions

How many MCP tools does WarpLink have?

47 MCP tools cover links, apps, domains, keys, analytics and organization details. The list on this site is generated from the same catalog the server registers.

Which assistants can connect?

Any MCP client. Most connect with the server URL and a one-time browser sign-in, and an API key works for non-interactive use.

Can an agent sign up on its own?

Yes. Post an agent_name and an email to /v1/agent/signup. We create a Free workspace, email the person a claim link and return an access token for the MCP server. Until the person claims it, the workspace holds one app and ten links, and links stay paused.

How do I stop an assistant from creating duplicates?

Send an idempotency_key on create_link or create_app. The key is kept for 24 hours, so a retried call does not make a second link.

Can I preview a link before it is created?

Yes. Set dry_run to true on create_link, create_app or update_link. The response returns the result with dry_run set to true and saves nothing.

Is this the same as agent-assisted SDK setup?

No. SDK setup is an assistant adding WarpLink to your app's code. This page covers assistants that create, share and read links for the people they work with.

Give your assistant links that work

Start building, freeFree to start. No sales call.