Skip to content

Choose an acquisition path

Start with the path that matches the evidence you can provide. 3 paths are available now: use 1 or combine them when you need broader coverage or finer attribution. File import is planned and cannot be used today.

Connect a source Available now Acquire governed billing, identity, ownership, and usage context through read-only connections.
Instrument an app Available now Capture request-level cost, tokens, latency, and caller identity at the invocation boundary.
Add discovery coverage Available now Find AI activity that governed billing and application paths do not yet explain.

Planned acquisition paths

These paths are specified but not shipped. They carry no setup action, and the current alternative is named on each row.

Import a file Planned, unavailable today Validating and ingesting a governed provider export is specified, but the upload surface, import API, and registered file drop are not shipped. Connect a source or instrument an app instead.

Observation is not invocation

A discovery signal is an observation, not an invocation. Discovery evidence, aggregate usage, entitlement inventories, and exclusion signals do not become invocations unless a governed promotion rule accepts the evidence and produces an invocation record. Until then, Venturi preserves the observation state and its provenance instead of treating detected activity as request-level usage.

This boundary also applies to connected sources. Billing totals and adoption inventories can improve attribution without proving that a specific model request occurred.

Path availability

  • Connect a source: available now. Review the connector catalog for the acquisition path each governed provider has today.
  • Instrument an app: available now. Use the Ingestion API when your code can emit an event, or the drop-in proxy when you can change the provider SDK base URL.
  • Add discovery coverage: available now. Use CASB, DNS/firewall, or customer-authorized eBPF metadata to create detected-only observations.
  • Import a file: planned, unavailable today. The governed contract is specified, but the upload surface, import API, and registered file drop are not shipped. Review File import before planning around this path.

Invariants across every path

  • Fail open at the invocation boundary. Ingestion and proxy processing must not block production traffic.
  • Do not capture content. Send or collect metadata, not prompt or completion text.
  • Preserve evidence state. Keep observed, inferred, excluded, and promoted records distinguishable through attribution and review.
  • Use read-only access. Source acquisition must not grant Venturi permission to change customer systems.