FIRST-PARTY CONNECTORS

Connect the site you control.

AIWebSignals does not need access to your hosting, CDN, or cloud account. Your infrastructure sends narrowly scoped request evidence to a per-site collector, where it is normalized into the same privacy-minimized event contract.

Just researching a website?

No ownership or connector is required. Use the public scanner to inspect what machines can observe from the public Internet.

Analyze any public website
Want actual first-party AI traffic?

Choose the environment below. Connected evidence unlocks actual AI requests, requested paths, failures, and probable journeys.

Choose your environment

Where does your site run?

Cloudflare WorkersLive validated

Workers Trace Logpush -> isolated HTTPS collector

Production observer + Workers Trace Logpush validated on AIWebSignals and an unrelated second Worker/site.

Set up Cloudflare Workers
VercelContract validated

Vercel Custom Drain -> HTTPS collector

Custom Drain HTTP transport and JSON/NDJSON behavior are specification-tested; first real customer will provide live provider certification.

Set up Vercel
FastlyContract validated

Fastly Real-Time Log Streaming -> HTTPS collector

Fastly HTTPS logging transport, domain-control challenge, custom header, and configured JSON record format are specification-tested.

Set up Fastly
Akamai DataStream 2Contract validated

Akamai DataStream 2 Custom HTTPS -> collector

DataStream 2 Custom HTTPS transport and documented JSON field names are specification-tested.

Set up Akamai DataStream 2
AWS CloudFrontContract validated

CloudFront logs -> Amazon Data Firehose -> HTTPS collector

CloudFront standard-log parsing and Amazon Data Firehose HTTP request/acknowledgement contract are specification-tested.

Set up AWS CloudFront
NGINX / VPSLocal end-to-end validated

Local observer/shipper -> HTTPS collector

The zero-dependency combined-log shipper is exercised from raw access-log input through privacy minimization and real local HTTP delivery in CI.

Set up NGINX / VPS
Apache / VPSLocal end-to-end validated

Local observer/shipper -> HTTPS collector

The zero-dependency combined-log shipper is exercised from raw access-log input through privacy minimization and real local HTTP delivery in CI.

Set up Apache / VPS
WordPressLocal end-to-end validated

WordPress request observer -> HTTPS collector

The connected PHP observer is syntax-checked and executed in CI against a WordPress API harness that verifies classification, delivery behavior, validation routing, and secret stripping without a hosting account.

Set up WordPress
Other / custom infrastructureContract validated

Trusted observer/shipper -> HTTPS collector

Authenticated HTTPS collector accepts bounded JSON, NDJSON, CSV, or combined-style records and is covered by parser contract tests.

Set up Other / custom infrastructure
No provider account custody.

Customers configure delivery inside infrastructure they already control. AIWebSignals does not ask for Cloudflare, Vercel, AWS, Fastly, Akamai, hosting, or WordPress administrator credentials. Hosted connectors that have not yet been exercised against a real customer account are labeled Contract validated until automatic first-customer certification completes.