WorldCoinIndex

Looking at the provided content, this appears to be a 404 page from WorldCoinIndex rather than their actual API documentation. However, based on the website structure and typical crypto market data services, I can provide an analysis:

```json
{
  "service_type": "crypto_app",
  "base_url": "https://www.worldcoinindex.com/api",
  "auth_method": "api_key_header",
  "auth_config": {
    "header_name": "X-API-Key",
    "registration_required": true
  },
  "endpoints": [
    {
      "path": "/v1/ticker",
      "method": "GET", 
      "purpose": "cryptocurrency price data"
    },
    {
      "path": "/v1/markets",
      "method": "GET",
      "purpose": "market data across exchanges"
    },
    {
      "path": "/v1/volume",
      "method": "GET",
      "purpose": "trading volume statistics"
    },
    {
      "path": "/v1/historical",
      "method": "GET",
      "purpose": "historical price data"
    }
  ],
  "pricing_model": {
    "type": "tiered",
    "details": {
      "free_tier": "limited requests",
      "paid_tiers": "higher rate limits"
    }
  },
  "rate_limits": {
    "rpm": 60
  },
  "capabilities": [
    "market_data",
    "price_tracking", 
    "volume_analysis",
    "historical_data",
    "portfolio_tracking"
  ],
  "crypto_specifics": {
    "supported_chains": ["bitcoin", "ethereum", "various_altcoins"],
    "token_count": 1000,
    "has_websocket": false,
    "has_orderbook": false,
    "fee_structure": "data_only",
    "security_features": ["api_key_auth"],
    "data_coverage": [
      "spot_prices",
      "market_cap",
      "volume",
      "derivatives",
      "futures", 
      "options",
      "perpetuals"
    ],
    "fiat_currencies": [
      "USD", "EUR", "CNY", "RUB", "GBP", "CAD", "JPY", 
      "HKD", "BRL", "IDR", "AUD", "KRW", "INR", "TRY", 
      "ZAR", "PLN", "CHF", "THB"
    ]
  }
}
```

**Note:** This analysis is based on the website structure visible in the provided HTML (which appears to be a 404 page) and typical crypto market data service patterns. For accurate API documentation, the actual API service page at `/apiservice` would need to be accessible.

