Saram documentation
Saram runs synthetic personas through your product in a real browser. It reports the defects that reproduce, and what the personas thought, with the evidence behind each.
What is here
Section titled “What is here”- Quickstart: from a dashboard API key to a first run over HTTP, and reading its issues, verdicts and session video.
- Connect your coding agent: Claude Code, Cursor or Codex on the Saram MCP server, by signing in or with an API key, then a first run from validating its spec to reading what it found.
- Guides: the run spec, field by field; issues vs persona feedback, and what to file as a ticket; providers and your own keys, for who bills the model calls; and usage and billing, for the plans, the balance and the usage report.
- HTTP API reference: every public operation of the Saram API at
https://api.saram.sh, with request and response schemas and a client to try requests. Requests authenticate withAuthorization: Bearer <credential>, where the credential is a Saram API key (sk_saram_...) or a signed-in person’s access token. - MCP tools: the tools of the Saram MCP server at
https://api.saram.sh/mcp, what the server tells a connecting agent, and each tool’s arguments. - Docs for agents: every page here as Markdown, and the
llms.txtindex.
What a run gives you
Section titled “What a run gives you”A run produces two kinds of output, and they are not interchangeable:
- Issues are defects, gated on reproduction. An issue that reproduced without the persona layer is safe to act on by itself.
- Verdicts and opportunities are persona feedback: subjective, linked to evidence, and scored by agreement across personas. They are advisory, and are attributed to the persona rather than stated as fact.