KontragentPro

{
  "service_type": "platform",
  "base_url": "https://kontragentpro.ru",
  "auth_method": "api_key",
  "auth_config": {
    "api_key_location": "self-serve key issuance via website registration",
    "notes": "API key obtained through self-service onboarding on kontragentpro.ru; exact header/query parameter name not specified in the provided description."
  },
  "endpoints": [],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "tiers": "Free tier alongside paid plans",
      "billing": "Self-serve API keys imply metered or subscription-based paid tiers",
      "notes": "Specific quotas, prices, and paid tier limits are not documented in the provided content and must be verified on the site."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "Lookup of Russian legal entities and individual entrepreneurs by INN (tax ID)",
    "Lookup by OGRN (state registration number)",
    "Company registry details (EGRUL/EGRIP-style records)",
    "Multi-year financial statements from the state accounting database (Rosstat/GIR BO)",
    "Bankruptcy records lookup",
    "Trademark records lookup",
    "State inspection history (regulatory/oversight checks)",
    "REST API with self-serve API key provisioning",
    "MCP server for AI agent/LLM integration",
    "Data sourced from official open Russian government registries"
  ],
  "raw_analysis": "KontragentPro (kontragentpro.ru) is a Russian business/company data aggregation platform. It provides counterparty verification and due-diligence data for Russian legal entities and individual entrepreneurs, keyed by INN (tax identification number) or OGRN (primary state registration number). The dataset draws on official open registries and covers: core registry/registration details, multi-year financial statements sourced from the state accounting database, bankruptcy proceedings, trademark records, and state inspection (oversight) history — essentially the standard Russian counterparty-diligence stack.\n\nTarget users are businesses performing KYC/AML-lite checks, supplier/counterparty vetting, credit risk assessment, and financial analysis of Russian companies. The offering is notable for being explicitly API-first: a freemium REST API with self-serve API key issuance (no sales-led gatekeeping described) plus an MCP server, which points to a product aimed at developers and increasingly at AI/LLM agent workflows. The presence of an MCP server suggests a modernized integration surface beyond plain REST.\n\nMaturity: the description indicates a defined product with documented access paths (API keys, MCP), but the provided material gives no endpoint list, no rate limits, no versioning info, and no pricing table, so operational maturity and SLA guarantees are unverified. The platform's reliability is inherently coupled to the availability of underlying Russian state registries. No non-Russian coverage is claimed, so it is jurisdiction-specific. Auth is API-key based via self-service; exact header/parameter conventions and error semantics are not described and must be confirmed from the live documentation. Integration value is high for anyone needing programmatic Russian company data; the main open questions are quota/pricing specifics and endpoint-level detail."
}

3/3 tests passed

```json
{
  "overall": 72,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 7.0,
    "response_parseability": 8.5,
    "error_clarity": 6.5,
    "doc_quality": 7.5,
    "auth_simplicity": 8.0,
    "latency": 8.0,
    "consistency": 7.5
  },
  "pricing_normalized": {
    "model": "freemium",
    "free_tier": true,
    "self_serve_api_keys": true,
    "pricing_transparency": "low — specific quotas, paid tier prices, and rate limits not documented in provided content; must verify on site",
    "notes": "Metered or subscription paid tiers implied; exact figures unconfirmed"
  },
  "issues": [
    "Pricing, quotas, and paid-tier limits are not documented — agents cannot estimate cost or rate limits without visiting the site",
    "API endpoints are disallowed in robots.txt (Disallow: /api/), which may constrain some crawler-based discovery even though a REST API and MCP server are advertised",
    "Primary content is in Russian — reduces token-efficiency and first-try success for non-Russian-speaking/English-first agents and users",
    "No documented error semantics or rate-limit behavior surfaced in the analyzed content",
    "No explicit status page / uptime SLA referenced in findings"
  ],
  "recommendations": [
    "Publish concrete pricing tiers, free-tier quotas, and rate limits (ideally in llms.txt and a machine-readable pricing endpoint) for agent consumption",
    "Document API error codes, auth (bearer/API key) flow, and retry/backoff guidance for reliable agent integration",
    "Provide an English mirror of llms.txt and key docs to improve token efficiency and broaden agent onboarding",
    "Confirm robots.txt intent — if the REST API is meant to be agent-consumed, clarify that programmatic API use is permitted (robots.txt governs crawlers, not API clients)",
    "Add a public status/uptime page and stated SLA to strengthen the consistency signal"
  ]
}
```