Scope
Book a demo

Step 1 of 2

Book a demo

Your work email first, then pick a time.

Backed byCombinator

Own the agent customer journey.

See which AI agents find your product, what they came to do and where they stop. Fix what blocks them, then watch the revenue that follows.

  1. 01Discover0 now
  2. 02Evaluate0 now
  3. 03Install0 now
  4. 04Sign in0 now
  5. 05Pay0 now
  6. 06Revenue$48,210
Agent sessions moving through a customer journey. Illustration, sample data.Point anywhere to look closer

The blind spot

Agents already shop on your buyers' behalf. Your analytics can't see them.

Your analytics

0 agent sessionsNot tracked

Scope

1,143 agent sessions29.1% converted

The console

This is what Scope sees.

Every agent session on your docs, API and MCP server, joined into one journey per agent, with the drop-offs ranked by what they cost.

Scope/Overview
TripeSample workspaceSep 12 to Oct 12

Agent sessions4 live

1,143▲ 22%

30 days

Conversion

29.1%▲ 2.4 pts

to first payment

Main intent

Subscriptions

21% of 723 intents

Biggest fix

API keys guide

289 sessions lost

Funnel by agent

1,143 sessions

  • Cursor491
  • Codex290
  • Claude Code204
  • Unnamed158

1,143

Discovered

−31%

78569%

Installed

−20%

62555%

Signed in

−47%

33329%

First payment

−25%

24922%

Second payment

−36%

15914%

MCP connected

Intents

in their own words

  • Subscriptions151

    “Bill API calls at $0.002 each with usage-based billing.”

  • Checkout142

    “Set up a Checkout session for a one-time €120 payment and return the URL.”

  • Refunds45

    “Refund the last charge for cus_8x2Lk and let them know by email.”

Fix next

ranked by sessions lost

  • Wrong auth header in the API keys guide

    289 sessions lost · before the first payment

    Fix

  • Test payment declined on a real card

    185 sessions lost · before the first payment

    Fix

  • Markdown reader served HTML

    108 sessions lost · before the install

    Fix

The agent customer journey, step by step

  1. 01Attribute

    See every agent that arrives, and how it found you.

    Claude Code, Codex, Cursor, Muse, Instinct and the long tail, each named with the evidence behind the name. See what it searched for, the page it landed on and the ones it skipped.

    Arrivals4 sessions now
    • CodexTerminalfound you via llms.txtdeclared2s
    • Claude CodeTerminalfound you via a search resultverified5s
    • CursorEditorfound you via your docs searchdeclared9s
    • InstinctTextfound you via a comparison pagedeclared14s
    • UnnamedUnknownfound you via sitemap.xmlinferred21s

    Codex searched your docs

    usage based billing with meter events
    • /docs/usage-billing404, guided
    • /docs/billing/usageOpened
    • /docs/api-keysSkipped

  2. 02Intent

    Understand why they came.

    Every session carries the task the agent was given, in the person's own words. Scope groups them into intents and shows which ones turn into customers.

    Intents723 sessions with a stated task

    This session: Set up usage-based billing with meter events for our API. Grouped under Subscriptions.

    • Subscriptions151 sessionsconverts 41%

      “Bill API calls at $0.002 each with usage-based billing.”

    • Checkout142 sessionsconverts 33%

      “Set up a Checkout session for a one-time €120 payment and return the URL.”

    • Refunds45 sessionsconverts 12%

      “Refund the last charge for cus_8x2Lk and let them know by email.”

  3. 03Journey

    Follow every step.

    Docs read, package installed, signed in, first API call, MCP connected. Scope joins each step into one journey and marks the moment it broke.

    JourneyCodex · one session, start to stop

    Task: “Set up usage-based billing with meter events for our API.”

    1. 00:00read /llms.txt
    2. 00:04read /docs/billing/usage
    3. 00:21npm install @tripe/cliInstalled
    4. 00:48tripe login, approved by a personSigned in
    5. 01:12POST /v1/meters 401 X-Api-Key rejectedBlocked
    6. 01:15read /docs/api-keys same header again
    7. 01:31POST /v1/meters 401
    8. 01:38session ends, no first paymentStopped
    Got to
    Signed in
    Stopped at
    First API call
    Failed calls
    2 of 2

  4. 04Revenue

    Tie agents to revenue.

    Conversion and revenue by agent, by intent and by page. Know which agents send paying customers, and what each drop-off costs you.

    Revenue by agent30 days
    AgentSessionsConvertedRevenue
    Cursor49128%$19,870
    Codex29036%$15,040
    Claude Code20435%$11,280
    Unnamed15811%$2,020
    All agents1,14329%$48,210

    Revenue by intent

    Subscriptions$21.4k
    Checkout$17.9k
    Payments$6.5k

    Observed: 289 sessions like this one stopped at the first API call. Estimated: $6,940 a month at risk, at the conversion rate of sessions that got past it.

  5. 05Improve

    Fix what stops them. Prove it worked.

    Scope ranks fixes by the revenue they unlock and shows each one as a change you can read, like a wrong header in an API guide. Test it on real agents before your buyers meet it, then watch the funnel move.

    Fix next289 sessions · before the first payment

    Wrong auth header in the API keys guide

    CancelConfirm

    The same task on 48 agent runs before release · reached first payment

    Before29.1%
    After42.8%
