WeGA API

```json
{
  "service_type": "platform",
  "base_url": "https://weber-gesamtausgabe.de",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [
    {
      "path": "/api/v1/openapi.json",
      "method": "GET",
      "description": "OpenAPI specification for WeGA API version 1.1.0 (current version)"
    }
  ],
  "pricing_model": {
    "type": "free",
    "details": {
      "note": "Academic/research digital edition project, publicly accessible"
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Access to scholarly data from the Carl Maria von Weber Gesamtausgabe (complete edition)",
    "Digital humanities research data",
    "OpenAPI-documented REST interface",
    "Full-text and metadata access to Weber's works, letters, and writings",
    "Public scholarly edition access"
  ],
  "raw_analysis": "The WeGA (Weber-Gesamtausgabe) API is the programmatic interface to the Carl Maria von Weber Complete Edition, a scholarly digital humanities project. The base URL https://weber-gesamtausgabe.de hosts both the human-facing digital edition and the accompanying API.\n\nKey findings from the provided metadata:\n\n1. **Versioning/deprecation**: The description explicitly carries a DEPRECATION WARNING stating that this described API specification version is outdated and superseded by version 1.1.0, accessible at https://weber-gesamtausgabe.de/api/v1/openapi.json. This indicates an actively maintained, versioned API with a published OpenAPI (Swagger) specification — a strong signal of maturity and good developer documentation.\n\n2. **OpenAPI spec available**: The presence of a machine-readable OpenAPI document (v1.1.0) means the full endpoint list, schemas, and parameter definitions can be retrieved programmatically. I could not enumerate individual endpoints from the truncated description alone, so the endpoints array reflects only the known spec URL.\n\n3. **Authentication**: No authentication details are indicated. Scholarly edition APIs of this type are typically open/public (no API key), so auth_method is set to 'none' pending confirmation from the OpenAPI spec itself.\n\n4. **Pricing**: Free — this is an academic/research infrastructure project (likely publicly funded), not a commercial service.\n\n5. **Target audience**: Musicologists, historians, digital humanities researchers, and developers building scholarly applications around Weber's corpus.\n\n6. **Maturity**: The explicit versioning (v1.0 deprecated → v1.1.0) and OpenAPI publication suggest a maintained and reasonably mature API, though it is a niche domain-specific service rather than a general-purpose platform.\n\nRecommended next step: fetch https://weber-gesamtausgabe.de/api/v1/openapi.json to enumerate concrete endpoints, response schemas, and any rate-limiting or auth requirements, then update this record accordingly. The truncated 'For feedba...' text appears to be a 'For feedback...' contact note, reinforcing that this is a community/academic project rather than a commercial vendor."
}
```

2/3 tests passed

{
  "overall": 46,
  "dimensions": {
    "token_efficiency": 5.0,
    "first_try_success": 6.0,
    "response_parseability": 4.0,
    "error_clarity": 4.0,
    "doc_quality": 4.0,
    "auth_simplicity": 9.0,
    "latency": 4.0,
    "consistency": 6.0
  },
  "pricing_normalized": {
    "model": "free",
    "notes": "Publicly accessible academic digital edition project; no paid tier expected."
  },
  "issues": [
    "No /llms.txt (404) — agents lack a machine-readable entry point describing the platform",
    "Robots.txt is a large user-agent blocklist; unclear how many AI agents are actually allowed, which creates ambiguity for agent crawlers",
    "No documented LLM-facing surface beyond a generic OpenAPI mention; actual API endpoints/schema not confirmed in checks",
    "Website latency (~878ms main page, ~495ms for 404) is mediocre for agent loops",
    "Help/docs quality unverified — no example of getting-started content or limitation documentation in the check results",
    "Content is German-first (lang=\"de\"); agent-facing English docs may be sparse"
  ],
  "recommendations": [
    "Publish an /llms.txt describing the OpenAPI surface, auth model (none/key), rate limits, and example queries",
    "Provide a stable JSON index endpoint listing works, letters, and writings with IDs for direct agent retrieval",
    "Clarify the robots.txt policy for AI agents — a single explicit allow/deny line is more token-efficient than a long bot list",
    "Reduce main-page latency below 500ms; ensure API responses are consistently fast and cacheable",
    "Add a concise English quickstart with curl examples and error-code documentation",
    "Expose an OpenAPI/Swagger spec at a well-known path (e.g., /openapi.json) with clear response schemas"
  ]
}