x402 Rate Limits and Usage Controls

Elfa x402 endpoints use server-side request limiting. Unlike API-key plans, x402 has one baseline and no tiered subscription limits.

Current x402 Limits

	x402
Limit	1,000 requests
Window	60 seconds
Scope key	Client IP address (Express default limiter key)
Applies to	Documented /x402/v2 data, chat, and auto endpoints
Response on exceed	429 Too Many Requests

Additional x402 Safeguards

Chat flows also include abuse protections (temporary/permanent blocking logic) that are separate from the RPM limiter. These are behavior-based and not published as fixed RPM quotas.

Best Practices

1. Cache responses where possible.
2. Add exponential backoff with jitter for 429 retries.
3. Avoid large traffic bursts from a single egress IP.
4. Monitor 429 frequency and tune concurrency.

For authentication and pricing details, see x402 Payments.