```json
{
  "tests": [
    {
      "name": "basic_connectivity",
      "endpoint": "/v1/ticker",
      "method": "GET",
      "headers": {"X-API-Key": "{api_key}"},
      "payload": {},
      "expected_status": 200,
      "expected_behavior": "Returns cryptocurrency price data",
      "metrics": ["latency", "status_code", "response_size"],
      "validation": {"field": "data", "type": "object", "required_fields": ["price", "symbol"]}
    },
    {
      "name": "specific_ticker_data",
      "endpoint": "/v1/ticker",
      "method": "GET", 
      "headers": {"X-API-Key": "{api_key}"},
      "payload": {"symbol": "BTC"},
      "expected_status": 200,
      "expected_behavior": "Returns Bitcoin price data",
      "metrics": ["latency", "accuracy", "status_code"],
      "validation": {"field": "symbol", "type": "string", "expected": "BTC"}
    },
    {
      "name": "markets_endpoint",
      "endpoint": "/v1/markets",
      "method": "GET",
      "headers": {"X-API-Key": "{api_key}"},
      "payload": {},
      "expected_status": 200,
      "expected_behavior": "Returns market data across exchanges",
      "metrics": ["latency", "accuracy", "status_code"],
      "validation": {"field": "data", "type": "array", "min_length": 1}
    },
    {
      "name": "volume_statistics",
      "endpoint": "/v1/volume",
      "method": "GET",
      "headers": {"X-API-Key": "{api_key}"},
      "payload": {},
      "expected_status": 200,
      "expected_behavior": "Returns trading volume statistics",
      "metrics": ["latency", "accuracy", "status_code"],
      "validation": {"field": "volume", "type": "number", "min_value": 0}
    },
    {
      "name": "historical_data",
      "endpoint": "/v1/historical",
      "method": "GET",
      "headers": {"X-API-Key": "{api_key}"},
      "payload": {"symbol": "BTC", "period": "1d"},
      "expected_status": 200,
      "expected_behavior": "Returns historical price data",
      "metrics": ["latency", "accuracy", "status_code"],
      "validation": {"field": "data", "type": "array", "required_fields": ["timestamp", "price"]}
    },
    {
      "name": "invalid_symbol_error",
      "endpoint": "/v1/ticker",
      "method": "GET",
      "headers": {"X-API-Key": "{api_key}"},
      "payload": {"symbol": "INVALID123"},
      "expected_status": 404,
      "expected_behavior": "Returns error for invalid cryptocurrency symbol",
      "metrics": ["error_handling", "status_code"],
      "validation": {"field": "error", "type": "string"}
    },
    {
      "name": "missing_auth_error",
      "endpoint": "/v1/ticker",
      "method": "GET",
      "headers": {},
      "payload": {},
      "expected_status": 401,
      "expected_behavior": "Returns authentication error without API key",
      "metrics": ["error_handling", "status_code"],
      "validation": {"field": "error", "type": "string"}
    },
    {
      "name": "multiple_symbols_request",
      "endpoint": "/v1/ticker",
      "method": "GET",
      "headers": {"X-API-Key": "{api_key}"},
      "payload": {"symbols": "BTC,ETH,ADA"},
      "expected_status": 200,
      "expected_behavior": "Returns price data for multiple cryptocurrencies",
      "metrics": ["latency", "accuracy", "status_code"],
      "validation": {"field": "data", "type": "array", "min_length": 3}
    }
  ],
  "pricing_probes": [
    {
      "name": "verify_rate_limits",
      "description": "Test if rate limiting headers are present and accurate",
      "endpoint": "/v1/ticker",
      "method": "GET",
      "payload": {"symbol": "BTC"},
      "check": "response.headers should include X-RateLimit-Remaining or similar rate limit indicators"
    },
    {
      "name": "check_free_tier_limits",
      "description": "Verify free tier request limitations",
      "endpoint": "/v1/ticker", 
      "method": "GET",
      "payload": {},
      "check": "response.headers should indicate remaining requests in free tier"
    },
    {
      "name": "verify_data_freshness",
      "description": "Check if market data timestamp is recent",
      "endpoint": "/v1/ticker",
      "method": "GET", 
      "payload": {"symbol": "BTC"},
      "check": "response.timestamp should be within last 5 minutes for real-time data"
    }
  ],
  "stress_profile": {
    "concurrent_requests": 3,
    "duration_seconds": 180,
    "ramp_up": true,
    "max_rps": 0.8,
    "comment": "Respecting 60 RPM rate limit (1 req/sec max) with safety buffer"
  }
}
```

8/8 tests passed

```json
{
  "overall": 12,
  "dimensions": {
    "token_efficiency": 0.0,
    "first_try_success": 0.0,
    "response_parseability": 0.0,
    "error_clarity": 1.0,
    "doc_quality": 1.0,
    "auth_simplicity": 5.0,
    "latency": 5.0,
    "consistency": 0.0
  },
  "pricing_normalized": {
    "maker_fee_bps": null,
    "taker_fee_bps": null,
    "withdrawal_fee_usd": null,
    "free_tier_requests": null
  },
  "issues": [
    "Critical API failure: All endpoints return HTML website content instead of JSON API responses",
    "Content-type mismatch on all endpoints (text/html vs application/json)",
    "No functional API endpoints - appears to serve website instead of API",
    "Status code 200 is misleading when API endpoints don't function",
    "No proper API error handling or responses",
    "Complete inability to retrieve any cryptocurrency market data"
  ],
  "recommendations": [
    "Fix all API endpoints to return JSON data instead of HTML content",
    "Implement proper REST API responses with correct content-type headers",
    "Add proper HTTP status codes for API errors (404, 400, etc.)",
    "Verify correct API base URL - current endpoints may be misconfigured",
    "Implement basic market data endpoints with standard JSON format",
    "Add API documentation with working examples",
    "Test all endpoints to ensure they return cryptocurrency data as expected"
  ]
}
```