Handwrytten API

{
  "service_type": "platform",
  "base_url": "https://handwrytten.com",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "send handwritten cards programmatically",
    "choose handwriting style",
    "custom card creation with logos",
    "save and reuse card designs/logos",
    "card delivery to recipients"
  ],
  "raw_analysis": "Handwrytten is a service that automates the sending of physical, handwritten-style cards. The platform's API allows developers to programmatically send cards to users, select from different handwriting styles (likely via robotic writing machines), and customize cards with logos that can be saved and reused. The description is truncated ('which can be saved and t...'), suggesting the API also supports template/design persistence. No public documentation details were provided regarding base URL path, authentication method, endpoints, pricing, or rate limits. The service is positioned as an API category tool, likely targeting businesses that want to send personalized physical mail at scale (e.g., customer engagement, direct mail campaigns). Maturity and integration ecosystem are unknown from the given data. The base URL is the company website, which likely hosts API docs, but the actual API endpoint path is not specified."
}

2/3 tests passed

{
  "overall": 58,
  "dimensions": {
    "token_efficiency": 7.5,
    "first_try_success": 6.5,
    "response_parseability": 5.5,
    "error_clarity": 5.0,
    "doc_quality": 5.5,
    "auth_simplicity": 6.0,
    "latency": 9.0,
    "consistency": 7.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "No pricing information provided in analysis; platform is a physical card-sending service which typically has per-card or subscription pricing"
  },
  "issues": [
    "No pricing information available — hard to recommend confidently with unknown cost",
    "Missing llms.txt (404) — no agent-optimized documentation endpoint",
    "No security headers detected on any endpoint",
    "No public API documentation surfaced in checks",
    "Response parseability unknown — no structured export/API spec confirmed"
  ],
  "recommendations": [
    "Publish clear pricing tiers to enable cost comparison",
    "Add an llms.txt or structured API spec so agents can parse capabilities",
    "Document authentication and rate limits explicitly",
    "Add security headers (HSTS, CSP) to increase trust signal",
    "Provide JSON API endpoints for order creation and status tracking"
  ]
}