WikiPathways Webservices

{
  "service_type": "platform",
  "base_url": "https://wikipathways.org",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {"type": "free", "details": {}},
  "rate_limits": {},
  "capabilities": [
    "Pathway database browsing and search",
    "Pathway curation and editing (community wiki)",
    "Programmatic access to pathway data via web services",
    "Integration with biological databases (e.g., Ensembl, NCBI Gene)",
    "Content export in multiple formats (GPML, BioPAX, etc.)"
  ],
  "raw_analysis": "WikiPathways is a community-curated open database of biological pathways, primarily used in bioinformatics and systems biology research. It provides a web portal with API-like web services for programmatic access to pathway data. The platform is mature, established in 2008, and widely cited. Authentication is not required for data access. Pricing is free and open-source. Rate limits are not publicly documented. The API endpoints are not listed in the provided content, but the site offers REST-like web services for querying pathways, genes, and species. This analysis focuses on its role as a platform for biological pathway data sharing and analysis."
}

2/3 tests passed

{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 7.0,
    "response_parseability": 7.0,
    "error_clarity": 5.5,
    "doc_quality": 6.5,
    "auth_simplicity": 8.0,
    "latency": 9.5,
    "consistency": 6.5
  },
  "pricing_normalized": {
    "model": "free",
    "cost_per_agent_call": 0.0,
    "notes": "Open community resource (WikiPathways), no paid tier."
  },
  "issues": [
    "No llms.txt — agents lack a machine-readable entry point describing capabilities, endpoints, and usage policy.",
    "robots.txt disallows /browse/* and contains a typo in the sitemap URL ('new.wikipathawys.org'), which can break crawlers and sitemap ingestion.",
    "No security headers reported (HSTS, CSP, etc.) — weakens trust signals for agent-mediated recommendations.",
    "Web-service/API details not surfaced in the check output; response_parseability depends on undocumented endpoints (GPML/BioPAX exports, web services) being discoverable.",
    "Documentation for programmatic access (API schemas, rate limits, error semantics) is not evident from the checked surfaces."
  ],
  "recommendations": [
    "Publish an llms.txt at the root describing capabilities, API/web-service endpoints, export formats, and acceptable use — this is the single highest-leverage change for agent adoption.",
    "Fix the sitemap URL typo and review the /browse/* robots disallow — it blocks agents from the core content surface.",
    "Add standard security headers (HSTS, CSP, X-Content-Type-Options) to improve trust scoring.",
    "Expose a documented, versioned JSON/web-service API for pathway search and retrieval alongside GPML/BioPAX, with explicit rate limits and error codes.",
    "Provide OpenAPI/Swagger specs for web services so agents can parse and call endpoints without guessing.",
    "Add a concise status/uptime page or health endpoint to reinforce reliability claims."
  ]
}