---
title: "Critique the user's OWN dating bio and rewrite it three times in their voice"
method: POST
path: "/api/v1/dating/own-profile/bio"
---

# Critique the user's OWN dating bio and rewrite it three times in their voice

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

## Request

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

Costs a model call. FlirtMaster edition only (404 `edition_feature_unavailable` otherwise). Without `bio`, the one read from the last screenshot analysis is used (400 `bio_missing` if there is none). `network` sets the character limit every rewrite is fitted to (default: the network of the last analysis, else tinder). `languages` are ISO 639-1 codes, up to 3; each rewrite comes in every requested language. Uses the dating voice profile when there is one. Limited to 20 per user and hour; a demo session spends from the same 5-generation cap as suggest-message and nothing is stored.

## Request body

- object
  - `bio` string, nullable
  - `network` 'tinder' | 'bumble' | 'badoo' | 'hinge' | 'facebook' | 'instagram' | 'whatsapp' | 'telegram' | 'parejas' | 'other', nullable
  - `languages` string[]

## Response `200`

`{ analysis: { network, charLimit, languages, critique, rewrites, usedVoiceProfile } }`

## Other responses

- `400`: Invalid body, or no bio to analyse (`bio_missing`)
- `404`: Not part of this edition (`edition_feature_unavailable`)
- `422`: The bio 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)