Know when any data connector fails silently.
Even when everything looks "up." Monitor API credentials, usage quotas, and scraper output quality across your whole pipeline on a schedule you choose. One alert when it degrades, one notice when it recovers.
$0.02 per check • No subscription
Your pipeline degrades silently.
Your SerpAPI quota runs out. Your GitHub PAT expires over the weekend. The TikTok or LinkedIn Actor your pipeline depends on ships a changed output schema. Its maintainer's decision, not yours. None of it crashes your app. Your output just gets quietly worse until a customer notices. Datasource Pulse notices first.
Catch expiration before it breaks
Rotate a key on your schedule, not after a customer complains.
Track quota proactively
Know when you're at 80% before you hit the 100% wall.
Catch output schema changes
A maintainer renames one field and your tables fill with nulls → you'll know the run it happens, not weeks later.
Reduce incident response time
One message the moment something degrades, not hours later.
Maintain downstream SLAs
Your data products stay reliable even when your vendors aren't.
Visibility across your stack
One check instead of logging into every vendor console separately.
The steady pulse of reliable infrastructure.
Datasource Pulse runs on a schedule you choose. It probes your connectors, compares them to the last known state, and fires exactly one deduplicated alert when things change.
1. Scheduled Trigger
Runs every 1-6 hours, or triggered on-demand by an AI agent.
2. Probe Data
Checks credential health, quotas, or scraper output quality across any source you point it at.
3. State Check
Compares result to previous memory. Detects degradation or recovery.
4. One Alert
Fires a single Slack message on change. Logs a record to your dataset.
No alert storms.
If a connector fails, you get one alert. If it's still failing on the next run, we stay quiet. You only hear from us again when it escalates (like a quota going from 80% to 100%) or when it recovers.
- Includes the specific failure classification (e.g.,
quota_exhausted) so you know exactly what to fix. - Echoes your custom impact note verbatim so the on-call engineer knows what broke downstream.
{
"transition": "healthy -> failing",
"connector_id": "serpapi-main",
"failure_class": "quota_exhausted",
"message": "SerpAPI failing...",
"impact": "Search indexing halted",
"metadata": {
"quota_used_pct": 100.0
}
}Credential & Quota Health
We make the cheapest authenticated call per vendor: enough to prove your token is alive and read your current usage. Know when you're at 80% capacity before you hit the wall.
Catch Dead Tokens
Validates API keys, OAuth refresh tokens, and Bearer tokens without consuming expensive credits.
Custom Quota Soft Caps
Evaluate warnings against your budget line, not the vendor's billing wall. Get notified before an unexpected spike costs you thousands.
Any endpoint. The current 35+ pre-wired list is a head start, not a limit.
Not on the list? One generic_http check monitors anything with a URL: your own API, a partner feed, your database's REST or health endpoint. And the pre-wired list keeps growing.
"vendor": "openrouter",
"quotaSoftCap": 50.00
Scraper Output Quality
Official APIs are locked down, so your pipeline probably depends on third-party scrapers (TikTok, Google Maps, LinkedIn) built by someone else. When their maintainer pushes a breaking schema change, your app quietly consumes garbage data.
Datasource Pulse monitors the Actors you don't own.
{"check_type": "actor","connector_label": "Compass Google Maps","state": "failing","failure_class": "schema_drift","message": "Output schema changed.","metadata": {"missing_fields": ["reviewsCount", "price"],"new_fields": ["review_metrics"],"actor_id": "compass~google-maps"}}
Alert fired before your ETL job ingested the missing fields.
Agent-first architecture.
AI agents build autonomous data pipelines. Datasource Pulse is the drop-in reliability check that tells them when their tools are broken.
API & MCP Ready
Discoverable and callable as a tool via the Apify API and MCP. Takes a structured JSON input manifest, returns exactly one status record per connector.
Agent access docs →Machine-Readable Errors
No parsing human error strings. A stable failure_class enum (dead_token, schema_drift, rate_limited) lets agents branch logic automatically.
x402 Payments · Live
Agents buy health checks from our API today: $0.02 in USDC on Base, no account of any kind. Listed in Coinbase’s x402 Bazaar, settled on-chain, verifiable by anyone.
Radically simple pricing.
Pay for the check, not the result. A dead token or exhausted quota still bills, because catching that failure is exactly the value you're paying for.
Pay per event
No subscriptions. No per-run minimums.
- Charge applies on attempt (failures count)
- Subset recheck: preflight expensive jobs by checking just one key
- Set a hard max cost ceiling per run
- x402 agentic payments supported (USDC on Base)
Frequently asked questions
How do I get an alert when a data feed goes stale?
Watch freshness, not uptime: a stale feed still answers 200. The manual route is a daily job comparing the feed’s newest timestamp against a threshold set just past its update cadence. The automated route is a Datasource Pulse check on the actor or endpoint producing the feed: zero-yield streaks, volume drops against a learned baseline, and abandoned-scraper warnings, each as a named alert with a recovery notice when the feed comes back, at $0.02 per check. Full walkthrough of both routes: how to get an alert when a data feed goes stale.