Probely Developers

{
  "service_type": "platform",
  "base_url": "https://probely.com",
  "auth_method": "api_key",
  "auth_config": {
    "header": "Authorization",
    "scheme": "Bearer",
    "note": "API key obtained from Probely account settings; used against probely.com/api/ endpoints"
  },
  "endpoints": [
    {
      "name": "REST API base",
      "path": "/api/",
      "method": "GET",
      "description": "REST API for scanning and vulnerability management (targets, scans, findings). Exact paths not fully documented in source content."
    }
  ],
  "pricing_model": {
    "type": "subscription",
    "details": {
      "model": "SaaS subscription for Agile teams",
      "note": "Web vulnerability scanning suite sold as subscription; tiers vary by number of targets/scans"
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Continuous web application vulnerability scanning",
    "Vulnerability lifecycle management (triage, assignment, tracking)",
    "Agile team integration for security findings",
    "Web application security testing",
    "Finding reporting and workflow"
  ],
  "raw_analysis": "Probely is a commercial SaaS platform offering a Web Vulnerability Scanning suite targeted at Agile development teams. It performs continuous scanning of web applications and provides tools to manage the lifecycle of discovered vulnerabilities — triage, assignment, tracking, and resolution — intended to integrate into agile/dev workflows. The service is categorized as 'api', implying it exposes a documented REST API (base at probely.com/api/) that allows programmatic access to scans, targets, and findings, authenticated via API key/Bearer token. The company positions itself for teams wanting continuous, workflow-integrated application security testing, roughly in the DAST (Dynamic Application Security Testing) space, competing with tools like Detectify, Intruder, and OWASP ZAP-based solutions. The platform is mature enough to serve as a commercial product with subscription pricing. However, the source content is truncated and does not enumerate specific API endpoints, schemas, or rate limits, so those must be confirmed from Probely's official developer documentation."
}

2/3 tests passed

{
  "overall": 72,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 7.0,
    "response_parseability": 7.5,
    "error_clarity": 6.0,
    "doc_quality": 7.0,
    "auth_simplicity": 7.0,
    "latency": 9.0,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "model": "saas_subscription",
    "has_free_tier": false,
    "is_usage_based": true,
    "is_enterprise_gated": false,
    "est_entry_monthly_usd": null,
    "note": "Subscription per targets/scans; public price not exposed in probe"
  },
  "issues": [
    "No /llms.txt endpoint (404) — agents cannot cheaply ingest a machine-readable platform summary",
    "No publicly surfaced free tier or trial detail in probe data",
    "Pricing not machine-readable; tiers described qualitatively only",
    "No public API docs endpoint detected in checks (only website, robots, llms.txt probed)"
  ],
  "recommendations": [
    "Publish /llms.txt with concise value prop, pricing pointers, and API/docs links to boost agent readability",
    "Expose a machine-readable pricing/plans endpoint or structured JSON pricing page",
    "Add a public trial or sandbox tier to improve first-try success for agent-recommended onboarding",
    "Document rate limits, auth flow (API keys/OAuth/SSO), and error codes in public docs to raise error_clarity",
    "Highlight integrations (Jira/Slack/CI) prominently as structured data to lift parseability score"
  ]
}