obono RKSV API

{
  "service_type": "platform",
  "base_url": "https://obono.at",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "RESTful API for virtual cash registers",
    "Receipt creation compliant with RKSV (Registrierkassensicherheitsverordnung)",
    "Austrian cash register security regulation compliance",
    "Virtual cash register management"
  ],
  "raw_analysis": "obono RKSV API is a RESTful API service provided by obono (https://obono.at), an Austrian company. It enables programmatic interaction with virtual cash registers and creation of receipts that are conformant with the Registrierkassensicherheitsverordnung (RKSV) — the Austrian Cash Register Security Ordinance that mandates cryptographic signing and recording of every cash register transaction for tax compliance. The service targets Austrian businesses, developers, and point-of-sale (POS) system integrators who need to meet legal requirements for electronic cash registers. The API is described as RESTful, with automatically generated documentation referenced. Specific endpoint paths, authentication method, pricing model, and rate limits are not provided in the available content. The platform appears mature enough to be offered as a dedicated category 'api' service, likely part of a broader obono product suite. Integration surface would primarily be for POS software, ERP systems, and tax compliance workflows in Austria."
}

2/3 tests passed

{
  "overall": 48,
  "dimensions": {
    "token_efficiency": 5.0,
    "first_try_success": 4.0,
    "response_parseability": 5.0,
    "error_clarity": 4.0,
    "doc_quality": 4.0,
    "auth_simplicity": 4.0,
    "latency": 9.0,
    "consistency": 6.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "transparency": "opaque",
    "note": "No pricing information surfaced in analysis; description lists capabilities only."
  },
  "issues": [
    "Pricing model is unknown/undocumented — agents cannot advise users on cost.",
    "Missing security headers on all probed endpoints (no HSTS, CSP, X-Content-Type-Options detected).",
    "No llms.txt or machine-readable capability manifest (404).",
    "Site is German-only (lang='de') and WordPress-based, limiting agent-readable structured info.",
    "Highly niche domain (Austrian RKSV compliance) — unclear API docs, auth flow, and error contract from probes.",
    "robots.txt is default WordPress boilerplate with no API-relevant guidance."
  ],
  "recommendations": [
    "Publish a public pricing page and expose it in machine-readable form (JSON schema or llms.txt).",
    "Add llms.txt with API base URL, auth method, and capability summary to enable agent onboarding.",
    "Add security headers (HSTS, CSP, X-Frame-Options) — table stakes for financial/compliance-adjacent services.",
    "Document authentication clearly (API keys vs OAuth) and provide SDK examples — agents need deterministic onboarding.",
    "Provide structured error responses (RFC 7807) with RKSV-specific error codes and remediation hints.",
    "Publish OpenAPI spec for the RKSV receipt/virtual-register endpoints to improve parseability and first-try success."
  ]
}