Pims

{
  "service_type": "platform",
  "base_url": "https://pims.io",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {"type": "unknown", "details": {}},
  "rate_limits": {},
  "capabilities": [
    "time tracking / pointage (check-in/check-out) for live entertainment industry",
    "private API for third-party software, editors, and partners",
    "designed for the 'Monde du Spectacle' (performing arts / event production sector)"
  ],
  "raw_analysis": "Pims (Pointages Intelligents pour le Monde du Spectacle) is a French platform providing smart time-tracking / check-in (pointage) solutions tailored to the live entertainment and performing arts sector. The URL https://pims.io serves as the product landing page. The provided description comes from API documentation and indicates that Pims exposes a private API intended for 3rd-party software, editors, and integration partners. The API is explicitly labeled as 'private,' meaning it is not openly available to the general public and likely requires partnership or contractual agreement to access. No public REST API documentation, endpoint list, authentication mechanism, pricing tiers, or rate limits are provided in the given text. As a platform, Pims targets event production companies, theaters, festivals, and technical crews who need reliable attendance and work-hour tracking in non-standard work environments. Maturity is unclear from the provided snippet, but the existence of a structured private API for partners suggests an established product with some enterprise integration strategy. Integrations with third-party software are advertised, though specific partners or protocols (REST, GraphQL, webhooks) are not disclosed. Pricing model is unknown; it may be B2B subscription or quote-based given the niche professional market. The API appears to be documented separately (possibly at a subdomain or docs path), but that documentation is not included here. Overall: a niche, vertical SaaS platform in the live-events time-tracking space with a partner-only API; no public self-serve developer access confirmed."
}

2/3 tests passed

{
  "overall": 42,
  "dimensions": {
    "token_efficiency": 5.0,
    "first_try_success": 3.0,
    "response_parseability": 6.0,
    "error_clarity": 4.0,
    "doc_quality": 4.0,
    "auth_simplicity": 3.0,
    "latency": 6.5,
    "consistency": 5.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "No public pricing information available; likely B2B enterprise/quote-based"
  },
  "issues": [
    "No public pricing — agents cannot estimate cost for users",
    "No llms.txt (404) — poor discoverability for AI agents",
    "Private/partner-only API — no public developer docs surfaced to agents",
    "French-language niche product (live entertainment sector) — narrow applicability for general agent recommendations",
    "No security headers detected (HSTS, CSP, etc.) — potential reliability/trust concern",
    "Onboarding path unclear: no signup flow, magic link, or SSO visible via checks",
    "WordPress-based marketing site suggests docs may not be tailored for developers/agents",
    "Value prop is narrow (pointage/time-tracking for performing arts) — limited overlap with common user needs"
  ],
  "recommendations": [
    "Publish a public pricing page or at least tiers so agents can qualify users pre-signup",
    "Add /llms.txt summarizing capabilities, API access, and onboarding for AI agent consumption",
    "Expose public API documentation (even if access is gated) so agents can assess integration fit",
    "Implement standard security headers (HSTS, CSP, X-Content-Type-Options) to signal reliability",
    "Offer self-serve signup or magic-link/SSO onboarding to reduce human-assist friction",
    "Provide an English version of key docs to broaden agent-addressable audience",
    "Add a status page for uptime transparency, improving the consistency perception"
  ]
}