For developers
Xpensiv API.
Create an API key in the console. Send it as a Bearer token. Keys are stored as hashes and shown only once.
Quickstart
- Sign in and create an API key. Copy it when it appears: it is shown once.
- In a terminal, run
export XPENSIV_API_KEY="xpk_..."with your key. - Start a check, wait for it to finish (usually one to three minutes), then read the findings. The script below does all three.
export XPENSIV_API_KEY="xpk_your_key"
RESP=$(curl -s -X POST https://xpensiv.si/api/v1/checks \
-H "Authorization: Bearer $XPENSIV_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://example.com"}')
ID=$(echo "$RESP" | sed -n 's/.*"id":"\([^"]*\)".*/\1/p')
if [ -z "$ID" ]; then echo "$RESP"; else
echo "check $ID started"
for i in $(seq 1 36); do
curl -s https://xpensiv.si/api/v1/checks/$ID -H "Authorization: Bearer $XPENSIV_API_KEY" | grep -qE '"status":"(completed|failed)"' && break
sleep 10
done
curl -s https://xpensiv.si/api/v1/checks/$ID/result -H "Authorization: Bearer $XPENSIV_API_KEY"
fiRun a check
curl -X POST https://xpensiv.si/api/v1/checks \
-H "Authorization: Bearer $XPENSIV_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://example.com"}'Replies 202 with {"id":"…","status":"queued","statusUrl":"…","resultUrl":"…"}.
Poll status
curl https://xpensiv.si/api/v1/checks/CHECK_ID \
-H "Authorization: Bearer $XPENSIV_API_KEY"Replace CHECK_ID with the id from the first call. Status is queued, running, completed or failed. Poll every 10 seconds.
Get findings
curl https://xpensiv.si/api/v1/checks/CHECK_ID/result \
-H "Authorization: Bearer $XPENSIV_API_KEY"Result JSON includes verdict, findings (region, severity, skill, evidence, fix and prompt; skill names the core design skill the finding comes from), screenshots and Lighthouse scores. Requests are rate limited and subject to account audit quota. A missing or wrong key returns 401; a bad URL returns 400 with an example.
MCP endpoint
Streamable HTTP endpoint: https://mcp.xpensiv.si. Tools: check_app, get_check and list_checks. OAuth metadata is at /.well-known/oauth-authorization-server. Developer clients may authenticate with an API key. Ready-made configs for Cursor, Claude Code and Codex are in Connect your agent.