Skip to main content

Use case · List building

Build account lists from live events

A seller thinks in events: who changed jobs, who is hiring, who raised. Each event is a filter.

What you build

From signal to action

First the view a seller gets, then one record behind it. Both come from the public sample files.

01

What your team sees

Twelve real records from two feeds. Each filter chip maps to one field of the record, so the list narrows as the seller adds a signal type, an event or a date.

Search filters · new sales leaders
Add a filter

12 of 12 records

as of Aug 11, 2026
  • SMGRich Givone

    SVP & Chief Sales Officer to Chief Revenue Officer

    jobChangeAug 1, 2026
  • KnitWell Group

    204 open roles, 64% in sales

    hiringVelocityAug 11, 2026
  • MatillionNatalie Maybin

    Joined from SailPoint as Global Inside Sales Director

    jobChangeAug 1, 2026
  • KPMG

    884 open roles, 27% in accounting

    hiringVelocityAug 11, 2026
  • Waterleau GroupJoris Moors

    Promoted to Sales Director

    promotionJul 1, 2026
  • Wolt

    115 open roles, 22% in sales

    hiringVelocityAug 11, 2026
  • SiderisePaul Kersey

    Commercial Director to Director of Commercial Sales

    jobChangeAug 1, 2026
  • Dana

    157 open roles, 17% in engineering

    hiringVelocityAug 11, 2026
  • ElawayViktor Hansson

    Head of Sales Developed Markets to Head of Sales Sweden & Denmark

    jobChangeJul 1, 2026
  • Viking

    41 open roles, 20% in sales

    hiringVelocityAug 11, 2026
  • CytivaPar Hermansson

    Promoted to Sr Director, IT Business Enablement, Commercial

    promotionJun 1, 2026
  • ALK Technologies

    49 open roles, 16% in sales

    hiringVelocityAug 11, 2026

The records are real, from the public sample files for work milestones and hiring velocity. The filter set is yours to configure; each chip maps to one field on the record.

02

The record your product receives

One hiring velocity record as it arrives. Each filter reads one field: the subtype, the detection date, the company size or the number of open roles.

Record · hiring-velocity.csv
signal_type
hiring-velocity-v2
signal_subtype
hiringVelocity
detected_at
2026-08-11T07:14:15.000Z
company.domain
wolt.com
company.employee_count_low
1001
company.employee_count_high
5000
data.numberOfOpenRoles
115

A real record from the public sample file. The field names are the ones your code reads.

How it arrives

Built for how your stack already works

GCS push for a daily file per feed. REST API for one account on demand. MCP server for AI agents.

  • Every signal of a feed, on a schedule

    GCS push

    Daily to weekly
    Scheduled exports to your bucket in JSONL, Parquet, or CSV.
    gs://autobound-<signal>/<date>/output.jsonl
  • One account or one contact, right now

    REST API

    JSON over HTTPS
    Real-time search, enrich, and filter across every signal type.
    $ curl https://signals.autobound.ai/v1/companies/search
  • An AI agent that asks its own questions

    MCP server

    Agent-native
    Every signal type as a tool in Claude, ChatGPT, or Cursor.
    $ claude mcp add --transport http autobound https://mcp.autobound.ai/mcp

The feeds

The feeds behind this use case

Each feed page shows how we build the signal, the fields, and a sample file.

FAQ

Common questions

Which filters can we offer?

Signal type, subtype, date, industry, company size, and seniority for contacts.

Can one list use several feeds?

Yes. Every feed uses the same record shape, so one list can mix feeds.

How does the list reach our product?

As a daily file for each feed, or on demand through the REST API.

Build a list from your own accounts

Send a list of company domains. We return the signals we hold for each one, so you judge the fit on accounts you know.