Connector catalog¶
Find your provider, connect it read-only from guided setup, and open the setup guide for it.
Every provider here is governed: its evidence shape, credential primitive, and read-only boundary are defined in the platform’s source-system catalog, and this page is generated from that catalog rather than maintained by hand.
No connector is required to start. Venturi attributes AI consumption from the ingestion API, the drop-in proxy, or file import alone. Connectors add the organizational evidence (identity, code ownership, org structure, and budget) that raises attribution confidence beyond what invocation data can carry by itself.
Connect the evidence behind AI economics¶
Venturi joins AI usage and cost to the services, code, identities, teams, and budgets responsible for it. These connections form a continuously updated ownership record that supports cost allocation, adoption, and governance.
| Source group | Example systems | Evidence connected |
|---|---|---|
| Customer | Salesforce (Service/Agentforce), ServiceNow Customer Workflows, Zendesk | Customer accounts, workflows, and business outcomes |
| Finance & Operations | SAP S/4HANA, Oracle Fusion Cloud ERP, NetSuite, Workday Financials | Cost centers, budgets, invoices, and financial outcomes |
| Security & Identity | Okta, Microsoft Entra ID | Directory identities, groups, and access context |
| People & Talent | Workday HCM, BambooHR | Teams, reporting lines, and organizational changes |
| Data Platforms | Snowflake, Databricks, Google BigQuery | Data workloads, AI usage, and analytical joins |
| AI Stack | OpenAI, Anthropic, AWS Bedrock, Azure AI / Azure OpenAI, Google Vertex AI | Model usage, provider accounts, and billed cost |
| Engineering & Infra | GitHub (incl. Copilot), GitLab, Atlassian (Jira/JSM), ServiceNow ITSM, Datadog | Repositories, services, code owners, and operations |
The catalog describes the source systems in Venturi’s integration contract. In your tenant, confirm each enabled source’s access, last successful sync, and coverage in connector readiness.
Billing, runtime, and ownership evidence¶
Cloud billing connects through the AWS, Azure, and Google Cloud onboarding paths. Provider usage APIs, cloud exports, and runtime metadata contribute different evidence to the same ownership record.
| Evidence | Examples | Contribution |
|---|---|---|
| Billing and usage | Cloud billing exports; OpenAI and Anthropic usage and cost APIs | Reconcile quantities, rates, and charges |
| Runtime metadata | Ingestion API, proxy, and passive capture | Connect model calls to services and execution context |
| Organizational context | Identity, code ownership, team, customer, and finance systems | Connect technical identifiers to accountable owners and to the business outcomes your own systems record |
A provider’s account ID, project, workspace, IAM principal, or allocation tag is useful ownership evidence. Venturi joins those identifiers across sources and retains the evidence and freshness behind each mapping. An unresolved mapping remains visible as an unknown.
Billing granularity and delivery freshness are separate. AWS CUR 2.0 supports hourly, daily, or monthly line items and refreshes at least daily. Bedrock application inference profiles add application, team, or workload tags to cost allocation. Their billed cost is grouped by usage type and day.
Venturi collects operational metadata and usage quantities. Prompt text, completions, and customer content stay outside the ingestion boundary. Choose the hosting mode and approved residency lane in deployment modes.
Provider references: AWS CUR 2.0, export delivery, Bedrock inference profiles, Azure exports, Google Cloud billing exports.
How to read a row¶
Every provider connects read-only. Venturi stores each credential as an encrypted credential reference in your tenant, and guided setup verifies reads and denied writes before the connector activates.
The page that walks through setting this provider up: its provider-specific guide where one exists, otherwise the general provider setup guide.
Opens guided setup, which generates the Venturi connector, federation, and external-ID artifacts for this provider in-product.
Venturi connectors perform read operations only. Each setup guide lists required permissions and any provider credential that also carries write privileges.
Customer 10 providers
Finance & Operations 10 providers
Security & Identity 10 providers
People & Talent 10 providers
Data Platforms 10 providers
AI Stack 10 providers
Engineering & Infra 10 providers
Setup guides¶
Each guide documents one read-only connector in the Venturi platform connector package: its setup, validation, or discovery surface. Several cover sources the governed catalog above does not enumerate as providers, including an editor’s own billing export, a Copilot or Gemini adoption feed, an automation platform’s usage log, and network-level discovery methods. Start here when your source is not a row above.
Identity and lifecycle context
GitHub code ownershipRepository, team, and Copilot context
Microsoft Entra ID directory inventoryDirectory users and groups
Cursor BYOK provider billingProvider billing exports
Microsoft 365 Copilot adoptionAdoption and licensing context
Google Workspace Gemini adoptionAdoption and licensing context
Salesforce Agentforce usageAction usage and credit context
Snowflake Cortex usageCortex and query usage context
Databricks AI Functions usageServing and Lakeflow context
BigQuery ML and Vertex AI usageRemote-model and request-log context
Power Platform AI creditsEnvironment credit consumption
UiPath AI Units usageTenant, folder, and automation consumption
Boomi AgentStudio usageAgentStudio and Control Tower context
MuleSoft AI Gateway meteringToken metering context
Workato recipe usageRecipe and workspace context
Zapier automation contextAsset, Zap execution, and MCP server events
CASB shadow-AI detectionDetected-only CASB and SaaS-management observations
DNS and firewall AI discoveryDetected-only DNS, firewall, and EDR observations
eBPF passive AI discoveryCustomer-authorized metadata discovery
Capability identifiers and vendor permissions¶
The access table in each setup guide uses one of two kinds of names, and the guide labels which kind it shows.
- Vendor permissions are literal names in the vendor’s own vocabulary: a
Microsoft Graph application permission such as
User.Read.All, an Okta OAuth scope such asokta.users.read, a Google OAuth scope URL, a Snowflake database role, or a Databricks system table. Grant them exactly as written, in the vendor’s console or API. - Venturi capability identifiers, such as
Boomi.orAgentStudio. Read dns., are names in the Venturi connector manifest. They declare which read-only data a connector collects and appear in the connector’s health details. They are not OAuth scopes, IAM permissions, or API privileges, and you never enter them in a vendor console.query_ logs. readonly
Where a guide lists capability identifiers, it also names the vendor-side authorization that grants the same read-only access and links the vendor’s official documentation for it. Where a vendor offers no read-only credential, the guide says so and names the exception.
Sync windows and failure behavior¶
Inventory connectors (Okta, GitHub, and Microsoft Entra ID) have no time lookback: they read directory or organization inventory, and the table notes which records each one reads incrementally. Usage connectors read a rolling lookback window on every sync. The table lists each connector’s default and the setting that overrides it.
| Setup guide | Connector ID | Lookback | Override |
|---|---|---|---|
| Identities | okta |
None: full inventory and the last 7 days of System Log events, then changed users and new System Log events | Not applicable |
| Code ownership | github |
None: full inventory each sync; Copilot metrics report covers 28 days | Not applicable |
| Microsoft Entra ID directory inventory | azure_ad |
None: full inventory each sync, then new sign-in events | Not applicable |
| Cursor BYOK provider billing | cursor_byok |
24 hours | VENTURI_ |
| Microsoft 365 Copilot adoption | m365_copilot |
30 days | VENTURI_ |
| Google Workspace Gemini adoption | google_ |
30 days | VENTURI_ |
| Salesforce Agentforce usage | salesforce_ |
30 days | VENTURI_ |
| Snowflake Cortex usage | snowflake_cortex |
24 hours | VENTURI_ |
| Databricks AI Functions usage | databricks_ |
24 hours | VENTURI_ |
| BigQuery ML and Vertex AI usage | bigquery_ml |
24 hours | VENTURI_ |
| Power Platform AI credits | power_platform |
30 days | VENTURI_ |
| UiPath AI Units usage | uipath |
30 days | VENTURI_ |
| Boomi AgentStudio usage | boomi |
30 days | VENTURI_ |
| MuleSoft AI Gateway metering | mulesoft |
30 days | VENTURI_ |
| Workato recipe usage | workato |
30 days | VENTURI_ |
| Automation context | zapier |
30 days | VENTURI_ |
| CASB shadow-AI detection | casb_shadow_ai |
24 hours | VENTURI_ |
| DNS and firewall AI discovery | dns_ |
24 hours | VENTURI_ |
| eBPF passive AI discovery | ebpf_ |
15 minutes | VENTURI_ |
Every connector fails open. If an upstream read fails, that sync returns no rows for the affected source and never blocks ingestion from other sources or your AI traffic. The next scheduled sync reads the source again: a usage connector re-reads its full lookback window, and an inventory connector re-reads its inventory and resumes its incremental reads (Okta changed users and System Log events, Microsoft Entra ID sign-ins) from the last recorded position.
Before you connect¶
- Complete guided onboarding for your cloud and organization.
- Confirm the connector uses read-only scopes, roles, or grants. Where a vendor offers no read-only credential, the connector guide names that exception.
- Store each credential as an encrypted credential reference in
Settings / Admin / Credentials. - Assign an owner for credential rotation and offboarding.
- Use metadata only; do not provide prompt or completion content.
Cloud onboarding uses no long-lived cloud credentials by default; the Azure client-secret fallback, with a 90-day TTL, is its documented exception. Connectors differ: most authenticate with a credential that stays valid until you rotate it, such as an API token, private key, or client secret. Venturi stores each one as an encrypted credential reference. Rotate it on the vendor’s schedule, and use a federated identity credential instead of a stored secret where a guide offers one.
After configuration, use Verify & confirm to check read-only status, the latest sync timestamp, and coverage behavior.
Sign in to send feedback. Opens in a new tab.
Copy page details
Docs feedback: Connector catalog
Page: https://docs.venturi.systems/connectors/