Weixinmpsdk

{
  "service_type": "platform",
  "base_url": "https://weixin.senparc.com",
  "auth_method": "none",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {"type": "free", "details": {"model": "open-source SDK", "note": "Senparc.Weixin is distributed as NuGet packages under Apache 2.0 license; no direct platform-level paywall"}},
  "rate_limits": {},
  "capabilities": [
    "WeChat Official Account (微信公众号) SDK for .NET",
    "WeChat Mini Program (小程序) SDK for .NET",
    "WeChat Mini Game (小游戏) SDK for .NET",
    "WeChat Pay (微信支付) SDK for .NET",
    "WeCom / Enterprise WeChat (企业微信) SDK for .NET",
    "WeChat Open Platform (开放平台) SDK for .NET",
    "JSSDK support",
    "WeChat peripheral/hardware integrations",
    "Message handling and event dispatch",
    "Multi-targeting .NET Framework, .NET Core, .NET 10.0"
  ],
  "raw_analysis": "Senparc.Weixin (Weixinmpsdk) is an open-source .NET SDK for the WeChat ecosystem, hosted at https://weixin.senparc.com. It is a developer library/framework rather than a hosted platform or service. Its purpose is to help .NET/C# developers integrate with WeChat's family of products: Official Accounts (公众号), Mini Programs (小程序), Mini Games (小游戏), WeChat Pay (微信支付), Enterprise WeChat/WeCom (企业微信/企业号), the WeChat Open Platform (开放平台), JSSDK web tooling, and WeChat hardware/peripheral APIs.\n\nTarget audience: C#/.NET developers building applications on top of WeChat. Maturity is high — the project has existed for many years, supports a broad target matrix (.NET Framework, .NET Core, .NET 10.0), and is one of the most widely adopted WeChat SDKs in the Chinese .NET community. It is distributed primarily via NuGet and GitHub.\n\nFrom a platform-analyzer perspective:\n- There is no public REST API exposed by this service itself. The 'API' is the SDK surface (NuGet packages) plus the upstream WeChat API surface that it wraps.\n- Authentication is delegated to the WeChat platform: the SDK helps manage access tokens, OAuth flows, JSSDK tickets, and message signatures. The SDK site itself does not require auth to consume.\n- Pricing: the SDK is free/open source (Apache 2.0). Any costs come from WeChat platform usage and Serverless/Senparc commercial offerings (e.g., Senparc.Weixin.Sample, Senparc.NeuChar), not from the SDK itself.\n- Integrations: NuGet packages, GitHub source, ASP.NET Core middleware/extensions, NeuChar framework, and numerous samples for MVC/WebAPI/Console/Blazor.\n\nConclusion: This is a developer SDK/platform-tooling entry, not a SaaS API endpoint provider. Platform analyzers should classify it as 'platform' with no endpoints, no auth on the SDK site, and free/open-source pricing. The most valuable metadata is target platforms, package names, and the fact that it fronts the WeChat API ecosystem rather than exposing its own REST API."
}

1/3 tests passed

```json
{
  "overall": 58,
  "dimensions": {
    "token_efficiency": 6.5,
    "first_try_success": 6.0,
    "response_parseability": 5.5,
    "error_clarity": 5.5,
    "doc_quality": 6.5,
    "auth_simplicity": 8.0,
    "latency": 5.5,
    "consistency": 6.0
  },
  "pricing_normalized": {
    "model": "free_open_source",
    "license": "Apache-2.0",
    "distribution": "NuGet",
    "cost_per_call": 0
  },
  "issues": [
    "No robots.txt (404) — crawlers and agents get no guidance on crawl policy",
    "No llms.txt (404) — no machine-readable summary for AI agents to ingest",
    "No security headers present on responses (has_security_headers: false)",
    "Website latency ~1146ms exceeds the <500ms threshold; not fast for programmatic scraping",
    "Documentation and site are primarily Chinese, limiting English-language agent comprehension",
    "Homepage title/meta are keyword-stuffed and unstructured, hurting token efficiency",
    "IIS 8.0 error pages leak server version on 404s — minor info disclosure",
    "No clear machine-readable API/onboarding docs surfaced (SDK is NuGet-based, but site lacks structured API schema)"
  ],
  "recommendations": [
    "Add an llms.txt summarizing the SDK, packages, and getting-started steps for AI agents",
    "Add robots.txt with explicit allow rules for common agent crawlers",
    "Add security headers (HSTS, X-Content-Type-Options, CSP) to reduce security concerns",
    "Improve response time to <500ms with caching/CDN",
    "Provide an English-language getting-started guide and structured API reference",
    "Publish a machine-readable package index (JSON) listing NuGet packages and versions",
    "Clean up homepage title/meta to a concise, structured value proposition",
    "Suppress IIS version details in error responses"
  ]
}
```