What you need
- A site in Senaste with its domain verified and a panel of personas.
- An API key, made in your account under API keys. It starts with uxp_. Open API keys
- Credits on your balance: one per persona for up to 20 steps.
- An agent that can run shell commands or send HTTP requests, such as Claude Code, Cursor or Codex.
Keep the key out of the code
Put the key in an environment variable, for example SENASTE_API_KEY, in your shell or in the agent’s secret settings. Do not paste it into the prompt or commit it: anyone with the key can spend your credits. You can revoke a key at any time on the same page.
The prompt
Paste this into your agent with your domain in place of example.com. It asks before it spends credits, and it treats every note as a lead to check, not as a fact. It is in English for every agent; ask for the report in your language if you like.
Test my live site with Senaste and fix what stops people.
API: https://senaste.ai/api/v1. The key is in the environment variable SENASTE_API_KEY; send it as the header "Authorization: Bearer $SENASTE_API_KEY". Never print the key or write it to a file.
1. GET /sites and find the site with the domain example.com. If it is missing or "verified" is false, stop and tell me.
2. Count the personas in its "panel" with "enabled": true. The run costs that many credits (one per persona, up to 20 steps). Tell me the number and wait for my yes.
3. POST /runs with {"site": "<the site id>", "steps": 20} and keep the "id" from the reply.
4. GET /runs/<id> once a minute until "status" is done, failed, interrupted or cancelled.
5. Read results[].outcome and results[].notes. The notes are written by an AI model and some are wrong, so treat each blocker and major note as a lead: find the page in this codebase, confirm the problem is real, and fix it. Change nothing you cannot confirm.
6. Report back: each note you acted on and the file you changed, then the notes you skipped and why.What comes back
For each persona the agent gets its outcome (reached the goal, gave up, stopped at a form, ran out of steps), the pages it opened and its notes, each with a severity (blocker, major, minor or praise), the page and what the persona saw. The full report with a screenshot of every step stays in your dashboard.
Test what you deployed
Senaste visits your site over the internet, so it tests the version that is live, or the one on a test host you verified, such as staging.example.com. A fix that is only on your laptop is not tested yet. Deploy first, then ask the agent to run the same panel again; the dashboard compares the new run with the last one.
Limits worth knowing
- Notes come from a model and some are wrong. That is why the prompt asks the agent to confirm each one in the code first.
- Runs go one at a time across the whole service, so yours may wait in the queue before it starts.
- The API allows 60 requests a minute. Checking a run once a minute is plenty.
- On a live site forms are not sent, so sign-up and payment are tested up to the last step.
