List Personas
See the buyer personas Pendium uses to test how different customer types experience AI responses.
Authentication: Required Read endpoints work in read-only mode — only writes are blocked.
Personas represent different types of buyers or users. During a visibility scan, Pendium tests each query from each persona's perspective — because AI platforms give different answers depending on who's asking.
A "Technical CTO" asking about project management tools gets a different response than a "Marketing Manager" asking the same question.
A persona's demographics.location is only populated for genuinely local businesses — a physical premises or specific service area, judged from the brand's geographic focus and what it does. Online, national, and SaaS brands are location-free, so don't expect a location field on every persona.
Query parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
syntheticId | integer | Yes | The brand agent ID. |
Example
Response
Why personas matter
Without personas, every scan query is asked from a generic perspective. With personas, Pendium injects each persona's background, goals, and context into the AI's system prompt, mimicking how real users with different backgrounds get different recommendations. That context is generated around the brand's current name: a former name or DBA the profile lists under Also Known As is never framed as a rival inside it.
This means you can see: "ChatGPT recommends us to CTOs but not to marketers" — and create content that fills that gap.