16
/100
prowl
Benchmarked Apr 06, 2026

CryptingUp

Cryptocurrency data

cryptodata crypto_app public
Benchmark Your API

Score Breakdown

Latency 7/10
Consistency 3/10
Error Clarity 2/10
Auth Simplicity 2/10
Documentation 1/10
Token Efficiency 1/10
First-Try Success 1/10
Parseability 1/10

Benchmark Analysis Log

Full LLM thinking from the 4-phase benchmark pipeline.

Analyze
Looking at the provided URL for CryptingUp, I can see that the domain `cryptingup.com` is currently parked for sale through HugeDomains.com. The content shows a domain parking page rather than any actual API documentation or crypto service.

Since the service appears to be unavailable and the domain is for sale, I cannot provide a proper analysis of CryptingUp's crypto application features, API endpoints, or capabilities.

```json
{
  "error": "service_unavailable",
  "message": "CryptingUp service appears to be unavailable - domain is parked for sale",
  "status": "inactive",
  "domain_status": "for_sale"
}
```

The analysis cannot proceed as there is no active crypto service or API documentation available at the provided URL.
Plan
```json
{
  "tests": [
    {
      "name": "test_service_availability",
      "endpoint": "/",
      "method": "GET",
      "headers": {},
      "payload": {},
      "expected_status": 200,
      "expected_behavior": "Check if service is available or if domain is parked",
      "metrics": ["latency", "status_code"],
      "validation": {"field": "content", "type": "string", "contains_any": ["hugeDomains", "domain for sale", "parked"]}
    },
    {
      "name": "test_api_root_access",
      "endpoint": "/api",
      "method": "GET",
      "headers": {},
      "payload": {},
      "expected_status": 404,
      "expected_behavior": "Attempt to access API root, expect failure due to service unavailability",
      "metrics": ["latency", "status_code"],
      "validation": {"field": "status_code", "type": "number", "min": 400}
    },
    {
      "name": "test_apidoc_access",
      "endpoint": "/apidoc",
      "method": "GET",
      "headers": {},
      "payload": {},
      "expected_status": 404,
      "expected_behavior": "Attempt to access API documentation, expect failure",
      "metrics": ["latency", "status_code"],
      "validation": {"field": "status_code", "type": "number", "min": 400}
    },
    {
      "name": "test_common_crypto_endpoints",
      "endpoint": "/v1/ticker",
      "method": "GET",
      "headers": {},
      "payload": {},
      "expected_status": 404,
      "expected_behavior": "Test common crypto API endpoint, expect failure",
      "metrics": ["latency", "status_code"],
      "validation": {"field": "status_code", "type": "number", "min": 400}
    }
  ],
  "pricing_probes": [
    {
      "name": "verify_service_unavailable",
      "description": "Confirm that the service is not operational and pricing cannot be verified",
      "endpoint": "/pricing",
      "method": "GET",
      "payload": {},
      "check": "Service should return error or parking page, not pricing information"
    }
  ],
  "stress_profile": {
    "concurrent_requests": 1,
    "duration_seconds": 5,
    "ramp_up": false
  }
}
```
Execute

0/4 tests passed

TestEndpointStatusLatency
test_service_availabilityGET /30295ms
test_api_root_accessGET /api30228ms
test_apidoc_accessGET /apidoc30229ms
test_common_crypto_endpointsGET /v1/ticker30229ms
Interpret
Looking at these benchmark results, this crypto service is completely non-functional for agent use. All endpoints return 302 redirects instead of actual API responses.

```json
{
  "overall": 15,
  "dimensions": {
    "token_efficiency": 1.0,
    "first_try_success": 1.0,
    "response_parseability": 1.0,
    "error_clarity": 2.0,
    "doc_quality": 1.0,
    "auth_simplicity": 2.0,
    "latency": 7.0,
    "consistency": 3.0
  },
  "pricing_normalized": {
    "maker_fee_bps": null,
    "taker_fee_bps": null,
    "withdrawal_fee_usd": null,
    "free_tier_requests": null
  },
  "issues": [
    "All API endpoints return 302 redirects instead of data",
    "Market ticker endpoint (/v1/ticker) inaccessible",
    "API documentation not accessible",
    "No security headers present",
    "Unknown authentication requirements",
    "No actual crypto/trading functionality accessible"
  ],
  "recommendations": [
    "Verify correct base URL and API endpoint structure", 
    "Implement proper REST API responses instead of redirects",
    "Provide public market data endpoints without authentication",
    "Add comprehensive API documentation",
    "Include security headers (CORS, rate limiting info)",
    "Clarify authentication requirements for different endpoint tiers",
    "Test basic market data endpoints (ticker, orderbook, trades)",
    "Implement proper HTTP status codes and error messages"
  ]
}
```

Agent Readiness

x402 Payments
Not supported
Streaming
No
Sandbox
None
Agent Auth
public
SDKs
None listed
MCP Support
No

Want the full interactive view?

See operational metrics, LLM evaluations, agent readiness, and more.

Open in Dashboard