​
Changes to VisionAgent Authentication

To better support developer needs and enhance security, we’re implementing API authentication for VisionAgent. These changes will prevent unauthorized access and API misuse while ensuring reliable service for users.

As part of the API authentication implementation, we’re changing the endpoint that VisionAgent calls.

These changes will go into effect on April 11, 2025.

To ensure that VisionAgent and VisionAgent-generated code continue to work correctly, please follow the instructions in the sections below before April 11, 2025.

​
Action Required: Users of the VisionAgent Library

If you’ve installed the VisionAgent library, perform the following actions before April 11, 2025:

  1. Update VisionAgent to the latest version by running: pip install --upgrade vision-agent.
  2. Get your API key here.
  3. Set your VisionAgent API key as this environment variable: VISION_AGENT_API_KEY.

After upgrading VisionAgent, both code already generated by VisionAgent and new code generated by VisionAgent will call the correct endpoint.

​
Action Required: If You Directly Call the VisionAgent Endpoint

If you created code that directly calls the VisionAgent endpoint, you must change the endpoint before April 11, 2025, in order for the code to work.

Change the endpoint from:

api.landing.ai

to:

api.va.landing.ai

If you get errors caused by an HTTP 301 redirect, update the endpoint to resolve the issue.

​
Action Required: Users of the VisionAgent Web App

The VisionAgent web app is available here. When you deploy generated code in the VisionAgent web app, the deployed code calls the VisionAgent endpoint.

Any code deployed before April 11, 2025 will need to be re-deployed in order for it to call the correct endpoint.

Any code deployed after April 11, 2025 will call the correct endpoint.