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

# Personas

> Define who the whole-roster search should find.

A persona is a plain-language description of who you want to reach. It can identify any employee,
not only a manager or decision maker. firmintent first analyzes the enriched roster, then refreshes
profiles, posts and contacts only for likely or possible matches.

Every `target_people` job requires exactly one persona slug:

```json theme={null}
{"input":"linkedin.com/company/acme","operation":"target_people","persona":"marketing-leaders"}
```

## Owners & founders

Every account has the system persona `owners-founders`. Its name and definition are immutable and it
cannot be deleted. It starts as the default, but you may make another persona the default. The API
always preserves at least one default and the database allows at most one per account.

## CRUD

* `GET /v1/personas` lists personas.
* `POST /v1/personas` creates one from `name`, `definition`, and optional `make_default`.
* `PATCH /v1/personas/{slug}` edits a custom persona or changes the default.
* `DELETE /v1/personas/{slug}` deletes a custom persona.

Editing or deleting the system persona returns `409 system_persona_immutable`.

Describe who to keep and explicit exclusions. For example:

```json theme={null}
{
  "name": "Marketing leaders",
  "definition": "Heads of marketing, growth or demand generation with purchasing influence. Exclude agencies, freelancers and junior individual contributors."
}
```

Persona selection changes the result, never the flat 1-credit price. A successful job with zero
matches is still a completed and charged company analysis.