HTTP Status Codes
Partial data
PropX402 always returns a response even when individual sources fail. Failed sources return anote key instead of data:
500 error.
Reference
Errors & Limits
HTTP status codes, partial data handling, and rate limits
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
HTTP status codes, partial data handling, and rate limits
| Status | Meaning | Action |
|---|---|---|
200 | Success | Data returned in data object |
402 | Payment Required | Expected — x402 client pays and retries automatically |
400 | Bad Request | Missing or empty address in request body |
500 | Intel Fetch Failed | Address not geocoded or critical upstream failure — check address format |
504 | Gateway Timeout | Vercel 30s limit exceeded — upstream API was slow, retry |
note key instead of data:
{
"floodRisk": {
"note": "FEMA API unavailable",
"zone": null
}
}
500 error.
✅ "1411 8th Ave SE, Cedar Rapids, IA 52403"
⚠️ "1411 8th Ave SE" ← may fail geocoding