3 APIs across 3 product groups. All share one credential.
| I want to... | Use | Why |
|---|---|---|
| Submit and track benefits-claim documents into VBA intake | Benefits Intake | Benefits Intake issues a secure upload location, validates PDFs, accepts the payload, and reports per-submission and batch status. |
| Look up VA forms and download links | VA Forms | VA Forms returns all forms with revision dates and finds a specific form by name, so an agent fetches the right blank form before a claim. |
| Confirm a person's Veteran status | Veteran Confirmation | Veteran Confirmation returns a Confirmed or Not Confirmed result for an individual, useful for verification before a submission or for discounts. |
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the VA (U.S. Department of Veterans Affairs) APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the VA APIs by hand means passing the apikey header, choosing between the sandbox and production va.gov hosts, and coding the document upload flow for sensitive Veteran data yourself. Through Jentic you install Jentic One once, add the VA APIs from the Jentic directory, store the key once, and your agent calls any of them.
Permission scoping
The VA APIs mix read-only lookups with a claim-submission path, so your own rules pin the agent to only the operations it needs, such as confirming a Veteran and reading a form while blocking document submission. You choose that allowed set, so nothing outside it runs.
Credential isolation
Your single 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.
Specific to using VA (U.S. Department of Veterans Affairs) APIs through Jentic.
What can an agent do across the VA APIs?
An agent can look up VA forms and their revision dates, confirm whether an individual is a Veteran, and submit and track benefits-claim documents into the Veterans Benefits Administration intake process. These steps can be chained into one workflow that verifies a person, fetches the right form, and files the completed document.
Do the VA APIs share one credential?
Yes. All three APIs use a single VA-issued API key passed in the apikey header, so one credential from the VA developer program covers VA Forms, Veteran Confirmation, and Benefits Intake.
How do I get access to the VA APIs?
Access is granted through the VA Lighthouse developer program at developer.va.gov. You apply for credentials, start against the sandbox host on va.gov, and request production approval before submitting real Veteran data.
Are these official VA APIs?
Yes. They are published by the U.S. Department of Veterans Affairs, so form metadata, Veteran-status confirmations, and the claim-intake path come directly from the VA rather than a third-party source.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
For Agents
An agent can look up VA forms and their revision dates, confirm whether a person is a Veteran, and request a secure upload location to submit and track benefits-claim documents into the VBA intake process. The three APIs share one VA-issued API key, so an agent can chain form lookup, status confirmation, and document submission in a single workflow.
These are official U.S. Department of Veterans Affairs APIs, so the form data, Veteran-status confirmations, and claim-intake path come straight from the VA rather than a third-party mirror. The set spans the full path from finding the right form to verifying a Veteran to submitting a tracked claim document.
Use for: Looking up VA form metadata, confirming an individual's Veteran status, and submitting or tracking benefits-claim documents into the VBA intake pipeline
Not supported: payment processing, direct messaging, real-time streaming, claim adjudication, eligibility calculation
Credentials: All three APIs authenticate with a single VA-issued API key passed in the apikey header, so one credential from the VA developer program covers the whole set.
All 3 VA (U.S. Department of Veterans Affairs) OpenAPI specs are vendor-official and indexed by Jentic, kept validated and agent-ready.
The U.S. Department of Veterans Affairs developer program (VA Lighthouse) publishes APIs that let approved third-party systems work with VA benefits data. Across these APIs an agent can look up VA form metadata and download links, confirm an individual's Veteran status, and submit and track benefits-claim documents directly into the Veterans Benefits Administration intake pipeline. All three APIs use a VA-issued API key and share a sandbox and production host on va.gov, so an agent built for one can reuse the same access model for the others.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fva.gov" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fva.gov" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Once connected, ask your agent something like: “confirm a veteran and submit their benefits claim documents to the VA”.
Each workflow spans multiple VA (U.S. Department of Veterans Affairs) APIs. Jentic routes each operation to the right API automatically.
Verify a Veteran, then submit their claim
Before an agent submits a benefits-claim document, it confirms the individual is a Veteran, then requests a secure upload location and sends the PDF into VBA intake. This gives a casework assistant a single flow from identity check to a tracked submission.
Call POST /status to confirm Veteran status, then POST /uploads to request an upload location and PUT the claim PDF
Veteran Confirmation + Benefits Intake
Fetch the right form, then file it
An agent looks up the correct VA form and its download link by name, then submits the completed document into the VBA intake pipeline and captures the submission id. This replaces manual form hunting and fax filing with one digital path.
Call GET /forms/{form_name} to get the form and its PDF link, then POST /uploads and submit the completed document
VA Forms + Benefits Intake
Confirm, retrieve the form, and submit end to end
For a full intake workflow an agent confirms the person is a Veteran, pulls the matching form and its revision date, then validates and submits the claim document and monitors its status. All three steps run under the one VA API key.
Call POST /status, then GET /forms/{form_name}, then POST /uploads/validate_document and POST /uploads to file and track the claim
Veteran Confirmation + VA Forms + Benefits Intake
Intent-based discovery
Agents search the Jentic directory by intent such as 'submit a benefits claim document' or 'confirm an individual's veteran status', and Jentic returns the matching VA operation with its input schema so the agent calls the right endpoint without browsing the VA reference docs.
Is there a sandbox before production?
Yes. Each API exposes a sandbox host on va.gov for testing, and production access to submit real benefits-claim documents requires approval through the VA developer program.
How do these APIs work with AI agents through Jentic?
Once Jentic One is installed, you or your agent can find and add any of these VA APIs from the Jentic directory to your workspace. The agent searches by intent, receives the matching operation schema, and executes the call while your Jentic One instance injects the stored API key.
All 4 are in the Jentic catalogue with the same one-credential, intent-search pattern.