Benefits Intake

{
  "service_type": "platform",
  "base_url": "https://api.va.gov",
  "auth_method": "api_key",
  "auth_config": {
    "auth_type": "API key (via VA Lighthouse developer portal)",
    "notes": "VA Lighthouse APIs require an API key obtained through developer.va.gov. Some endpoints may require OAuth 2.0 for veteran-authorized access.",
    "header": "apiKey",
    "registration_url": "https://developer.va.gov"
  },
  "endpoints": [
    {
      "name": "Submit Benefits Claim Document",
      "method": "POST",
      "path": "/services/vba_documents/v1/uploads",
      "description": "Upload a benefits claim document (PDF) via multipart form data for processing by the Veterans Benefits Administration."
    },
    {
      "name": "Get Upload Status",
      "method": "GET",
      "path": "/services/vba_documents/v1/uploads/{guid}",
      "description": "Retrieve the processing status of a previously submitted document upload."
    }
  ],
  "pricing_model": {
    "type": "free",
    "details": {
      "notes": "VA APIs are provided free of charge to authorized developers and organizations. No monetary cost for API access; authorization/sandbox approval required."
    }
  },
  "rate_limits": {
    "notes": "Rate limits are enforced by the VA Lighthouse platform. Specific values may vary by endpoint and are documented in the developer portal."
  },
  "capabilities": [
    "Digital submission of VA benefits claim documents",
    "Designed for use by Veterans Service Organizations (VSOs), federal agencies, and individual Veterans",
    "Supports PDF document upload",
    "Tracks processing status of submitted documents",
    "Integration into third-party claims management systems",
    "Part of the broader VA Lighthouse API platform"
  ],
  "raw_analysis": "The 'Benefits Intake' service refers to the Veterans Benefits Administration (VBA) document submission capability exposed through the VA Lighthouse API platform, not a standalone product at va.gov:benefits. The URL provided (https://va.gov:benefits) appears malformed; the legitimate consumer-facing site is https://www.va.gov/health-care or https://www.va.gov/benefits (note: va.gov uses subpaths, not ':' syntax). The actual programmatic interface lives under https://api.va.gov/services/vba_documents/v1/ and is documented at developer.va.gov.\n\nPurpose: Allows authorized third-party systems employed by Veterans Service Organizations (VSOs), agencies, and Veterans themselves to digitally submit VA benefits claim documents (typically PDFs and associated evidence) directly to the Veterans Benefits Administration. This replaces slower paper/mail submission workflows and is a key modernization effort by the VA.\n\nAudience: VSO representatives (e.g., American Legion, VFW, DAV service officers), accredited claims agents, VA-accredited attorneys, and Veterans submitting their own claims through tools that have integrated the API. Also used by agencies that support Veteran benefits coordination.\n\nMaturity: The VBA Documents API (Benefits Intake) is one of the more mature VA Lighthouse APIs. It has been available in production since roughly 2019-2020, has a stable versioned surface (v1), and is widely integrated by VSO tooling. It supports sandbox testing prior to production access.\n\nAuthentication: Access is gated through developer.va.gov. Developers register an application to obtain an API key (sent via the 'apiKey' header). Certain veteran-data-scoped endpoints in the VA ecosystem also support OAuth 2.0 for veteran-consented data access, but the Benefits Intake upload endpoints primarily use API key authentication with elevated authorization for approved organizations.\n\nCapabilities: Document upload (multipart form), status polling, error/validation feedback (malformed PDFs, duplicate submissions, file size limits), and integration hooks for claims management software.\n\nPricing: Free. There is no fee for VA Lighthouse API usage. The cost is organizational effort in obtaining authorization and building compliant integrations.\n\nRate limits and quotas: Managed by VA Lighthouse; applicants are typically given documented quotas per environment (sandbox vs. production) after approval.\n\nIntegrations: Commonly integrated into VSO case management systems, claims automation tools, and Veteran-facing benefit assistance platforms. Also connects conceptually with other VA Lighthouse APIs (e.g., Decision Reviews, Appeals, Veteran Confirmation, Benefits Claims status) to form a fuller claim-submission and tracking pipeline.\n\nRecommendation for Prowl: Treat this as a platform with a REST API rather than a pure no-API platform. Onboarding requires developer.va.gov registration and approval; the base URL to use programmatically is https://api.va.gov, and the canonical documentation is at https://developer.va.gov/explore/api/benefits-intake (VBA Documents)."
}

2/3 tests passed

{
  "overall": 62,
  "dimensions": {
    "token_efficiency": 7.0,
    "first_try_success": 4.0,
    "response_parseability": 9.0,
    "error_clarity": 6.5,
    "doc_quality": 7.0,
    "auth_simplicity": 4.0,
    "latency": 9.5,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "model": "free",
    "cost": 0,
    "notes": "VA Lighthouse APIs are free to use; authorization/sandbox approval required, which is the real barrier"
  },
  "issues": [
    "No llms.txt (404) — no agent-first documentation discovery",
    "Auth is complex: requires VA Lighthouse developer registration and sandbox/production approval for VSOs, federal agencies, or individual Veterans",
    "Onboarding is not self-serve in minutes; approval workflow adds friction",
    "robots.txt is template-level and unhelpful for agents crawling docs",
    "Marketing site preview is minimal ('Welcome to the va.gov API') — limited signal about capabilities from root"
  ],
  "recommendations": [
    "Publish an llms.txt and machine-readable capability manifest for agent discovery",
    "Provide a clear sandbox self-signup path so agents/users can test endpoints without lengthy approval",
    "Expose structured error schemas (it partially does this) with human-readable remediation hints",
    "Document rate limits, processing SLAs, and status polling semantics explicitly",
    "Add a getting-started quickstart with copy-paste curl examples and token flow"
  ]
}