UStackUStack
MSX icon

MSX

MSX is a market intelligence runtime and API for AI agents that helps them find startup ideas, run live market investigations, and return source-backed opportunities. It is aimed at builders and teams using Claude, Codex, Cursor, or internal agents.

MSX

Overview

MSX is a market intelligence runtime and API for AI agents. It helps agents such as Claude, Codex, and Cursor find startup ideas, decide what to build next, and run live market investigations against public demand signals.

The product is built around a hosted skill file at `msx.dev/skill.md`, a REST API, and source-backed investigation outputs. The workflow is designed so an agent can authenticate, ask before billing when needed, run a research job, and return buildable opportunities with citations and practical next actions. The enterprise pages also position MSX as a broader VOC and market-signal layer that mines web channels continuously for customer language, unmet needs, and launch or positioning inputs.

Core capabilities

Startup idea discovery

MSX turns live market signals into ranked startup ideas with evidence that agents can use instead of starting from a blank search.

Demand-signal scouting

The docs describe a workflow that can scan public demand, compare existing tools, and surface where buyers are asking for something better.

Agent authentication and API access

Agents can authenticate through a device flow, receive an account-bound API key, and then use the REST API for investigations and account checks.

Durable investigation workflow

Investigations are durable jobs with status, progress, and result endpoints, so agents can poll and resume rather than treating research as a one-shot request.

Source-backed results

Returned research includes citations, urgency, confidence, and practical next actions, which makes the output easier to use in downstream planning or drafting.

Web-wide signal mining

The enterprise page says MSX can mine 30+ web channels continuously for VOC, idea validation, talent signals, and market movement.

Common use cases

  • Validating startup ideas

    A founder or operator can ask an agent to scout a broad market question, then use MSX to rank opportunities and review source-backed summaries before deciding what to build.

  • Market and VOC research

    A PMM or research team can use the enterprise workflow to gather customer language, segment-tagged proof, and citation-grade evidence for positioning or launch planning.

  • Agent-native research workflows

    A builder can connect an agent to the skill file and API so market research runs inside the same workflow where they already work, rather than moving into a separate portal.

  • Ongoing market monitoring

    A team can run recurring investigations as durable jobs, then compare saved results and source-backed reports over time to track market movement.

  • Enterprise research support

    An enterprise buyer can contact sales for managed research, custom PDF or markdown outputs, or agent-ready market intelligence workflows.

Pros and Cons

Pros

  • Built specifically for agents, with a hosted skill file and API flow instead of a manual research workflow.
  • Produces source-backed investigations with citations, urgency, confidence, and next actions.
  • Supports durable investigation jobs, which is useful when research takes more than a single request.
  • Offers clear support paths for private account issues and setup questions.
  • Has published pricing tiers with included API access and saved results.

Cons

  • The documentation is stronger than the capability breakdown, so some workflow details are only described at a high level.
  • Pricing and support information are present, but integration specifics and data-source coverage are still limited in the public pages.

FAQ

How do agents start using MSX?

MSX is designed to give agents a simple public entrypoint: the hosted skill file at `msx.dev/skill.md` plus the REST API. The docs say agents should read the skill file before calling MSX, then follow the hosted contract for authentication, billing consent, quota handling, and investigation behavior.

How does authentication work?

The docs describe API-driven device authentication. An agent starts the device flow, shows the user a verification URL, waits for Google sign-in, and then polls for an account-bound API key before making authenticated requests.

What does an investigation return?

MSX supports durable investigation jobs. The create call returns an investigation ID and status, and the agent polls until the job succeeds, fails, cancels, or expires. When it succeeds, the result endpoint returns opportunities with evidence and next actions.

Is MSX sold as a subscription?

The pricing page lists Scout, Builder, and Growth plans. It also states that every plan includes the MSX skill, API access, saved results, and source-backed investigation reports.

How do users contact support?

Support is split by channel: email is recommended for billing, account access, privacy, deletion, or other private account details, while Discord is recommended for setup questions, product help, and agent troubleshooting.

Quick Facts

Category
AI agent market intelligence
Primary users
Agents and teams using Claude, Codex, Cursor, or internal agents
Access model
Hosted skill file plus REST API
Pricing
Paid plans listed: Scout, Builder, and Growth
Support channels
Email and Discord
Domain
mothershipx.dev / msx.dev
MSX - AI Tool, Features, Use Cases & Alternatives | UStack