BIN Lookup API

{
  "service_type": "platform",
  "base_url": "https://bintable.com",
  "auth_method": "api_key",
  "auth_config": {
    "api_key_header": "X-Mashape-Key",
    "api_key_param": null,
    "usage_notes": "API key required for higher rate limits; free anonymous tier available"
  },
  "endpoints": [],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "free_tier": "rate limited with attribution",
      "paid_tiers": "available for higher limits and private usage",
      "pro_plans": "up to 12k requests per hour"
    }
  },
  "rate_limits": {
    "anonymous": "low rate limit, possibly 10 requests per hour",
    "free_tier_with_key": "likely 100 requests per hour",
    "paid_tiers": "up to 12,000 requests per hour",
    "unknown_exact_limits": true
  },
  "capabilities": [
    "BIN (Bank Identification Number) lookup",
    "Card brand detection (Visa, MasterCard, Amex, etc.)",
    "Issuing bank country and bank name",
    "Card type (credit, debit, prepaid)",
    "Card level (standard, gold, platinum, etc.)",
    "Bank phone and website",
    "Community-updated BIN database",
    "API access via rapidapi and direct",
    "Simple RESTful JSON responses"
  ],
  "raw_analysis": "BINTable.com is a specialized web service providing Bank Identification Number (BIN) lookup APIs. It focuses on supplying card metadata based on the first six digits of a payment card number. The platform has a public free tier and more extensive paid plans for higher-rate requests. It offers accurate, updatable data with support for card brands like Visa, Mastercard, American Express, and Discover, and details such as bank name, country, and card type. The service is particularly suited for financial service developers, fraud prevention teams, and e-commerce platforms that require card validation and transactional risk analysis. The database is augmented through community contributions and partnerships, ensuring up-to-date coverage. The API is available both via RapidAPI and directly on the website, making integration easy. However, detailed documentation on request/response formats or full endpoint lists are scarce, suggesting teams may need to contact support or access the platform for exact API specs. The pricing model and rate limits are more clearly outlined on their plans page and are tiered, starting with a free option for developers and moving to volume-based subscriptions. The platform is not fully REST-documented publicly, which limits automated discovery. Overall, it represents a niche but critical utility for card-related processing and verification."
}

2/3 tests passed

```json
{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 8.0,
    "response_parseability": 9.0,
    "error_clarity": 6.0,
    "doc_quality": 5.0,
    "auth_simplicity": 4.0,
    "latency": 8.0,
    "consistency": 7.0
  },
  "pricing_normalized": {
    "free_tier": true,
    "free_rate_limited": true,
    "max_requests_per_hour_paid": 12000,
    "attribution_required": true
  },
  "issues": [
    "No /llms.txt file for AI/agent-friendly documentation",
    "Robots.txt disallows /validate-bin and /ap (likely API endpoint) — confusing for agents",
    "Freemium with attribution requirement may be problematic for private/commercial use",
    "No security headers observed (potential reliability concern)",
    "Pricing details are vague — actual costs not clearly stated in extracted info"
  ],
  "recommendations": [
    "Add /llms.txt with API schema, endpoints, and parameter documentation",
    "Clarify pricing tiers with explicit cost per request/monthly plans",
    "Simplify auth — consider API key via magic link or one-click signup (SSO)",
    "Un-deny /validate-bin in robots.txt and provide explicit API usage guidelines",
    "Add robust security headers and a status page for transparency"
  ]
}
```