Use case · Hiring
Open roles show where a company puts its budget. A jump in one team is a reason to call.
What you build
First the view a seller gets, then one record behind it. Both come from the public sample files.
01
Six companies with a jump in open roles. Each row shows the number of open roles and the team with the largest share, as of the detection date.
The records are real, from the public hiring velocity sample file, all detected on Aug 11, 2026.
02
One hiring velocity record as it arrives. It carries the open roles, the change in seven days and the industry, together with the company domain.
A real record from the public sample file. The field names are the ones your code reads.
How it arrives
GCS push for a daily file per feed. REST API for one account on demand. MCP server for AI agents.
gs://autobound-<signal>/<date>/output.jsonl$ curl https://signals.autobound.ai/v1/companies/search$ claude mcp add --transport http autobound https://mcp.autobound.ai/mcpThe feeds
Each feed page shows how we build the signal, the fields, and a sample file.
FAQ
Yes. Hiring trends carry one subtype for each department, such as sales or engineering.
The coverage report lists the refresh rate and the lag of each feed.
Yes. Hiring records attach to a company and match on the domain or the LinkedIn URL.
Send a list of company domains. We return the signals we hold for each one, so you judge the fit on accounts you know.