MotaWord API

{
  "service_type": "platform",
  "base_url": "https://motaword.com",
  "auth_method": "api_key",
  "auth_config": {
    "header": "Authorization",
    "scheme": "Bearer",
    "notes": "MotaWord uses an API key/token issued from the dashboard. The token is typically passed as a Bearer token or X-API-Key depending on endpoint version. Confirm against current developer docs at https://api.motaword.com or the developer portal."
  },
  "endpoints": [],
  "pricing_model": {
    "type": "subscription",
    "details": {
      "notes": "MotaWord is a pay-per-project translation platform. Customers pay per word/project for translation services. API access is generally included for account holders; there are no separate public tiers for the API itself. Volume/enterprise pricing may apply."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Create and post translation projects",
    "Track project status and progress",
    "Retrieve project and document details",
    "Manage translation documents (upload/download)",
    "Support for many language pairs",
    "Crowdsourced/parallel translator workflow",
    "Quote and cost estimation",
    "Multilingual content delivery"
  ],
  "raw_analysis": "MotaWord is a cloud-based translation platform that crowdsources translation work across a network of professional translators, often completing projects in parallel for faster turnaround. The service targets businesses and developers needing programmatic access to translation workflows: posting projects, uploading documents, tracking progress, and retrieving finished translations. Maturity: MotaWord has been operating for over a decade and is an established player in the translation/localization space, with a documented REST API and developer documentation. The API appears to be a REST/JSON service with API-key based authentication (token issued via the MotaWord dashboard). Exact endpoint paths, rate limits, and current auth header conventions were not retrievable from the provided snippet and should be verified against the official developer documentation. Integrations: MotaWord provides integrations with common CMS, e-commerce, and localization tooling (e.g., WordPress, Drupal, and content platforms), and exposes a REST API for custom integrations. Because the API is focused on the translation workflow rather than a general-purpose platform API, its surface area is limited to projects, documents, quotes, and status tracking. Pricing is usage/subscription based per translation volume rather than a standalone API product. Overall, this is a mature, niche, production-grade API for teams that need automated translation project management."
}

3/3 tests passed

```json
{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 6.0,
    "response_parseability": 7.0,
    "error_clarity": 6.0,
    "doc_quality": 6.5,
    "auth_simplicity": 5.0,
    "latency": 10.0,
    "consistency": 6.0
  },
  "pricing_normalized": {
    "model": "pay-per-project",
    "currency": "USD",
    "per_unit": "per word / per project",
    "api_access": "included for account holders",
    "public_tiers": "none separate for API",
    "notes": "Volume/enterprise pricing may apply; no transparent public price list"
  },
  "issues": [
    "Pricing is opaque — no public per-word rate, making cost prediction hard for agents to advise users",
    "All probes returned HTTP 202 (Accepted) instead of 200, suggesting responses may be asynchronous or the endpoint behavior is non-standard",
    "No security headers detected on any response — weak signal for platform maturity",
    "No llms.txt content served, limiting machine-readable discoverability for AI agents",
    "Auth flow not described in detail; unclear if API keys can be self-provisioned without human sales contact",
    "No explicit status page or uptime documentation referenced"
  ],
  "recommendations": [
    "Publish a public per-word pricing table so agents can estimate project costs for users",
    "Serve a proper llms.txt with endpoint, auth, and capability summary for AI agent consumption",
    "Clarify API authentication (self-serve keys vs. sales-gated) to improve first-try onboarding",
    "Add a public status page to strengthen consistency/uptime perception",
    "Return standard 200 responses (or document 202 async semantics) to improve parseability and agent success rate",
    "Add security headers (HSTS, CSP, X-Content-Type-Options) to signal production readiness",
    "Document rate limits, error codes, and file format constraints in a dedicated API reference"
  ]
}
```