Skip to main content
3 min read

abm-dev provenance / events

Read what enrichment produced. The provenance command returns the full v2 envelope (snapshot + narrative + events). The events command returns just the events stream — handy for piping into a webhook or a CRM trigger.

Renamed. This read used to be abm-dev source <id> — it's now abm-dev provenance <id>.

The bare abm-dev source command is now the Searchverb's company-&-role mode (a deprecated alias) — to source people by role at a company, run abm-dev search --role "Partner" --company-name "Acme".

provenance

abm-dev provenance <enrichment-id> \
  [--events-window-days 180] \
  [--json]

Default output renders identity, industry, head count, HQ, recent events, and any cached destination values as a human-readable summary. --json dumps the full envelope unchanged. enrichment:source is kept as a back-compat alias of this command.

events

abm-dev events <enrichment-id> \
  [--events-window-days 180] \
  [--json]

Prints the enrichment's events (funding rounds, leadership changes, and the rest) as a table, or as raw JSON with --json. See Events for the full list of event types.

Patterns

Pull funding-round events and pipe them into a Slack notifier (filter by type in jq):

abm-dev events 12455 --json \
  | jq -r '.[] | select(.event_type == "funding_round") | "\(.happened_at) \(.payload.round_name) at \(.payload.amount) by \(.payload.lead_investor)"' \
  | xargs -I {} slack-cli post --channel sales "{}"

Related