Go-UPC Barcode-Lookup API

{
  "service_type": "platform",
  "base_url": "https://go-upc.com",
  "auth_method": "api_key",
  "auth_config": {
    "key_location": "query_param",
    "key_name": "key",
    "notes": "API key is obtained by registering on go-upc.com and is passed as a query string parameter in the request URL."
  },
  "endpoints": [
    {
      "path": "/api/{barcode}",
      "method": "GET",
      "description": "Look up product information by a UPC, EAN, or ISBN barcode number.",
      "params": [
        {
          "name": "key",
          "in": "query",
          "required": true,
          "description": "Your Go-UPC API key."
        }
      ],
      "response_fields": [
        "product name",
        "description",
        "brand",
        "image URL",
        "barcode type/number"
      ]
    }
  ],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "free_tier": "Limited free lookups available after registration",
      "paid_tiers": "Higher-volume plans available; exact pricing not published in provided content"
    }
  },
  "rate_limits": {
    "notes": "Not specified in provided content. Rate limits likely depend on subscription tier."
  },
  "capabilities": [
    "UPC barcode lookup",
    "EAN barcode lookup",
    "ISBN barcode lookup",
    "Product metadata retrieval (name, description, brand)",
    "Product image URL retrieval",
    "Global product coverage"
  ],
  "raw_analysis": "Go-UPC is a product data lookup service exposing an API for resolving UPC, EAN, and ISBN barcodes to product metadata, including name, description, brand, and image URL. It is aimed at developers building e-commerce, inventory, cataloging, shopping, and scanning applications that need to enrich products from barcodes. Access requires registration to obtain an API key, which is passed as a query parameter. The model is freemium: a limited free tier exists, with paid plans for higher volume. The provided content does not disclose exact endpoints beyond the lookup pattern, full pricing, or rate limits, so those are inferred conservatively. The platform appears mature and production-oriented given its global product coverage and support for multiple barcode standards, though no public REST API documentation excerpt was included beyond the marketing description."
}

2/3 tests passed

{
  "overall": 68,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 7.0,
    "response_parseability": 8.0,
    "error_clarity": 6.0,
    "doc_quality": 6.0,
    "auth_simplicity": 7.0,
    "latency": 9.5,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "model": "freemium",
    "free_tier": "limited free lookups after registration",
    "paid_tiers": "not published",
    "clarity": "low"
  },
  "issues": [
    "No /llms.txt — agents have no machine-readable entry point for capabilities and docs",
    "robots.txt disallows /api/v1/code/ with a Crawl-delay of 10, signaling scraping is unwelcome and could hurt agent-driven discovery",
    "Paid pricing tiers are not published, forcing humans to contact sales — a friction point for autonomous evaluation",
    "Free tier is gated behind registration without a documented public quota in the provided content",
    "No visible mention of an OpenAPI spec, SDK, or structured schema for response parsing"
  ],
  "recommendations": [
    "Publish /llms.txt with a concise description, endpoint list, auth scheme, and links to OpenAPI spec — biggest win for agent discoverability",
    "Expose an OpenAPI/JSON Schema document so agents can generate typed clients on first try",
    "Publish transparent pricing tiers and free-tier quota numbers instead of sales-gated info",
    "Provide a self-serve API key flow with clear rate limits and error codes (401/404/429 distinctions)",
    "Add a status page and explicit uptime/SLA statement to raise consistency confidence",
    "Document error response schema and common failure cases (unknown barcode, invalid format) in help docs"
  ]
}