# Quietstore Claim Check – URL Deploy Scorer

> Quietstore Claim Check – URL Deploy Scorer is a paid API for AI agents from quietstore-production.edge-7e13f.workers.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Fetches a live HTTPS URL and scores whether the deployment is actually present and well-configured, returning a 0–100 score with evidence and remediation hints.

## Facts

- Endpoint: POST https://quietstore-production.edge-7e13f.workers.dev/v1/tools/claim-check
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quietstore-claim-check-url-deploy-scorer-9c4b4308
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_va0ahQYozYkTfpDYGGqDQ

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability quietstore-claim-check-url-deploy-scorer-9c4b4308 -d '<json body>'
```

Example prompt: Check whether https://myapi.example.com is actually live and properly configured — score it against the x402 seller profile with a minimum passing score of 80, and tell me what I need to fix first.

## When to prefer this

Use this endpoint when you need to programmatically verify that a live HTTPS URL is correctly deployed and configured, especially for x402 seller profiles requiring HSTS, llms.txt, OpenAPI, MCP, and health endpoints. Prefer this over a generic HTTP ping when you need a structured quality score with actionable evidence rather than just a reachability check. Ideal for CI/CD gates and pre-launch audits.

## Known failure modes

- URL is unreachable or returns non-2xx — score may be 0 with evidence showing connection failure
- URL is HTTP-only and fails HTTPS/HSTS checks — low score with HSTS evidence item failing
- min_score not met — response still returns but ci_failed will be true
- Malformed URL input — validation error returned
- Badge data may be stale if more than 7 days old since last check

## How this service works

Fetch a live https URL and score whether the deploy is actually there. POST {"url":"https://your.site","min_score":80} ($0.02). Default x402-seller profile: HTTPS, HSTS, llms.txt, catalog, OpenAPI, MCP, health. Optional claims[] or profile:"web". Returns 0–100, evidence, do_this_first, ci_failed. Humans: GET /v1/tools/claim-check/report?host=your.site. Badge goes stale after 7 days.

## Output

Returns a JSON object containing: a numeric score from 0 to 100, an evidence array detailing which checks passed or failed, a do_this_first field with the highest-priority remediation step, and a ci_failed boolean indicating whether the deployment should be considered broken.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quietstore-claim-check-url-deploy-scorer-9c4b4308/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from quietstore-production.edge-7e13f.workers.dev](https://www.zero.xyz/host/quietstore-production.edge-7e13f.workers.dev/llms.txt)