COMPOSED
Journey story from Funding + Hiring — exposed when written
Funding + AI is composed from Funding plus AI-relevant Hiring — AI first or funded first — re-checked as evidence accumulates. Wire it when your play needs the story, not two unrelated pings.
REST and firehose require the API Access add-on on Pro. Docs stay public.
POST outbound · Settings → Webhooks · type=funding-ai
POST /api/v1/companies · signal_query: "signal:funding-ai:30d"
GET /api/v1/companies/{id}
At a glance
COMPOSED
Journey story from Funding + Hiring — exposed when written
Both
No composed row without capital and AI-relevant hiring evidence
Raise
Aged from the funding date — not only when the row was written
Windows
Pairs well with funded-ai-hiring style slice searches
What you get via API
When VeilStrat decides capital and AI hiring cohere, it writes Funding + AI. That composed row can hit your firehose and appear in REST search and dossiers — with direction (AI first / funded first) reflected in product labels.
Use it to enroll accounts into post-raise AI build plays without stitching Funding and Hiring yourself.
Integration loop
Treat Funding + AI as a scarce enrollment event. Enrich deeply, then open the right sequence.
Enable Funding + AI on the firehose so only coherent journeys hit this path.
GET /api/v1/companies/{id} returns the journey plus Funding and Hiring context for messaging.
Use AI-first vs funded-first labels from the dossier to pick the right sequence template.
Use GET /api/v1/slices with funded-AI windows when building a weekly list.
Example calls
Illustrative requests for journey-led workflows.
Search
Shortlist accounts mid-journey for pipeline review.
curl -s -X POST "${BASE_URL}/api/v1/companies" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "signal_query": "signal:funding-ai:30d", "page": 1, "pageSize": 25 }'Enrich
Read Funding, Hiring, and the composed row before drafting outreach.
curl -s "${BASE_URL}/api/v1/companies/COMPANY_UUID" \
-H "Authorization: Bearer YOUR_API_KEY"Slices
Requires slice plus at least one filter — see docs for allowed params.
curl -s "${BASE_URL}/api/v1/slices?slice=funded-ai-hiring&scoreMin=70" \
-H "Authorization: Bearer YOUR_API_KEY"GTM automations
Automate the play that only makes sense when both halves exist.
Sequences
Skip accounts that raised without AI hiring — or hired without capital.
Copy
Branch templates for AI-first vs funded-first journeys from dossier labels.
IR / corpdev
Notify research pods when a raise starts attracting AI seats.
Scoring
Reserve top score bands for composed journeys, not single-signal noise.
Composition rule
Client-side “funding AND hiring” filters are not the same as Funding + AI. VeilStrat re-evaluates coherence and ages from the raise. Subscribe to the composed type when your play depends on that judgment.
Related
Jump to the buyer-facing signal guide, sibling APIs, or the technical docs.
Subscribe to Funding + AI, enrich on every ping, and enroll post-raise AI plays with the same coherence rules as the dashboard.
REST and firehose require the API Access add-on on Pro. Docs stay public.