Veterans Affairs
The US Department of Veterans Affairs (VA) Lighthouse API platform provides a portfolio of public-facing REST APIs enabling third-party developers and partners to access veteran benefits data, health records (FHIR), appeals and decision review status, facilities information, forms, and service history verification. APIs support OAuth 2.0 with OpenID Connect and API key authentication and are available with sandbox and production environments.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Veterans Affairs the way a machine reads it — 54 machine-readable artifacts across 10 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Veterans Affairs scores 40.1/100 (developing), with a separate agent-readiness read of 33/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Veterans Affairs's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/va/"
title="Veterans Affairs on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/va.svg"
alt="Veterans Affairs Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/va/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/va/"
title="Veterans Affairs on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/va/card.svg"
alt="Veterans Affairs Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Veterans Affairs
Each block below is one kind of artifact we hold for Veterans Affairs. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 25
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Patient Health API (FHIR)
Allows Veterans and authorized third parties to access patient health data using the HL7 FHIR R4 standard, including records, medications, conditions, immunizations, and appoint...
Health Care Costs and Coverage API (FHIR)
Provides access to health care expense data for VA patients including medical charges, services received, and payments for health-related expenses using the FHIR standard.
Appeals Status API
Enables authorized parties to request the status of a Veteran's benefits claim appeal, including the current step in the process, estimated decision dates, and hearing information.
Decision Reviews API
Allows accredited representatives and Veterans to interact with VA decision reviews (benefit appeals), including submitting Supplemental Claims, Higher-Level Reviews, and Board ...
VA Facilities API
Provides location information and services data for VA facilities including VA Medical Centers, community-based outpatient clinics, Vet Centers, and benefits offices across the ...
VA Forms API
Provides information about VA forms including metadata, current versions, and downloadable URLs for official VA forms used in benefits and healthcare applications.
Veteran Verification API
Allows authorized third parties to verify a Veteran's service history, Veteran status, discharge information, and disability rating using OAuth 2.0 authorization from the Veteran.
Direct Deposit Management API
Enables accredited VSO representatives to view and update direct deposit information for Veterans receiving VA disability compensation and pension payments.
VA Letter Generator API
Allows Veterans and authorized third parties to generate official VA letters confirming veteran status, service history, benefit summary, and other information required for hous...
Benefits Reference Data API
Provides reference data used for VA benefits forms and applications, including lists of service branches, discharge types, disabilities, countries, and other standardized VA dat...
Veterans Affairs Appealable Issues API
The Appealable Issues API from Veterans Affairs — 1 operation(s) for appealable issues.
Veterans Affairs Appeals Status API
The Appeals Status API from Veterans Affairs — 1 operation(s) for appeals status.
Veterans Affairs Contestable Issues API
The Contestable Issues API from Veterans Affairs — 1 operation(s) for contestable issues.
Veterans Affairs Higher-Level Reviews API
The Higher-Level Reviews API from Veterans Affairs — 10 operation(s) for higher-level reviews.
Veterans Affairs Labs And Tests API
The Labs And Tests API from Veterans Affairs — 1 operation(s) for labs and tests.
Veterans Affairs Legacy Appeals API
The Legacy Appeals API from Veterans Affairs — 2 operation(s) for legacy appeals.
Veterans Affairs Medical Records API
The Medical Records API from Veterans Affairs — 30 operation(s) for medical records.
Veterans Affairs Messaging API
The Messaging API from Veterans Affairs — 20 operation(s) for messaging.
Veterans Affairs Notice of Disagreements API
The Notice of Disagreements API from Veterans Affairs — 15 operation(s) for notice of disagreements.
Veterans Affairs Other Accredited Representatives API
The Other Accredited Representatives API from Veterans Affairs — 1 operation(s) for other accredited representatives.
Veterans Affairs Prescriptions API
The Prescriptions API from Veterans Affairs — 8 operation(s) for prescriptions.
Veterans Affairs Supplemental Claims API
The Supplemental Claims API from Veterans Affairs — 15 operation(s) for supplemental claims.
Veterans Affairs Tooltips API
The Tooltips API from Veterans Affairs — 2 operation(s) for tooltips.
Veterans Affairs Unique User Metrics API
The Unique User Metrics API from Veterans Affairs — 1 operation(s) for unique user metrics.
Veterans Affairs VSO Accredited Representatives API
The VSO Accredited Representatives API from Veterans Affairs — 1 operation(s) for vso accredited representatives.
Scroll within the panel for all 25 ·
Open Collections 15
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONAppealable Issues API
OPEN COLLECTIONAppealable Issues Appeals Status API
OPEN COLLECTIONAppealable Issues Contestable Issues API
OPEN COLLECTIONAppealable Issues Labs And Tests API
OPEN COLLECTIONAppealable Issues Legacy Appeals API
OPEN COLLECTIONAppealable Issues Medical Records API
OPEN COLLECTIONAppealable Issues Messaging API
OPEN COLLECTIONAppealable Issues Notice of Disagreements API
OPEN COLLECTIONAppealable Issues Other Accredited Representatives API
OPEN COLLECTIONAppealable Issues Prescriptions API
OPEN COLLECTIONAppealable Issues Supplemental Claims API
OPEN COLLECTIONAppealable Issues Tooltips API
OPEN COLLECTIONAppealable Issues Unique User Metrics API
OPEN COLLECTIONAppealable Issues VSO Accredited Representatives API
OPEN COLLECTIONScroll within the panel for all 15 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Va Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Va Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Va Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Va Context
JSON-LDExamples 5
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Veterans Affairs — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/va · machine-readable index on apis.io
This is an independent, third-party profile of Veterans Affairs, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.