Research sources
- Connection: API or operator-provided file
- Permission: read only where possible
- Status: configuration-dependent
- Test: missing values and rate limits
Company search, contact checks, context, and drafting live in separate tabs with fragile handoffs.

The agent carries the brief and evidence while each connection keeps an explicit permission and status.
RUNTIME COMPATIBILITY MODEL
A useful connection is one whose input contract, credential scope, failure mode, and destination behavior your team can explain. The matrix below is an evaluation model, not a claim of official vendor partnerships.
AUTOMATION ARCHITECTURE
The agent reads a prospecting brief, queries configured data sources, and returns a SAMPLE-labeled result for inspection. No destination write and no outreach send occur.
The agent proposes field updates, displays provider provenance and conflicts, then waits for an operator to approve an export or CRM write.
The agent turns approved account facts into a draft while leaving send controls, suppression, regional compliance, and sender authentication with the operating team.
INSTALLATION PATH
Copy, run, configure a minimal research source, and inspect a first result. Copying is not installation; installation is not configuration; configuration is not approval.