Your Agent API Key

This page explains the API key that identifies one registered vecta-agent to the control plane.

What it does

Each agent has its own vc_... API key. It lets that agent pull the non-secret configuration for its jobs and report status for those jobs. The key does not grant access to another agent's jobs or another user's data.

The key is saved by the agent CLI in /root/.config/vecta/config.toml during registration. It is never shown in the dashboard, and the current CLI does not print it separately. The control plane stores only an unrecoverable representation of it.

Warning

Treat the API key as a secret. If you lose it, delete that agent and register it again. Deleting the agent also removes its jobs, run history, and snapshot-ID records; backed-up data remains in the repository, but you must recreate the jobs to manage it through Vecta.

Do not confuse it with the registration token

The dashboard creates a registration token for one registration. That token expires after 24 hours and can be used once. The API key is created during registration and identifies the resulting agent until the agent is deleted.

What's next

Follow Getting Started to register a server, or read Agents for the full agent lifecycle.