CSV Format
Your CSV file must include these columns in order:Example CSV
Field Requirements
Host Fields (Required)
host_external_id: Unique identifier for the host within your organization. Used for idempotent imports (e.g.,web-prod-001)
host_name: Display name for the host (e.g., Production Web Server)
host_target_type: Connection protocol: ssh or winrm
Host Fields (Optional)
host_tags: Comma-separated additional names used to identify the host (e.g.,web-01,app-server-01)
Despite its name, the
host_tags column populates a host’s Additional Names (free-form aliases), not the structured OS, Shell, Type, and Technologies tags. Those tags are a closed vocabulary that you assign in Command Center on each host’s detail page after import. See Hosts: Host Tags.10.0.1.10)
host_public_ip: External IP address (e.g., 203.0.113.45)
Agent Fields
Leave all agent and credential fields empty to create a host without an agent. agent_name: Display name for the agent (e.g.,WebApp Agent)
agent_configuration_name: Must match an existing Specialty key (not the display name). See Specialties for available keys.
agent_main_engine: Primary LLM model (e.g., deepseek/deepseek-v3-together)
agent_secondary_engine: Fallback LLM model (e.g., qwen/qwen3-235b-openrouter)
Credential Fields
When an agent is specified, all 8 credential fields are required (2 credentials per agent). agent_credential_X_name: Credential name. If a credential with this name already exists in the organization, it will be reused. agent_credential_X_source_type: Eithersecret (value stored directly) or vault_path (reference to external vault)
agent_credential_X_role: One of:
remote_username(SSH/WinRM username)remote_password(SSH/WinRM password)remote_private_key(SSH private key)remote_public_key(SSH public key)
- For
secret: the actual username, password, or key content - For
vault_path: the path in your vault (e.g.,secret/db/user)
Multiple Agents per Host
To assign multiple agents to one host, repeat the host row with the samehost_external_id and host_name:
Credential Reuse
Credentials are identified by name within the organization. If you import a CSV with a credential name that already exists:- The existing credential will be reused (no duplicate created)
- The agent will be linked to the existing credential
Importing via Command Center
- Go to Hosts
- Click Import Hosts
- Upload your CSV file
- Click Import Hosts to submit
Idempotent Imports
Eachhost_external_id can only be imported once per organization. Attempting to import a CSV containing an external_id that already exists will fail with an error listing the duplicates.
This prevents accidental duplicate imports when re-running the same CSV.
Common Import Errors
Missing required columns: Ensure your CSV includes all 18 column headers in the exact order shown above. Empty host_external_id: Every row must have a non-emptyhost_external_id.
Invalid host_target_type: Must be exactly ssh or winrm (lowercase).
Configuration not found: The agent_configuration_name must match an existing Specialty’s key field, not its display name. Check Specialties for valid keys.
Incomplete agent fields: If you specify agent_name, you must also provide agent_main_engine, agent_secondary_engine, and all 8 credential fields.
Invalid credential source_type: Must be exactly secret or vault_path.
Invalid credential role: Must be one of: remote_username, remote_password, remote_private_key, remote_public_key.
host_name mismatch: If the same host_external_id appears multiple times, the host_name must match exactly across all rows.
Duplicate external_id: A host with this host_external_id already exists in the organization.
Important Notes
- Hosts are imported into the currently selected organization
- The entire CSV is validated before any data is written, so if any row fails validation, nothing is imported
- Large imports (1000+ hosts) are supported efficiently
- Credentials with the same name are reused, not duplicated

