Storecove API

{
  "service_type": "platform",
  "base_url": "https://storecove.com",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "e-invoicing",
    "Peppol Access Point",
    "invoice delivery",
    "invoice receiving",
    "document exchange"
  ],
  "raw_analysis": "Storecove is a Dutch e-invoicing platform and Peppol Access Point provider. It enables businesses and software vendors to send and receive structured electronic invoices and documents across networks such as Peppol, and via other e-invoicing standards and national networks. The company positions itself as an API-first e-invoicing infrastructure provider, aimed at ERP, accounting, and business software vendors who want to embed e-invoicing capabilities into their products, as well as enterprises needing compliant invoice exchange.\n\nMaturity: Storecove is an established vendor in the European e-invoicing space, operating as a certified Peppol Access Point. The platform has been active for years and is integrated by multiple accounting and ERP software providers.\n\nThe service does expose an API (the Storecove API), which is its primary product. The API is intended for programmatic submission, retrieval, and management of e-invoices and related documents. However, the provided metadata does not include a public OpenAPI/REST endpoint list, auth details, rate limits, or pricing tiers; those details would require accessing their developer documentation at https://www.storecove.com/en/developers/ or similar.\n\nKey capabilities include: sending invoices via Peppol and other networks, receiving invoices, accessing invoice status and delivery receipts, managing legal entities and network identifiers, and supporting multiple e-invoicing formats (UBL, CII, etc.). Integrations are primarily through the API, with SDKs and plugins for common platforms.\n\nBecause the details supplied are minimal, fields such as auth_method, pricing_model, rate_limits, and endpoints are marked unknown or empty rather than inferred."
}

1/3 tests passed

{
  "overall": 47,
  "dimensions": {
    "token_efficiency": 6.5,
    "first_try_success": 5.0,
    "response_parseability": 4.0,
    "error_clarity": 4.0,
    "doc_quality": 4.5,
    "auth_simplicity": 3.5,
    "latency": 6.0,
    "consistency": 5.5
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "No pricing information exposed in surface scans. Peppol Access Point services typically involve per-document or subscription fees but this platform does not surface any public pricing, tiers, or trial details."
  },
  "issues": [
    "No /robots.txt (404) — crawlers and agents get no crawl policy signals.",
    "No /llms.txt (404) — no machine-readable summary for LLM agents.",
    "No documented pricing, even at a high level — a blocker for users evaluating fit before signup.",
    "Missing structured onboarding signals (no OpenAPI spec, no public developer docs referenced in surface scan).",
    "Several responses were 404s served as HTML that does not clearly indicate the resource was missing vs. an error — error clarity is weak.",
    "TYPO3-based marketing site with no visible API/developer surface; integration path for agents is unclear.",
    "Auth model for the platform (Peppol Access Point) is not described — users cannot predict onboarding cost.",
    "Latency on main page (~1s) is acceptable but not fast; robots/llms probes were faster, suggesting some page-level overhead."
  ],
  "recommendations": [
    "Publish a /llms.txt with a concise value prop, Peppol capability summary, pricing model, and links to docs.",
    "Add a /robots.txt with an explicit AI-agent crawl policy.",
    "Expose machine-readable pricing (JSON/YAML) at a stable path so agents can answer 'what does it cost?' without scraping marketing pages.",
    "Publish an OpenAPI (or at least AsyncAPI) spec for invoice submission/receipt endpoints.",
    "Provide a developer quickstart with sandbox credentials and a magic-link or API-key auth flow to reduce onboarding friction.",
    "Ensure 404 pages return proper status semantics and a clear error body, not generic HTML.",
    "Add a status page link and uptime SLA documentation to improve consistency perception.",
    "Cache/optimize the marketing page to bring TTFB under 500ms."
  ]
}