Config

Configuration

Non-secret configuration follows a fixed precedence: CLI flags > shell env > agent-ads.config.json. Secrets always use the credential store or shell env.

Config file

agent-ads.config.json

Place this file in your project root. The CLI looks for it in the current directory and walks up to the filesystem root.

Inspect config

Show resolved config path

bash

agent-ads meta config path

Validate

Check config file syntax

bash

agent-ads meta config validate

Output

Output Flags

Shared output flags work the same way across all engines.

Format

JSON (default), JSONL, or CSV

bash

agent-ads meta insights query --format csv --output report.csv

Pretty print

Human-readable JSON

bash

agent-ads meta insights query --pretty

Envelope

Wrap response with metadata and paging

bash

agent-ads meta insights query --envelope

Doctor

Doctor Commands

Each engine has a doctor command that verifies your setup. Add --api to also test API connectivity.

Meta

Verify Meta setup

bash

agent-ads meta doctor --api

Google

Verify Google setup

bash

agent-ads google doctor --api

TikTok

Verify TikTok setup

bash

agent-ads tiktok doctor --api

Verify Pinterest setup

bash

agent-ads pinterest doctor --api

Verify LinkedIn setup

bash

agent-ads linkedin doctor --api