# Build with ViralSpy

Canonical URL: https://docs.viralspy.com/docs



ViralSpy gives software and coding agents the same core discovery and research capabilities as the application: videos, ranked feeds, creators, advertisers, trend reports, and the ViralSpy analyst.

<div className="quick-grid">
  <a className="quick-card" href="/docs/quickstart">
    <strong>REST API</strong>

    Build predictable data workflows from any language with an OpenAPI 3.1 contract.
  </a>

  <a className="quick-card" href="/docs/mcp">
    <strong>MCP server</strong>

    Give Claude, Codex, and other MCP clients purpose-built tools and research prompts.
  </a>

  <a className="quick-card" href="/docs/api/reference">
    <strong>API reference</strong>

    Browse typed parameters, responses, errors, and copyable request examples.
  </a>
</div>

## Product limits [#product-limits]

* Search and discovery have no monthly plan quota. Automated access is still protected by burst, per-key, per-organisation, and daily fair-use limits.
* The ViralSpy analyst uses the organisation's shared monthly allowance. New organisations start with 100 analyst requests per month.
* API keys belong to one user in one organisation. A key never silently follows the user's active organisation.

## What MCP adds [#what-mcp-adds]

MCP is the tool interface used by an AI client. ViralSpy describes each operation with a strict schema, adds short instructions and workflow prompts, and returns structured data directly to the client. Your client's model decides when to call a tool; ViralSpy does not receive the rest of your conversation unless the client includes it in a tool argument.

For deterministic application code, use the REST API. For agent-driven research, use MCP. Both are backed by the same resource model and limits.