Frankie Financial API

{
  "service_type": "platform",
  "base_url": "https://frankiefinancial.io",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "Identity verification via national database checks",
    "Name verification",
    "Address verification",
    "Date of birth verification",
    "Compliance utility integration for developers"
  ],
  "raw_analysis": "Frankie Financial (frankiefinancial.io) is a compliance and identity verification service marketed as a 'Compliance Utility' for developers. Based on the provided description, its core capability is checking personal identity attributes — name, address, and date of birth — against national databases, which suggests an identity verification (IDV) / KYC (Know Your Customer) use case. The target audience is developers building regulated applications (fintech, banking, crypto, lending, etc.) that need to perform customer due diligence. The description explicitly states it is an API for developers to integrate into their applications, indicating a developer-first platform rather than an end-user product. \n\nMaturity assessment: Frankie Financial is a real Australian fintech company known for identity and compliance APIs, with some press coverage and partnerships in the Australian market. However, the information provided here is limited and does not disclose endpoint specifications, authentication mechanism, rate limits, or pricing. No public REST API documentation URL, OpenAPI spec, or SDK references are included in the submission. Pricing model is not described; identity verification vendors typically use per-check pricing, but this cannot be confirmed from the available data. Accordingly, pricing_model is set to unknown. \n\nIntegrations: The description only references national database checks; no specific third-party integrations (e.g., Salesforce, Plaid, or other compliance platforms) are described. Without an official API reference, endpoint enumeration and auth detection are not possible. Further research into Frankie Financial's developer portal would be required to determine base endpoints (likely under api.frankiefinancial.io or similar), whether API keys or OAuth are used, and the exact pricing tiers. The platform's capabilities listed here are inferred directly from the description and should be validated against official documentation."
}

0/3 tests passed

{
  "overall": 28,
  "dimensions": {
    "token_efficiency": 4.0,
    "first_try_success": 2.0,
    "response_parseability": 3.0,
    "error_clarity": 2.0,
    "doc_quality": 2.0,
    "auth_simplicity": 3.0,
    "latency": 1.0,
    "consistency": 2.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "No pricing information available; no transparency on tiers, usage limits, or cost structure."
  },
  "issues": [
    "All checks timed out at ~30s with no HTTP status code returned — site appears unreachable or severely degraded.",
    "No robots.txt or llms.txt detected, limiting agent discoverability and structured access.",
    "No security headers observed on any response.",
    "Pricing model is unknown — agents cannot surface cost expectations to users.",
    "Capabilities are stated in abstract terms (identity/compliance verification) with no API endpoints, SDKs, or integration surfaces documented in the analysis.",
    "No structured data (JSON API, OpenAPI spec, exports) surfaced for agent parsing."
  ],
  "recommendations": [
    "Investigate and resolve the 30s timeouts — the domain is effectively unreachable, which is a hard blocker for any agent recommendation.",
    "Publish an llms.txt and robots.txt to enable agent discovery and safe crawling.",
    "Expose an OpenAPI/JSON API spec and document auth (prefer magic-link or API key over enterprise-only flows).",
    "Publish transparent pricing tiers and rate limits so agents can advise users on cost.",
    "Add a status page and security headers to improve reliability perception.",
    "Provide a quickstart guide with curl examples to improve first-try success."
  ]
}