Content vault

The content vault is a searchable, AI-tagged index of every media item in your OnlyFans vault, plus the analytics that sit on top of it. Once your vault is indexed you can find any clip or set by title or tag in a keystroke, pull a whole folder as a bundle, and — far more valuable — read which content actually drives revenue, what is sitting dormant, where your demand outruns your supply, and which unseen pieces to send a given cohort next.

Every endpoint below lives under https://app.tease.link/api/admin/vault and is authenticated with a Bearer al_live_* key. All reads require the read scope; the scan trigger and auto-tag require write. Every response is JSON and is scoped to the owner that minted the key — you only ever see your own vault.

How it fits together

Scan and index the vault

Indexing is a background job. You trigger it, then poll status until it settles. A scan is idempotent — re-running it refreshes the index rather than duplicating it.

curl -X POST "https://app.tease.link/api/admin/vault/scan" \
  -H "Authorization: Bearer $TEASE_API_KEY"

{ "started": true, "already_running": false }

curl "https://app.tease.link/api/admin/vault/scan/status" \
  -H "Authorization: Bearer $TEASE_API_KEY"

{
  "folders": 84,
  "items": 5120,
  "ai_tagged": 4870,
  "last_indexed_ts": 1751280000,
  "running": false,
  "last_error": ""
}

Search the vault

Instant title- and tag-search across the index. Results come back grouped by folder, with any loose (folderless) items separated out, so the panel's content picker can render a tree immediately.

curl "https://app.tease.link/api/admin/vault/search?q=lingerie&scope=all&limit=200" \
  -H "Authorization: Bearer $TEASE_API_KEY"

Query parameters

Response

{
  "query": "lingerie",
  "scope": "all",
  "folders": [
    {
      "folder_id": "f_2291",
      "name": "Red lingerie set",
      "items": [
        {
          "media_id": "m_88120",
          "media_type": "photo",
          "folder_id": "f_2291",
          "folder_name": "Red lingerie set",
          "sorted": true,
          "title": "red set — teaser",
          "has_cover": true
        }
      ]
    }
  ],
  "loose": [],
  "counts": { "folders": 1, "items": 1 }
}

Each item carries: media_id, media_type (photo, video, gif, …), folder_id, folder_name, sorted (whether it's filed), title, and has_cover (whether a thumbnail is available — see covers).

Open a folder

Pull every item in one folder — the "select the whole pack" action. The response includes a flat media_ids array ready to drop straight into a message composer.

curl "https://app.tease.link/api/admin/vault/folder/f_2291" \
  -H "Authorization: Bearer $TEASE_API_KEY"

{
  "folder_id": "f_2291",
  "name": "Red lingerie set",
  "media_ids": ["m_88120", "m_88121", "m_88122"],
  "items": [
    { "media_id": "m_88120", "media_type": "photo", "title": "red set — teaser", "has_cover": true }
  ]
}

Pull a drop

A folder can also be read as a drop — its items grouped by role (video, photoset, bts, other) with a ready-ordered bundle_media_ids for a one-tap "send the whole drop". This is the natural unit a chatter sells.

curl "https://app.tease.link/api/admin/vault/drop/f_2291" \
  -H "Authorization: Bearer $TEASE_API_KEY"

{
  "folder_id": "f_2291",
  "name": "Red lingerie set",
  "cover_media_id": "m_88120",
  "roles": {
    "video":    { "count": 1, "media_ids": ["m_88130"] },
    "photoset": { "count": 8, "media_ids": ["m_88120", "m_88121"] },
    "bts":      { "count": 2, "media_ids": ["m_88140", "m_88141"] },
    "other":    { "count": 0, "media_ids": [] }
  },
  "bundle_media_ids": ["m_88130", "m_88120", "m_88121", "m_88140", "m_88141"],
  "counts": { "total": 11, "video": 1, "photoset": 8, "bts": 2, "other": 0 },
  "is_drop": true
}

Covers

Fetch a thumbnail image for any media id. The endpoint returns a thumbnail image (image/jpeg), so point an <img> at it directly — only items where has_cover is true have one.

curl "https://app.tease.link/api/admin/vault/cover/m_88120" \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -o cover.jpg

Returns 404 when the media id has no cover. The endpoint only ever serves a thumbnail for a media id in your own vault.

Auto-tag the backlog

auto-tag runs AI tagging over your untagged items so they become searchable and start flowing into the performance, gaps, and recommendation analytics. AI tagging runs server-side. It is an explicit action — it never sweeps your whole vault on its own — and it is cost-capped and idempotent: already-tagged items are skipped and never re-billed, and limit is clamped to a hard server ceiling rather than rejected.

curl -X POST "https://app.tease.link/api/admin/vault/auto-tag" \
  -H "Authorization: Bearer $TEASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "all_untagged": true, "limit": 100 }'

const res = await fetch('https://app.tease.link/api/admin/vault/auto-tag', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.TEASE_API_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({ all_untagged: true, limit: 100 }),
});
const result = await res.json();