Following Codex · usage billing
  1. Arrived
  2. Asked
  3. Blocked
  4. Cost counted
  5. Fixed
Arrivals4 sessions now
  • CodexTerminalfound you via llms.txtdeclared2s
  • Claude CodeTerminalfound you via a search resultverified5s
  • CursorEditorfound you via your docs searchdeclared9s
  • InstinctTextfound you via a comparison pagedeclared14s
  • UnnamedUnknownfound you via sitemap.xmlinferred21s

Codex searched your docs

usage based billing with meter events
  • /docs/usage-billing404, guided
  • /docs/billing/usageOpened
  • /docs/api-keysSkipped
Intents723 sessions with a stated task

This session: Set up usage-based billing with meter events for our API. Grouped under Subscriptions.

  • Subscriptions151 sessionsconverts 41%

    “Bill API calls at $0.002 each with usage-based billing.”

  • Checkout142 sessionsconverts 33%

    “Set up a Checkout session for a one-time €120 payment and return the URL.”

  • Refunds45 sessionsconverts 12%

    “Refund the last charge for cus_8x2Lk and let them know by email.”

JourneyCodex · one session, start to stop

Task: “Set up usage-based billing with meter events for our API.”

  1. 00:00read /llms.txt
  2. 00:04read /docs/billing/usage
  3. 00:21npm install @tripe/cliInstalled
  4. 00:48tripe login, approved by a personSigned in
  5. 01:12POST /v1/meters 401 X-Api-Key rejectedBlocked
  6. 01:15read /docs/api-keys same header again
  7. 01:31POST /v1/meters 401
  8. 01:38session ends, no first paymentStopped
Got to
Signed in
Stopped at
First API call
Failed calls
2 of 2
Revenue by agent30 days
AgentSessionsConvertedRevenue
Cursor49128%$19,870
Codex29036%$15,040
Claude Code20435%$11,280
Unnamed15811%$2,020
All agents1,14329%$48,210

Revenue by intent

Subscriptions$21.4k
Checkout$17.9k
Payments$6.5k

Observed: 289 sessions like this one stopped at the first API call. Estimated: $6,940 a month at risk, at the conversion rate of sessions that got past it.

Fix next289 sessions · before the first payment

Wrong auth header in the API keys guide

CancelConfirm

The same task on 48 agent runs before release · reached first payment

Before29.1%
After42.8%

Tripe · Sample workspace

One loop. More agents find you, more of them finish, more of them pay.

Agents

Every agent, named.
Every context, separated.

Each agent is named with the evidence behind the name, and its sessions are split by where it runs. Anything we cannot name is grouped by how it behaves, never guessed.

  • Claude Code
  • Codex
  • Cursor
  • Muse
  • Instinct
  • and more

Every name carries a label

Verified
Signed by the agent's provider
Declared
The agent said who it is
Inferred
Its behavior matches one family

FAQ

Questions, answered.

Still curious? See it on your own product.

Book a demo

Step 1 of 2

Book a demo

Your work email first, then pick a time.

What is Scope?

Scope is the agent experience platform. It shows how AI agents discover, evaluate and use your product, ties each agent's journey to sign-ups and revenue, and tells you what to fix so more of them succeed.

What is the agent customer journey?

The path an AI agent takes on a person's behalf: the search, the pages it reads, the sign-up, the first purchase or API call, and the revenue that follows. Scope reconstructs that path for every agent session.

Which agents does Scope identify?

Claude Code, Codex, Cursor, Muse, Instinct and many more, with new agents added as they appear. Every name carries a label that says how sure we are: verified, declared or inferred.

Why can't I see this in my analytics or my logs?

Some analytics tools can flag a request from a known agent provider, but they see a ping, not a session: no journey, no intent and no link to the account or the purchase that followed. Many don't see agents at all, because agents never run your page scripts. Logs see requests one at a time, and when an agent gives up before reaching you, nothing is logged.

How do fixes work?

Every fix comes with the sessions that surfaced it and the drop-off it explains. You get the change itself, such as a corrected code sample, a docs page or an MCP description, ready to review and ship. Then Scope tests it on real agents to prove the lift.

Who uses Scope?

Teams whose products agents already use, or soon will: developer tools, APIs, payments, SaaS, commerce and travel. If an agent can sign up for, buy or use your product, Scope is for you.

How do I reach you?

Write to anand@tryscope.app, or book a demo and we will walk you through it on your own product.