Self Service Developer API

{
  "service_type": "platform",
  "base_url": "https://peoplefinderspro.com",
  "auth_method": "basic",
  "auth_config": {
    "type": "basic_auth",
    "username_field": "api_access_profile_user",
    "password_field": "api_access_profile_password",
    "provisioning": "manual",
    "notes": "Credentials are issued per access profile; likely requires a paid or enterprise agreement with PeopleFinders Pro. No public OAuth/self-signup flow documented."
  },
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "notes": "Pricing is not publicly documented on the page. PeopleFinders Pro is a paid background check/data search platform; API access almost certainly requires a commercial contract or paid subscription rather than a free/self-serve tier despite the 'Self Service' label.",
      "typical_model": "subscription or per-query/volume-based enterprise pricing"
    }
  },
  "rate_limits": {},
  "capabilities": [
    "people search / person lookup",
    "background check data search",
    "contact information lookup",
    "personal records search",
    "programmatic search API for developers",
    "API documentation and demo environment",
    "access-profile-based credential management"
  ],
  "raw_analysis": "PeopleFindersPro is the professional/enterprise-facing arm of PeopleFinders, a long-established US people-search and public-records data broker. The URL described here (peoplefinderspro.com) is aimed at businesses, developers, and professional investigators (e.g., screening, collections, legal, due diligence) rather than consumers. The 'Self Service Developer API' page documents programmatic access to its search endpoints and appears to include a demo, but the actual API surface (endpoint paths, request/response schemas, rate limits, SLAs) is not exposed in the provided content — likely gated behind login and/or a sales contract.\n\nAuthentication is basic-style using an 'API access profile' username and password, which aligns with a legacy enterprise data-broker pattern rather than a modern OAuth/API-key developer platform. This strongly implies credentials are provisioned by an account rep after a commercial agreement, so 'self service' here refers to the developer-facing usage model rather than open signup.\n\nThe platform itself is mature: PeopleFinders has operated since the 1990s as a consumer and business data broker. The professional tier integrates with CRM/skip-tracing/screening workflows via API and bulk data. No public integration marketplace, SDK list, or developer portal features (keys, sandboxes, webhooks) are evident from the description, suggesting limited modern developer experience.\n\nCompliance context matters: as a US public-records/people-search provider, usage is likely restricted by FCRA, DPPA, GLBA, and state privacy laws depending on use case; buyers typically must attest to permissible purpose. No rate limits or pricing figures are published in the provided material, so those remain unknown. Overall this is an enterprise data-search API with gated, contract-based access and legacy basic-auth credentials, not an open self-serve developer product."
}

0/3 tests passed

{
  "overall": 32,
  "dimensions": {
    "token_efficiency": 4.0,
    "first_try_success": 2.0,
    "response_parseability": 5.0,
    "error_clarity": 3.0,
    "doc_quality": 3.0,
    "auth_simplicity": 2.0,
    "latency": 5.0,
    "consistency": 2.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "Pricing not publicly documented; likely commercial contract or paid subscription for API access despite 'Self Service' label."
  },
  "issues": [
    "DNS resolution failed for all endpoint checks (hostname not found), indicating the site was unreachable during testing",
    "No public pricing information available",
    "Likely requires commercial contract for API access, not self-serve",
    "No structured data/API discovery from tested endpoints",
    "Onboarding and sign-up flow unclear"
  ],
  "recommendations": [
    "Publish clear pricing tiers and API access requirements",
    "Ensure reliable DNS/uptime for the marketing and API domains",
    "Provide a public API quickstart and authentication documentation",
    "Offer a sandbox or demo tier to improve first-try success",
    "Add llms.txt and structured API docs for agent discoverability"
  ]
}