Terms of Use & Acceptable Use Policy

Free endpoints

/v1/endpoints, /v1/liveness, /v1/ecosystem, /v1/categories, /v1/providers, /v1/runs, /v1/health, /.well-known/x402

10 requests / minute per IP address (browse endpoints). Infrastructure endpoints (/health, /ecosystem, /categories) allow up to 60 req/min.
Sufficient for dashboard browsing and integration testing. Not intended for automated production workloads.

Paid endpoints

/v1/search ($0.002/query), /v1/history ($0.003/query), /v1/agent-search ($0.004/query), /v1/route ($0.005/query)

60 requests / minute per IP address.
Paid traffic receives full throughput. Payment is enforced independently of rate limits.

Thresholds for suspension

IP addresses that generate more than 500 requests in 10 minutes or more than 2000 requests per hour may be automatically suspended without prior notice.

Permitted

• Querying data for your own product or research
• Building applications and AI agents that consume the API
• Automated queries within rate limits
• Accessing paid endpoints using legitimate x402 payments
• Caching responses locally for reasonable periods (up to 24 hours for liveness data)

Prohibited

• Systematic bulk scraping of the full endpoint catalogue
• Reselling or redistributing raw API data as a competing product
• Circumventing rate limits using proxies, VPNs, or IP rotation
• Replay attacks or forging x402 payment headers
• Denial-of-service or stress-testing without written permission
• Automated enumeration of all endpoints for competitive intelligence extraction
• Using the service for illegal purposes or in violation of applicable law

Automatic enforcement

Our infrastructure monitors traffic patterns in real time. IP addresses exhibiting abusive behavior — including rate limit violations, payment fraud attempts, or traffic patterns consistent with enumeration attacks — are automatically blocked at the network layer.

Automatic blocks may be temporary (minutes to hours) or permanent, depending on severity.

Manual bans

We reserve the right to block any IP address, CIDR range, or autonomous system (ASN) that violates these terms, at our sole discretion, with or without prior notice.

Appeals

If you believe your IP was blocked in error, contact us at the contact page with your IP address and a description of the usage. Legitimate use cases can be whitelisted upon review.

No refunds for banned accounts

x402 payments are settled on-chain and are final by protocol design. If access is terminated due to policy violation, no refunds of prior payments are issued.

Source of data

All endpoint data is sourced from publicly accessible registries (primarily the CDP Bazaar) and from active liveness probing of publicly listed HTTP endpoints. No private or authenticated APIs are queried.

Accuracy

Liveness scores, metadata, and AI-enriched descriptions are provided for informational purposes. They reflect observed behavior at the time of the last check and may not represent current reality. Use of this data for financial or production-critical decisions is at your own risk.

AI-generated content

Category labels, descriptions, and tags marked as AI-enriched are generated by a language model based on observed endpoint metadata. They may contain errors or omissions. We make no warranty of accuracy for AI-generated fields.

Per-provider endpoint cap

To ensure dataset diversity and fair resource allocation, x402dash enforces a maximum of 100 indexed endpoints per provider host. Providers that register more than 100 endpoints (e.g. by expanding parametric URL variations such as /stocks/AAPL, /stocks/META) will have their endpoints deduplicated by path template and capped.

Selection criteria: endpoints are grouped by URL pattern (collapsing numeric IDs, tickers, and date segments), and the highest-scored endpoint per unique pattern is retained. If unique patterns still exceed the cap, top endpoints by liveness score are kept.

Why this policy exists

Parametric URL expansion (registering every permutation of an API as a separate endpoint) consumes disproportionate monitoring resources without adding meaningful coverage. A single provider registering thousands of near-identical URLs degrades the quality of aggregate statistics and wastes liveness-check bandwidth that benefits the entire ecosystem.

This cap is applied uniformly to all providers. It is not a ban or content moderation decision.