PI Web API 2018 SP1 Swagger Spec

{
  "service_type": "platform",
  "base_url": "https://techsupport.osisoft.com",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [
    {
      "name": "Swagger Spec",
      "path": "/api/docs",
      "method": "GET",
      "description": "Swagger specification file describing PI Web API 2018 SP1 endpoints. Exact path may be /piwebapi/swagger or similar depending on deployment."
    }
  ],
  "pricing_model": {
    "type": "unknown",
    "details": {}
  },
  "rate_limits": {},
  "capabilities": [
    "REST API for OSIsoft PI System data access",
    "Time-series data retrieval from PI Data Archive",
    "Asset framework (AF) navigation and queries",
    "Stream and batch data operations",
    "Event frame access",
    "Calculation and analytics services",
    "Authentication via Windows, Kerberos, or basic auth",
    "OpenAPI/Swagger-documented interface"
  ],
  "raw_analysis": "This entry points to a Swagger specification file hosted on OSIsoft (now AVEVA) technical support for PI Web API 2018 SP1. PI Web API is a RESTful interface to the OSIsoft PI System, an industrial data infrastructure used for collecting, storing, and analyzing time-series sensor and process data in manufacturing, energy, utilities, and other operational technology environments. The Swagger spec describes the API surface, which includes endpoints for PI Data Archive points, Asset Framework elements and attributes, event frames, streams, batch calls, calculations, and system information. Authentication typically relies on Windows integrated authentication, Kerberos, or basic credentials against an on-premises PI Web API node. Maturity is high within industrial settings; PI System has been a de facto standard for historians for decades, and PI Web API is the modern HTTP-based access layer replacing older PI SDK and PI OLEDB approaches. Integrations are broad via REST clients, .NET libraries, and partner tools, though the platform is proprietary, licensed, and usually deployed behind corporate networks rather than as a public cloud service. The referenced URL (techsupport.osisoft.com) is a support portal and documentation host, not the actual API runtime endpoint; the live API base URL would be whatever hostname the customer deploys (e.g., https://<piwebapi-server>/piwebapi). The pricing model is commercial and enterprise-licensed; exact pricing is not publicly listed. No public rate-limit documentation is available in the provided snippet."
}

1/3 tests passed

{
  "overall": 44,
  "dimensions": {
    "token_efficiency": 4.0,
    "first_try_success": 3.0,
    "response_parseability": 7.0,
    "error_clarity": 3.0,
    "doc_quality": 4.0,
    "auth_simplicity": 3.0,
    "latency": 8.0,
    "consistency": 4.0
  },
  "pricing_normalized": {
    "type": "unknown",
    "notes": "No public pricing information available. AVEVA PI System is enterprise-licensed, typically custom-quoted with opaque pricing. This is a significant barrier for agent recommendation since agents cannot give users a clear cost picture."
  },
  "issues": [
    "Homepage returns 403 Forbidden via Cloudflare — agents and crawlers are blocked from even reading the landing page, making it impossible to extract a value prop.",
    "llms_txt endpoint returns HTTP 500 Runtime Error — no LLM-friendly documentation surface exists.",
    "No public pricing model — enterprise sales motion means users cannot self-evaluate cost or feasibility.",
    "Auth requires Windows/Kerberos/basic auth against an on-prem PI Data Archive — this is fundamentally incompatible with agent-driven onboarding; a human IT setup is mandatory.",
    "robots.txt is minimally permissive but the site itself blocks access, signaling an anti-crawler posture that hurts agent discoverability.",
    "No security headers on the primary response, and conflicting signals (403 on root vs. 200 on robots.txt) complicate automated probing."
  ],
  "recommendations": [
    "Publish a public, crawlable landing page describing the PI Web API value proposition and core capabilities so agents can summarize it accurately.",
    "Provide a machine-readable docs surface (e.g., OpenAPI/Swagger served at a stable URL, plus an llms.txt) — the platform claims OpenAPI support but nothing is discoverable.",
    "Publish at least indicative pricing tiers or a free developer sandbox so users can evaluate before committing to enterprise sales.",
    "Fix the llms_txt endpoint (currently 500) or remove it — a broken endpoint is worse than none.",
    "Offer a token/OAuth developer sandbox for PI Web API so agents can run first-try integration without requiring a Windows domain or on-prem Kerberos setup.",
    "Improve error/limitation documentation: rate limits, data retention, AF/event-frame constraints are not surfaced anywhere crawlers can reach.",
    "Add a status page and uptime signals — current consistency cannot be verified from public sources."
  ]
}