You want outcomes
- Know when a competitor ships a page
- Catch new posts with scheduled checks, usually within an hour, plus check-now on demand
- Detect CMS / analytics / CDN shifts
- Keep agents current without babysitting cron
Tell Crawlwise which sites to watch. We check them on a schedule and POST your app (or AI agent) when something changes — new pages, new posts, or a tech-stack shift. On-demand lookups still work. You pay for changes, not empty checks.
New here? See how it works in 5 steps →
We watch sites on a scheduleYou pay when something changesHMAC-signed webhooks to your app
Billing mistakes get fixed — duplicate charges or credits you paid for but never received. Details.
# Free demo: no key needed
curl -G https://crawlwisedata.com/v1/techstack \
-d url=wordpress.org
# With your key: only feed items you haven't seen yet
curl -G https://crawlwisedata.com/v1/feed \
-H "Authorization: Bearer $CRAWLWISE_KEY" \
-d url=https://github.blog -d monitor=gh-blogconst res = await fetch(
'https://crawlwisedata.com/v1/techstack?url=wordpress.org',
{ headers: { Authorization: `Bearer ${process.env.CRAWLWISE_KEY}` } },
);
const { ok, data, charged } = await res.json();
console.log(data.technologyNames, charged.credits);import os, requests
r = requests.get(
'https://crawlwisedata.com/v1/techstack',
params={'url': 'wordpress.org'},
headers={'Authorization': f"Bearer {os.environ['CRAWLWISE_KEY']}"},
timeout=60,
)
print(r.json()['data']['technologyNames']){
"ok": true,
"endpoint": "techstack",
"mode": "demo",
"charged": { "credits": 0, "usd": 0 },
"balance": null,
"data": {
"url": "https://wordpress.org/",
"domain": "wordpress.org",
"statusCode": 200,
"technologyCount": 13,
"technologyNames": [
"WordPress 7.2", "Gutenberg 24.0.0", "Nginx", "PHP",
"MySQL", "Google Tag Manager", "HSTS", "RSS", ...
],
"technologies": [
{
"name": "Nginx",
"version": null,
"confidence": 100,
"categories": ["Web servers", "Reverse proxies"],
"implied": false,
"detectedBy": ["headers"]
},
...
],
"categories": {
"CMS": ["WordPress"], "Web servers": ["Nginx"], ...
}
}
}You are not buying “another scrape.” You are buying scheduling, change detection, and reliable delivery so software and AI agents stay informed.
Point us at a public site, feed, or sitemap you care about.
We schedule checks, keep state, detect new/updated/removed pages or tech changes, and skip empty noise.
When something changes we POST JSON with an HMAC signature you can verify.
Update a dashboard, notify a team, or wake an AI agent — without polling yourself.
These requests go to the production endpoints in demo mode: no key, 20 calls per day per IP (also capped per network), smaller result sizes and no monitors. Demo attempts count toward the limit even when they fail. On 429, respect Retry-After (seconds until 00:00 UTC).
Press “Run request” to call the API. The JSON response appears here.
Get 1,000 free credits on a real API key: full result sizes, named monitors and signed webhooks, no card. One key per email every 30 days; per network up to 5 requests an hour and 10 a day.
1,000 free credits, one time (about 33 tech-stack lookups or 100 feed reads). No card. One key per email every 30 days; per network up to 5 requests an hour and 10 a day. We never email you.
On-demand tech, feed, and sitemap reads — or hand us a webhook and we watch for you. Deterministic code, no AI guessing: every detection shows which signal matched.
Find the CMS, e-commerce platform, frameworks, analytics, CDN, web server and email/DNS providers behind any public page, using 7,600+ open-source fingerprints.
/v1/techstack$0.003 / pageRSS 2.0, Atom, RDF and JSON Feed, normalized into one schema. Pass a site URL and we discover the feed. Name a monitor and each call returns only items you haven't seen.
/v1/feed$0.001 / readEvery URL a site lists in its XML, gzipped or text sitemaps (found through robots.txt), with lastmod, images and hreflang. Monitors report new, updated and removed pages.
/v1/sitemap$0.001 + $0.10/1k URLsRead the API reference Free tech stack lookup
Also: free sitemap & feed checker · same demo API as the box above.
Wire Crawlwise into agent stacks without scraping our HTML. Deterministic tools — Crawlwise never runs an LLM on your request.
Import /openapi.json (or YAML) into your client generator. Includes the signed monitor.change webhook event schema.
Agent-friendly indexes at /llms.txt and /llms-full.txt pointing at docs, pricing, bot page and OpenAPI.
Local stdio package crawlwise-mcp (techstack, feed, sitemap, monitors, account). Install it from npm with npx crawlwise-mcp and add it to Claude Desktop or Cursor. Set CRAWLWISE_API_KEY. See docs.
No sales calls. Start with a free key, create a monitor, and receive a signed webhook when something moves. See the 5-step walkthrough.
Enter your email in the trial form for 1,000 credits (or buy a pack/plan). The key is shown once. Lost it? Recover.
POST /v1/monitors with a target URL, schedule: true, and your https webhook. We run scheduled checks, usually within an hour, plus check-now on demand.
We POST a signed monitor.change event. Check X-Crawlwise-Signature with your secret from GET /v1/webhooks/secret. Don't want to wait for a change? POST /v1/monitors/test sends a free signed sample now, and our demo target changes every 5 minutes. Copyable examples: docs.
Credits power both lookups and monitors. Empty scheduled checks are cheap (2 credits). Buy once, or subscribe for more watching capacity. 1 credit = $0.0001.
One-time, no renewal
100,000 credits
≈ 10,000 feed reads, or about 520 days of one monitor at the minimum interval with no changes. Also $25 (262,500 credits, +5%). Never expire while active.
See packsSide projects & small watch lists
250,000 credits / month, about 43 monitors
500 monitors · scheduled checks, usually within an hour, plus check-now on demand
Choose StarterNeed more than Starter? Email Crawlwise Data support — crawlwise.support@gmail.com for high-volume / custom limits — same product, higher caps.
Purchases are non-refundable except where law requires. Cancel stops future renewals — it is not a refund. Duplicate charges and credits never delivered get fixed. Refund terms.
Yes, three ways. Free account: create an account (0 credits) after accepting the Terms, then buy when ready. Free trial key: enter your email in the trial form (or POST /v1/trial) and get a real key with 1,000 one-time credits: full result sizes, monitors and webhooks, no card. That's enough to watch a real change arrive as a signed webhook: monitor our demo target, which changes every 5 minutes (about 50 credits). One per email every 30 days (soft IP/network caps for shared egress); disposable addresses are refused. No key at all: call any endpoint without a key, 20 calls per day per IP, with smaller results (feeds up to 15 items, sitemaps up to 75 URLs) and no monitors, use the demo box above, or the dedicated tech stack lookup / sitemap checker pages.
Unreachable sites, blocked pages (HTTP ≥ 400), timeouts, pages disallowed by robots.txt, invalid input and our own errors. Every error has the same JSON shape with "billable": false and charged.credits = 0.
Packs are one-time purchases. Nothing renews, and the credits never expire while your account is active. Plans are monthly subscriptions that renew until you cancel. Each paid month adds credits, and plans give more credits per dollar and higher limits.
We run them. POST /v1/monitors with a webhook URL and Crawlwise checks on a schedule, then POSTs a signed event when something changes. Noop checks cost 2 credits (5 for tech). You can still poll with ?monitor=NAME if you prefer. See docs.
Dashboard → Manage / cancel subscription opens the Stripe Customer Portal. Cancellation takes effect at the end of the paid period. You keep your plan and credits until then and aren't charged again.
Purchases are non-refundable except where law requires. Canceling stops future renewals — it is not a refund. We still fix duplicate charges and credits you paid for but never received. See the Terms.
Use key recovery. You prove you own your checkout email through Stripe's billing portal and we issue a new key (old keys are revoked). We can never show an existing key again because we only store a hash.
Yes. Use OpenAPI, llms.txt, or the local crawlwise-mcp MCP server (stdio). Install it with npx crawlwise-mcp. Crawlwise stays deterministic — no AI at runtime. Details: docs.
Only the free demo and public endpoints. Keyed endpoints intentionally don't send CORS headers, so your key stays on your server. Call the API from your backend.
More answers in Support & FAQ.
Get a free trial key (1,000 credits) and create your first monitor, or try the free demo with no key. When you need continuous watching, pick a pack or plan.