Can one company have multiple Web rows?

Yes. Multiplicity is by URL / page kind so you know which surface spoke.

Should I auto-enroll sequences on Web?

Most teams use Web for research tasks first, then enroll after Hiring or Funding confirmation. Automate carefully.

What access do I need?

Pro plus the API Access add-on for firehose and REST. Technical docs remain public at app.veilstrat.com/docs/api.

Web AI Activity API

BASE

Stream meaningful AI language from real company pages.

Web AI Activity writes only after crawl + quality check — product claims with substance, not vague marketing. Subscribe when page-level AI language should trigger research or outreach.

BASE signal from crawled pages — sitemap alone never writes
Firehose when a page clears the quality bar
Multiplicity by URL / page kind — which surface spoke
Pair with Hiring and Funding for fuller company context

Read the API docs Sign up for Pro View signal guide

REST and firehose require the API Access add-on on Pro. Docs stay public.

web-api.previewPro

POST outbound · Settings → Webhooks · type=web

POST /api/v1/companies · signal_query: "signal:web:30d"

GET /api/v1/companies/{id}

At a glance

How this signal type shows up in the API

BASE

Born from crawled page content — available via API when written

Quality

Vague AI marketing does not become a Web signal

Page

Rows reflect which URL / page kind spoke

Never

Sitemap mapping alone never creates a firehose event

What you get via API

Page-level AI claims as timed events

When a crawled page clears VeilStrat’s quality bar, a Web AI Activity signal writes. With Pro and API Access the firehose can push that event and REST can return it in search and dossiers with snapshot context.

Use Web to catch public AI positioning early — changelogs, product pages, careers — before hiring or funding confirms the build.

Subscribe to Web for page-level AI language alerts
Enrich for URL/page-kind context before messaging
Combine with Hiring/Funding subscriptions for fuller plays

Integration loop

Page write → research task

Web events are great for human-in-the-loop research. Enrich, create a task, optionally wait for Hiring confirmation.

01
Subscribe to Web
Enable Web AI Activity on the firehose for quality-gated page events.
02
Enrich for the URL story
GET /api/v1/companies/{id} for the Web row, snapshot fields, and other timeline signals.
03
Create a research task
Drop a link + summary into the AE/research queue; do not auto-spam sequences on every page.
04
Confirm with Hiring
Optionally require a later Hiring ping before heavy outbound investment.

Example calls

Common Web AI Activity API patterns

Illustrative requests for page-led research workflows.

Companies with recent Web signals

Find accounts whose pages just spoke AI with substance.

curl -s -X POST "${BASE_URL}/api/v1/companies" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "signal_query": "signal:web:30d", "page": 1, "pageSize": 50 }'

Enrich

Dossier after a Web webhook

Pull page-level context before creating a research task.

curl -s "${BASE_URL}/api/v1/companies/COMPANY_UUID" \
  -H "Authorization: Bearer YOUR_API_KEY"

Monitor

Health check

Budget-exempt uptime probe — still requires a valid API key and API Access.

curl -s "${BASE_URL}/api/v1/health" \
  -H "Authorization: Bearer YOUR_API_KEY"

GTM automations

Where Web API hooks land

Use page claims as early research triggers, not always as auto-dial fuel.

Research

Queue page citations for humans

Create tasks with URL context so reps can verify before outreach.

Intel

Digest competitor AI claims

Pipe Web events for watched domains into a weekly intel channel.

Timing

Catch positioning before hiring

Flag accounts speaking AI publicly ahead of headcount confirmation.

Personalization

Cite the page in first touch

Only after human review — inject the specific claim into sequence copy.

Quality rule

Maps never fire webhooks

If you only see sitemap activity in other systems, VeilStrat still will not write Web AI Activity. API consumers only receive rows after crawl + quality judgment — by design.

Keep exploring this signal surface

Jump to the buyer-facing signal guide, sibling APIs, or the technical docs.

FAQ

Web AI Activity API, answered

Page-signal questions before you automate research.

Vague AI marketing fails the quality bar. Only substantive page language becomes a Web signal — and only then can the firehose POST.

Catch real AI page claimsas they clear the gate.

Subscribe to Web AI Activity, enrich for URL context, and feed research queues with the same quality bar as the dashboard.