---
title: "Analyse screenshots of the user's OWN dating profile"
method: POST
path: "/api/v1/dating/own-profile/analysis"
---

# Analyse screenshots of the user's OWN dating profile

`POST /api/v1/dating/own-profile/analysis`

## Request

- Base URL: `https://memchats.com`
- URL: `https://memchats.com/api/v1/dating/own-profile/analysis`
- Auth: HTTP bearer

Costs a vision model call. FlirtMaster edition only (404 `edition_feature_unavailable` otherwise). Multipart with 1 to 10 screenshots in `files` (png, jpeg, webp, heic; 15 MB each, 40 MB in total). Returns the detected network, a per-photo assessment (what it communicates and its quality issues), the recommended photo order and why the first one, photos to drop, missing photo types, prompt answers judged, the literal bio if visible and the top 3 changes by expected impact. It talks about photos, never about how the person looks. Limited to 10 per user and hour; a demo session spends from the same 5-generation cap as suggest-message and nothing is stored.

## Response `200`

`{ analysis, screenshotCount }`

## Other responses

- `400`: No screenshots, or more than 10
- `404`: Not part of this edition (`edition_feature_unavailable`)
- `413`: A screenshot over 15 MB, or over 40 MB in total
- `415`: Unsupported image format
- `422`: The screenshots could not be analysed
- `429`: Hourly limit, the demo cap (`demo_suggestion_limit`), or the Monthly own-profile analyses of the plan (`own_profile_quota_exceeded`, with `limit`, `used`, `remaining`, `resetsAt`; Free 6, Plus 20, Pro and Empresa 40, shared by the analysis and bio routes; admins and demo sessions are not held to it)

---

[API](https://skmtc.dev/memchats/apis/memchats-api.md) · [All operations](https://skmtc.dev/memchats/apis/memchats-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memchats/apis/memchats-api/revisions/e62bca06f785?raw)