Select the signal types relevant to your research, then review company or contact matches and their supporting details.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Enrich a company identified by domain and summarize its signal evidence.
/oo Autobound: List Autobound signal types, then enrich company [domain] for [selected signal types] detected after [date]. Summarize the signals and data coverage.
Search contacts by signal criteria and organize matching profiles for review.
/oo Autobound: Find Autobound contacts with signal types [signal types] detected between [start date] and [end date]. Summarize profiles and their signal evidence, stating the match count reviewed.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect your Autobound Signal API key.
Connect Autobound →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
This connection reads Autobound signal types, searches companies and contacts by signal criteria, and enriches identified profiles.
Inspect signal definitions and retrieve signals for a company or contact.
Find companies and contacts matching explicitly selected signal types.
Get the authenticated Autobound Signals account details and current credit balance.
Leina 
Wanta 
autobound.get_account List Autobound signal types and optionally include live counts and refresh cadence metadata.
autobound.list_signal_types Enrich one company with Autobound company-level signals.
autobound.enrich_company Search companies that match Autobound company-level signal filters.
autobound.search_companies Enrich one contact with Autobound contact-level signals and employer context.
autobound.enrich_contact Search contacts that match Autobound contact-level signal filters.
autobound.search_contacts No matching tools.
List signal types first and select the ones relevant to your research. The result can include counts and refresh metadata when requested.
Provide at least one company domain, company name, or LinkedIn URL. A clear identifier helps avoid ambiguous matches.
No. They describe detected company or contact events. Use the event details, timestamps, and coverage as evidence for review rather than inferring intent.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.