Request a review.
A human reviewer takes the URL and returns a same-day, structured verdict. Pick the path that fits how you — or your agent — buys.
If your agent has a wallet, you can simply point it at us with one command.
Spend authority can come from a Stripe Shared Payment Token, a single-use Issuing card from Link’s Wallet for Agents, or a buyer-issued API key. The agent calls the endpoint, we charge the payment instrument once, we return a job ID, and we deliver the structured result to the webhook.
Request
POST /v1/reviews
One request creates the review, charges the buyer, and queues the reviewer. The agent does not need to handle Stripe Checkout, OAuth, or human confirmation flows.
curl -X POST https://api.uiopsy.com/v1/reviews \
-H "Authorization: Bearer $UIOPSY_API_KEY" \
-H "X-Stripe-Payment-Token: $STRIPE_SHARED_PAYMENT_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"target_url": "https://preview.myapp.com/pricing",
"pack": "starter",
"urgency": "today",
"focus": ["clarity", "trust", "conversion"],
"access_notes": "no login required",
"webhook_url": "https://myapp.com/uiopsy/webhook",
"customer": {
"name": "Buyer Agent",
"email": "agent@myapp.com",
"company": "MyApp"
}
}'Response
Synchronous response.
The POST returns immediately with a review ID, the amount charged, and an ETA. The reviewer is notified out-of-band.
{
"review_id": "rev_01HZX9...",
"status": "queued",
"amount_charged_cents": 24900,
"currency": "usd",
"delivery_eta": "2026-05-08T18:00:00Z",
"thread_id": "thr_01HZX9...",
"webhook_url": "https://myapp.com/uiopsy/webhook"
}Delivery
Webhook delivery.
When the human reviewer submits the verdict, we sign and POST the structured payload to your webhook. Score, summary, ranked issues, attachment URLs.
- HMAC-SHA256 signature in
X-Uiopsy-Signature. - Idempotency key in
X-Uiopsy-Idempotency-Key. - Retries with exponential backoff for 24 hours.
- 200/2xx ack required to stop retries.
Already set up over MCP?
If you ran the setup on the docs page, your agent already has the uiopsy_request_review tool. Add a payment-token env var to the same MCP server config and the existing tool call gets paid authority.
{
"tools": {
"uiopsy_request_review": {
"transport": "https",
"endpoint": "https://api.uiopsy.com/v1/reviews",
"auth": {
"bearer_env": "UIOPSY_API_KEY",
"payment_token_env": "STRIPE_SHARED_PAYMENT_TOKEN"
}
}
}
}Need an API key?
During the concierge launch we issue API keys manually. Tell us who the buyer is and which agent will be calling, and we’ll route a key.