res = requests.post(
    "https://app.tease.link/api/admin/vault/auto-tag",
    headers={"Authorization": f"Bearer {os.environ['TEASE_API_KEY']}"},
    json={"all_untagged": True, "limit": 100},
)
result = res.json()

Body parameters

Response

{
  "tagged": [{ "media_id": "m_88120", "tags": ["lingerie", "solo", "teaser"] }],
  "tagged_count": 1,
  "skipped": [{ "media_id": "m_88121", "reason": "already_tagged" }],
  "skipped_count": 1,
  "errors": [],
  "capped": false,
  "requested": 2
}

What sells — performance

performance ranks your vault by revenue: which individual media and which tags actually drive purchases, each with an unlock rate (how often a fan who received it bought it). This is the read behind "what's working" in the panel.

curl "https://app.tease.link/api/admin/vault/performance?limit=20" \
  -H "Authorization: Bearer $TEASE_API_KEY"

Query parameters

Response

{
  "range": { "from_ts": 1748688000, "to_ts": 1751280000 },
  "media": [
    {
      "media_id": "m_88130",
      "title": "red set — full video",
      "media_type": "video",
      "folder_name": "Red lingerie set",
      "has_cover": true,
      "tags": ["lingerie", "solo"],
      "sent": 247,
      "opened": 181,
      "purchased": 89,
      "revenue_cents": 142800,
      "unlock_rate": 0.34
    }
  ],
  "tags": [
    { "tag": "lingerie", "sent": 988, "opened": 731, "purchased": 301, "revenue_cents": 461500, "unlock_rate": 0.29 }
  ],
  "ppv_sends": 1320
}

Each media row carries media_id, title, media_type, folder_name, has_cover, tags, and the performance numbers:

What to shoot next — gaps

gaps answers "what should I shoot?" by surfacing tags where demand outruns supply — themes that sell well but where you have few items to send — alongside how much of your vault is still unsorted or untagged.

curl "https://app.tease.link/api/admin/vault/gaps?limit=20" \
  -H "Authorization: Bearer $TEASE_API_KEY"

Query parameters

Response

{
  "range": { "from_ts": 1748688000, "to_ts": 1751280000 },
  "shoot_more": [
    {
      "tag": "shower",
      "revenue_cents": 88200,
      "purchased": 61,
      "sent": 140,
      "rank": 1
    }
  ],
  "total_items": 5120,
  "unsorted": 380,
  "untagged": 250
}

Each shoot_more row reports the tag's revenue_cents, purchased, sent, and its rank — its position in the shoot list, where 1 is the most under-supplied for its demand. The list arrives already ordered; you don't need to derive the ranking.

What's gone cold — dormant

dormant returns vault items that have had zero send activity in a window — content that's just sitting there and could be re-circulated. It's a set-difference between your vault and what actually sold or was sent recently; nothing about your OnlyFans account net is touched.

curl "https://app.tease.link/api/admin/vault/dormant?window_days=30" \
  -H "Authorization: Bearer $TEASE_API_KEY"

Query parameters

Response

{
  "items": [
    {
      "media_id": "m_70011",
      "title": "beach throwback",
      "tags": ["outdoor", "bikini"],
      "cover": true,
      "last_sent": 1741000000
    }
  ],
  "count": 1,
  "window_days": 30
}

Cohort recommendations

recommend is the vault's most valuable read: given a cohort of fans, it returns unseen content — items that cohort has not already been sent — ranked for how well they fit. Point it at content (recommend for the people who bought a given piece) or describe a cohort with the same audience filters the broadcast composer uses.

curl "https://app.tease.link/api/admin/vault/recommend?source=tiktok&rfm_tag=whale&limit=20" \
  -H "Authorization: Bearer $TEASE_API_KEY"

Query parameters

Provide either content_id (recommend for the cohort that bought that content) or one or more audience filters. All parameters are optional and combine as an AND filter.

Response

{
  "items": [
    {
      "media_id": "m_88130",
      "title": "red set — full video",
      "tags": ["lingerie", "solo"],
      "cover": true,
      "unlock_rate": 0.4,
      "fit_reason": "Recommended for this cohort"
    }
  ],
  "cohort_summary": {
    "filters": { "source": "tiktok", "rfm_tag": "whale" },
    "source": "tiktok",
    "fan_count": 312
  },
  "thin": false
}

Each recommendation row carries media_id, title, tags, cover, unlock_rate, and a short, human-readable fit_reason you can show next to the suggestion.

Next steps