canonical: https://jentic.com/apis/va.gov/veteran-confirmation

# Va Gov Veteran Confirmation

The Deprecated Veteran Confirmation API allows you to confirm Veteran status for a given person. This can be useful for offering Veterans discounts or other benefits. The API will only return "Confirmed" or "Not Confirmed". Quickstart Guide 1. Get Access Credentials Get started by filling out the form on the [Apply for VA Lighthouse Developer Access](https://developer.va.gov/apply) page. After sub. The API exposes 1 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get confirmation about an individual's veteran status according to the va. Covers 1 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Get confirmation about an individual's Veteran status according to the VA
- Manage developer tools data programmatically
- Integrate Veteran Confirmation into automated workflows
- Query and filter Veteran Confirmation records by parameters
- Monitor Veteran Confirmation operational status and events

## Use cases

### Developer Tools Operations

Use the Veteran Confirmation to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including get confirmation about an individual's veteran status according to the va.

Example prompt: Call POST /status to get confirmation about an individual's veteran status according to the va

### Data Retrieval and Monitoring

Query Veteran Confirmation resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Veteran Confirmation endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Veteran Confirmation endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get confirmation about an individual's veteran status according to the va', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/status` | Get confirmation about an individual's Veteran status according to the VA |

## Key resources

- **veteran_confirmation_status** — Veteran Confirmation - Veteran Status

## Why Jentic

- **Setup:** Wiring the VA Veteran Confirmation API by hand means passing the apikey header and choosing between the sandbox and production va.gov hosts before you can check a single status. Through Jentic you install once, import Veteran Confirmation from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Veteran Confirmation exposes one status operation and carries its subject in the request body, so limit the agent to the operations it needs, such as confirming an individual's Veteran status. You choose that allowed set, so nothing outside it runs.
- **Credential handling:** Your VA-issued API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'confirm an individual's veteran status', and Jentic returns the matching Veteran Confirmation operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Veteran Confirmation use?

The Veteran Confirmation uses an API key passed in the `apikey` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get confirmation about an individual's veteran status according to the va with the Veteran Confirmation?

Yes. Use the POST /status endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Veteran Confirmation?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get confirmation about an individual's veteran status according to the va through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get confirmation about an individual's veteran status according to the va'. Jentic returns the matching Veteran Confirmation operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Veteran Confirmation have?

The Veteran Confirmation exposes 1 endpoints covering veteran_confirmation_status operations.

### Can I limit what my agent is allowed to do with the Veteran Confirmation API?

Yes. Because Jentic One is self-hosted, you define the rules that decide which operations and credentials your agent may use. The Veteran Confirmation API exposes a single status operation (POST /status) that confirms an individual's Veteran status from a subject in the request body, so you allow just that operation and nothing outside your chosen set runs. Your VA-issued API key stays with your own Jentic One instance and is injected only when an allowed call executes.