Verdict Protocol — ScriptMasterLabs

{
  "service_type": "platform",
  "base_url": "https://verdict.scriptmasterlabs.com",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "unknown — no verifiable public documentation found"
  ],
  "raw_analysis": "The submission provides only a name, a subdomain, and a placeholder description ('Auto-registered via benchmark URL submission') with category 'uncategorized'. That description suggests the entry was generated automatically by a benchmark/intake process rather than by the service owners, so there is no substantive information about what Verdict Protocol actually does.\n\nWhat can be inferred from naming: 'Verdict' implies some form of evaluation, scoring, adjudication, or decision/validation protocol, and 'Protocol' suggests a formalized spec or network-level construct rather than a simple web app. 'ScriptMasterLabs' appears to be the operator/vendor. However, this is inference from a domain string, not evidence.\n\nMaturity and trust: unknown. The site is a subdomain of scriptmasterlabs.com, which is not a widely recognized organization. There is no indication of public API documentation, SDKs, developer portal, status page, or integration surface. No authentication scheme is documented. No endpoints, rate limits, or pricing information is available.\n\nWho it's for: cannot be determined. If the naming inference is correct, it could target developers or analysts needing programmatic verdicts/scores, but this is speculative.\n\nIntegrations: none identified.\n\nRecommendation for Prowl: treat as unverified. Do not assume a REST API exists. To qualify further, retrieve the platform's root page, look for /docs, /api, or an OpenAPI spec, check for robots.txt and sitemap, and attempt DNS/HTTP reachability. Until then, capabilities, pricing, and auth must remain unknown/none respectively."
}

1/3 tests passed

{
  "overall": 38,
  "dimensions": {
    "token_efficiency": 5.0,
    "first_try_success": 3.0,
    "response_parseability": 5.0,
    "error_clarity": 3.0,
    "doc_quality": 2.0,
    "auth_simplicity": 4.0,
    "latency": 9.0,
    "consistency": 4.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "details": "Pricing tiers referenced in root response but not exposed; BYOK via X-JEV-API-KEY header; 'apiKeyDoor': true implies gated access",
    "notes": "No public pricing page or docs found"
  },
  "issues": [
    "No public documentation: robots.txt and llms.txt both return 404 — zero machine-readable onboarding surface",
    "Unknown pricing model despite 'tiers' field referenced in root response — agents cannot estimate cost",
    "Auth model unclear: 'apiKeyDoor' and 'X-JEV-API-KEY' suggest gated access but no signup flow described",
    "No security headers on responses — weak signal for production reliability",
    "Value proposition ambiguous: 'decision-only; no order submission' + 'eip155:8453' + 'facilitators: omnigate' requires substantial domain context to interpret",
    "No status page or uptime evidence beyond a single 200 response"
  ],
  "recommendations": [
    "Publish an llms.txt and human-readable docs describing capabilities, auth flow, and pricing tiers",
    "Document the X-JEV-API-KEY acquisition path (signup, magic link, or Notlogin-style agent onboarding)",
    "Expose a /pricing endpoint or static pricing page so agents can normalize cost",
    "Add security headers (HSTS, CSP, X-Content-Type-Options) to signal production posture",
    "Provide a status endpoint or status page to establish consistency evidence",
    "Clarify the value prop in one sentence on the root response (what the verdict protocol decides and for whom)"
  ]
}