CrawlDex
Preflight detail

stripe.com

dev_saas_api.check_rate_limits

healthy recipe://dev_saas_api.check_rate_limits/stripe-rate-limits/v1
Hold / Collect evidence first

Do not trust this route yet

The current evidence set is too thin for a confident agent decision.

Next: Run a canary or submit a trusted outcome before allowing an agent to attempt this unsupervised.
90AES
90% outcome rate
Evidence and trust

low trust

32%
basisBased on 2 evidence samples from catalog reporters.2
sourceSources: public web observation.
nextTreat this as directional until trusted canaries or operator reports arrive.
Confidence low 28%
Evidence 2 public web observation
Freshness 0d fresh
Blockers 0 none
Recipe

Read Stripe's rate-limit page, detect 429 headers, implement backoff, and use idempotency keys for retryable POST operations.

active
recipe://dev_saas_api.check_rate_limits/stripe-rate-limits/v1
  1. Open the official public source page and verify the current task path before acting. Source URL, page title, and task-specific branch are captured.
  2. Enter the task surface only after matching the user's goal to the documented path. Required identity, payment, policy, or JavaScript gate is visible.
  3. Stop at any irreversible, paid, or account-mutating step until the user approves. Final-state language and user approval are captured.
Dimension scores

Why the route scores this way

reachability 90
navigability 90
task completability 90
transactability 90
recoverability 90
policy parseability 90
trust safety 90
efficiency 90
Issue flags

Known blockers

none
Policy notes
observation methodpublic official help or docs page
observation date2026-06-09
rate limit docspublic
retry headersstripe rate limited reason
idempotencypost requests accept idempotency keys
source urlshttps://docs.stripe.com/rate-limits | https://docs.stripe.com/api/idempotent requests
Recommended actions

Remediation queue

  • lowagent
    Use Stripe's published headers and idempotency guidance when planning API automations. Improves reliability and lowers accidental duplicate mutation risk.
Agent handoff

Copy this into an agent runbook

dev_saas_api.check_rate_limits
Before attempting dev_saas_api.check_rate_limits on stripe.com, check CrawlDex. Current verdict: Collect evidence first. Run a canary or submit a trusted outcome before allowing an agent to attempt this unsupervised.
curl -sS -X POST /api/v1/preflight \
  -H 'content-type: application/json' \
  -d '{"site":"stripe.com","task":"dev_saas_api.check_rate_limits","agent_profile":{"stack":"browser-use","browser_runtime":"playwright"}}'
Preflight contract 
{
  "site": "stripe.com",
  "task": "dev_saas_api.check_rate_limits",
  "agent_profile": {
    "stack": "browser-use",
    "browser_runtime": "playwright"
  }
}