20
/100
prowl
Benchmarked Apr 06, 2026

Words

Definitions and synonyms for more than 150,000 words

defi defi_yield
Benchmark Your API

Score Breakdown

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

Benchmark Analysis Log

Full LLM thinking from the 4-phase benchmark pipeline.

Analyze
Looking at the Words API documentation, this is clearly not a DeFi protocol - it's a dictionary/word definitions API. This appears to be incorrectly categorized.

```json
{
  "service_type": "not_defi_protocol",
  "base_url": "https://wordsapiv1.p.rapidapi.com/words",
  "auth_method": "api_key_header",
  "auth_config": {
    "header_name": "X-RapidAPI-Key",
    "header_prefix": ""
  },
  "endpoints": [
    {"path": "/words/{word}", "method": "GET", "purpose": "get word definition"},
    {"path": "/words/{word}/definitions", "method": "GET", "purpose": "get definitions"},
    {"path": "/words/{word}/synonyms", "method": "GET", "purpose": "get synonyms"},
    {"path": "/words/{word}/antonyms", "method": "GET", "purpose": "get antonyms"}
  ],
  "pricing_model": {"type": "per_request", "details": {"freemium": "500 requests/month free"}},
  "rate_limits": {"rpm": 500},
  "capabilities": ["word_definitions", "synonyms", "antonyms", "pronunciation", "examples"],
  "defi_specifics": null,
  "analysis_error": "This is a dictionary/words API, not a DeFi protocol. It provides word definitions, synonyms, and linguistic data - completely unrelated to decentralized finance, yield farming, staking, or any blockchain/crypto functionality."
}
```

This service should be recategorized as "language/dictionary" rather than "defi". It has no DeFi-related functionality.
Plan
```json
{
  "tests": [
    {
      "name": "test_basic_word_lookup",
      "endpoint": "/words/example",
      "method": "GET",
      "headers": {
        "X-RapidAPI-Key": "{api_key}"
      },
      "payload": {},
      "expected_status": 200,
      "expected_behavior": "Returns word data including definitions, pronunciation, etc.",
      "metrics": ["latency", "accuracy", "status_code"],
      "validation": {"field": "word", "type": "string", "expected_value": "example"}
    },
    {
      "name": "test_word_definitions",
      "endpoint": "/words/beautiful/definitions",
      "method": "GET",
      "headers": {
        "X-RapidAPI-Key": "{api_key}"
      },
      "payload": {},
      "expected_status": 200,
      "expected_behavior": "Returns array of definitions for the word",
      "metrics": ["latency", "accuracy", "status_code"],
      "validation": {"field": "definitions", "type": "array", "min_length": 1}
    },
    {
      "name": "test_word_synonyms",
      "endpoint": "/words/happy/synonyms",
      "method": "GET",
      "headers": {
        "X-RapidAPI-Key": "{api_key}"
      },
      "payload": {},
      "expected_status": 200,
      "expected_behavior": "Returns array of synonyms",
      "metrics": ["latency", "accuracy", "status_code"],
      "validation": {"field": "synonyms", "type": "array", "min_length": 1}
    },
    {
      "name": "test_word_antonyms",
      "endpoint": "/words/good/antonyms",
      "method": "GET",
      "headers": {
        "X-RapidAPI-Key": "{api_key}"
      },
      "payload": {},
      "expected_status": 200,
      "expected_behavior": "Returns array of antonyms",
      "metrics": ["latency", "accuracy", "status_code"],
      "validation": {"field": "antonyms", "type": "array", "min_length": 1}
    },
    {
      "name": "test_invalid_word",
      "endpoint": "/words/invalidwordxyz123/definitions",
      "method": "GET",
      "headers": {
        "X-RapidAPI-Key": "{api_key}"
      },
      "payload": {},
      "expected_status": 404,
      "expected_behavior": "Returns 404 for non-existent word",
      "metrics": ["latency", "error_handling", "status_code"],
      "validation": {"field": "message", "type": "string"}
    },
    {
      "name": "test_missing_auth",
      "endpoint": "/words/test",
      "method": "GET",
      "headers": {},
      "payload": {},
      "expected_status": 401,
      "expected_behavior": "Returns 401 when API key is missing",
      "metrics": ["error_handling", "status_code"],
      "validation": {"status_code": 401}
    }
  ],
  "pricing_probes": [
    {
      "name": "verify_request_counting",
      "description": "Make multiple requests to verify per-request billing",
      "endpoint": "/words/test/definitions",
      "method": "GET",
      "payload": {},
      "check": "Each request should count toward 500/month quota, check response headers for usage indicators"
    }
  ],
  "stress_profile": {
    "concurrent_requests": 3,
    "duration_seconds": 10,
    "ramp_up": true
  }
}
```
Execute

1/7 tests passed

TestEndpointStatusLatency
test_basic_word_lookupGET /words/example403160ms
test_word_definitionsGET /words/beautiful/definitions42931ms
test_word_synonymsGET /words/happy/synonyms42940ms
test_word_antonymsGET /words/good/antonyms42941ms
test_invalid_wordGET /words/invalidwordxyz123/definitions42936ms
test_missing_authGET /words/test40183ms
defillama_tvl_crossrefGET https://api.llama.fi/protocols2000ms
Interpret
Looking at this service, there's a fundamental mismatch - this appears to be a dictionary/vocabulary API that has been misclassified as a DeFi protocol.

```json
{
  "overall": 5,
  "dimensions": {
    "token_efficiency": 1.0,
    "first_try_success": 1.0,
    "response_parseability": 2.0,
    "error_clarity": 4.0,
    "doc_quality": 1.0,
    "auth_simplicity": 2.0,
    "latency": 7.0,
    "consistency": 1.0
  },
  "pricing_normalized": {
    "cost_per_1k_requests": null,
    "free_tier_requests": null
  },
  "issues": [
    "CRITICAL: Service misclassification - this is a dictionary/vocabulary API, not a DeFi protocol",
    "No DeFi functionality detected - no yield, staking, TVL, or price endpoints",
    "Authentication barriers prevent testing (403 subscription required, 429 rate limits)",
    "All functional tests failed due to auth/subscription requirements",
    "Cannot assess DeFi data quality without access to actual DeFi endpoints"
  ],
  "recommendations": [
    "Reclassify service as 'developer_tools' or 'language_api' category",
    "Remove from DeFi benchmark pipeline - not applicable",
    "Address authentication issues to enable proper API testing",
    "If this is intended to be a DeFi service, endpoints need complete restructuring"
  ]
}
```

**Key Issues:**
- **Service Type Mismatch**: Endpoints like `/words/{word}/definitions` and `/words/{word}/synonyms` are clearly for vocabulary/dictionary services, not DeFi protocols
- **No DeFi Data**: Zero yield, TVL, staking, or price-related functionality detected
- **Authentication Failures**: All tests returned 401/403/429 errors, preventing proper evaluation
- **Wrong Benchmark Template**: This service should use `platform_profile` or `api_benchmark`, not `defi_yield`

This appears to be a classification error in the discovery system. The service should be recategorized and benchmarked with appropriate templates for language/vocabulary APIs.

Agent Readiness

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

Want the full interactive view?

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

Open in Dashboard