> ## Documentation Index
> Fetch the complete documentation index at: https://tryklint.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Fetch /llms.txt for the complete page index before exploring further. Every docs page is available as markdown by appending .md to its URL. Coding agents should start at /for-agents/coding-agents.md.

# Introduction

> Power your AI agents with social context.

Klint is the social context API. It turns Instagram into context your agents can use: **[search posts](/docs/instagram/search/posts-search)**, **[search accounts](/docs/instagram/search/accounts-search)**, and **[extract content](/docs/instagram/extract)**, all in plain language.

Klint watches every video and reads every post. It extracts the spoken words, the on-screen text, and what's actually happening in the content. Your agent does the thinking while Klint supplies the context.

<Note>
  **For AI agents:** `/llms.txt` indexes every page. [Klint for coding agents](/docs/for-agents/coding-agents) is the whole contract on one page. Append `.md` to any URL for raw markdown.
</Note>

## Get started

### Install the CLI and skills

One command authenticates and adds the Klint skills, including every [cookbook](/docs/cookbooks/overview), to your detected coding agents:

```bash theme={null}
npx klint@latest init
```

<Note>
  Restart your coding agent after setup so it discovers the new skills.
</Note>

### Set up the Klint MCP server

One server, every Klint capability. Works in any MCP client.

<Tabs>
  <Tab title="Claude Code">
    <Steps>
      <Step title="Run this command in your terminal">
        This adds Klint as a remote MCP server in Claude Code.

        ```bash theme={null}
        claude mcp add --transport http klint https://mcp.tryklint.ai
        ```
      </Step>

      <Step title="Verify installation">
        In Claude Code, run `/mcp` to see `klint` in your connected servers.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Codex">
    <Steps>
      <Step title="Run this command in your terminal">
        This adds Klint as a remote MCP server in Codex.

        ```bash theme={null}
        codex mcp add klint --url https://mcp.tryklint.ai
        ```
      </Step>

      <Step title="Verify installation">
        Run `codex mcp list` to confirm `klint` is registered, then restart Codex.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Cursor">
    <Steps>
      <Step title="One-click install">
        <a href="https://cursor.com/en/install-mcp?name=Klint&config=eyJ1cmwiOiJodHRwczovL21jcC50cnlrbGludC5haSJ9">**Add to Cursor →**</a>
      </Step>

      <Step title="Verify installation">
        Confirm the install when Cursor opens, then check Settings → MCP to see `klint` enabled.
      </Step>
    </Steps>
  </Tab>

  <Tab title="VS Code">
    <Steps>
      <Step title="One-click install">
        <a href="https://insiders.vscode.dev/redirect/mcp/install?name=Klint&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.tryklint.ai%22%7D">**Add to VS Code →**</a>
      </Step>

      <Step title="Verify installation">
        Confirm the install when VS Code opens. The server appears under MCP Servers in your settings.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Any MCP client">
    Point the client at:

    ```text theme={null}
    https://mcp.tryklint.ai
    ```
  </Tab>
</Tabs>

### Set up with an agent

Or hand the setup to the agent itself:

```text theme={null}
Fetch https://tryklint.ai/for-agents/coding-agents.md and set up Klint
for this project.
```

### Build directly

<Columns cols={2}>
  <Card title="Get an API key" icon="key" href="/docs/quickstart">
    Create a key in the dashboard, then run the quickstart request.
  </Card>

  <Card title="API reference" icon="book" href="/docs/api-reference/overview">
    Every endpoint, request field, and response shape.
  </Card>
</Columns>

## What can Klint do?

<Columns cols={2}>
  <Card title="Find trending hooks in your niche" icon="arrow-trend-up" href="/docs/cookbooks/find-trending-hooks">
    See which hooks, formats, and claims are earning attention this week, before everyone copies them.
  </Card>

  <Card title="Find creators in your niche" icon="users" href="/docs/cookbooks/find-creators">
    Discover and qualify the creators who actually publish in your space. Every name arrives with the posts that prove it.
  </Card>

  <Card title="Reverse-engineer viral content" icon="film" href="/docs/cookbooks/reverse-engineer-viral-content">
    Pull any post apart: hook construction, key messages, offer, transcript, and how the numbers moved.
  </Card>

  <Card title="Run a prior-art check" icon="magnifying-glass" href="/docs/cookbooks/prior-art-check">
    Has someone already run this hook or concept? Search what posts say and show, not just captions.
  </Card>

  <Card title="Read any Reel as text" icon="closed-captioning" href="/docs/cookbooks/read-reels-as-text">
    Transcript, on-screen text, and visual descriptions for any post, one GET away.
  </Card>

  <Card title="Map a niche" icon="map" href="/docs/cookbooks/map-a-niche">
    Build the research set: qualified accounts in a niche, plus the posts that prove each one belongs.
  </Card>
</Columns>

Search is where it starts. The same API is built to grow into performance history, monitoring, and niche benchmarks.

## Why Klint?

* **Whole-post search**: One semantic query over speech, on-screen text, visuals, and creative structure, pinned by hard filters.
* **Results that qualify**: Every result satisfies the query and every filter. Weak matches never pad the list.
* **The hard part is done**: Watching, transcribing, reading, creative breakdown. No proxies, no login walls, no raw video.
* **Honest numbers**: Metrics are observations with timestamps. Unknown is never dressed up as zero.
* **Agent-native**: MCP server, installable cookbook skills, every page as markdown, errors that teach the fix.
* **Compounding history**: Baselines, monitoring, and benchmarks accumulate on the same API as Klint keeps watching.

## The API

Klint covers Instagram today, deeply. TikTok, YouTube, and other social channels follow on the same API.

### Instagram

Three calls cover the surface:

<Card title="Search posts" icon="magnifying-glass" href="/docs/instagram/search/posts-search" horizontal>
  Find posts by what they say, show, and how they perform.
</Card>

<Card title="Search accounts" icon="user" href="/docs/instagram/search/accounts-search" horizontal>
  Qualify accounts by their profile and what they actually publish.
</Card>

<Card title="Extract" icon="photo-film" href="/docs/instagram/extract" horizontal>
  A post or account back in full, understood.
</Card>

## Resources

<Columns cols={2}>
  <Card title="Query writing" icon="pen" href="/docs/instagram/search/posts-search#writing-a-query-that-qualifies">
    What separates a query that qualifies from one that comes back empty.
  </Card>

  <Card title="Filter grammar" icon="filter" href="/docs/instagram/search/posts-search#filter-the-results">
    Pin results down with hard filters, and see exactly what gets rejected.
  </Card>

  <Card title="Errors and retries" icon="triangle-exclamation" href="/docs/api-reference/errors">
    Every error the API returns, what causes it, and whether to retry.
  </Card>

  <Card title="Authentication" icon="key" href="/docs/api-reference/authentication">
    API keys and the request header, in thirty seconds.
  </Card>
</Columns>