Credits & Pricing

Every API call consumes API Credits. Credits are deducted on successful responses only — failed requests (4xx, 5xx) cost zero.

API Credits vs Report Credits

PadStats has two separate credit systems. API Credits are consumed by REST API calls (api.padstats.io/v1/*). Report Credits are consumed by the web platform when generating downloadable reports. They are different units, tracked separately, and cannot be exchanged. This page covers API Credits only.

---

Plans & Allocation

	Standard ($100/mo)	Professional ($300/mo)	Enterprise
Monthly API Credits	1,000	5,000	Custom
Credit Cost	$0.10 / credit	$0.06 / credit	Negotiated
Top-Up Rate	$0.10 / credit	$0.06 / credit	Negotiated

The Free tier does not include API access.

---

Rate Limits

Tier	Requests/second	Requests/minute	Requests/day
Standard	5	100	5,000
Professional	15	500	25,000
Enterprise	Custom	Custom	Custom

---

Parameter Caps

Parameter	Standard	Professional	Enterprise
num_comps max	10	15	30
limit (crime incidents)	100	500	1,000+
census_keys max per request	5	10	50
units array (multi-unit rental POST)	10	10	200
Crime lookback window	6 months	18 months	36 months

---

Endpoint Credit Costs

Hazard Lookups (10 credits each)

Endpoint	Credits	Reference
GET/POST /v1/flood-zone	10	Reference
GET/POST /v1/storm-surge	10	Reference
GET/POST /v1/fire-risk	10	Reference
GET/POST /v1/sinkhole-risk	10	Reference

Census Data (1 credit per key)

Endpoint	Credits	Reference
GET/POST /v1/census-data	1 per census key	Reference
POST /v1/census-data/by-geoid	1 per census key	Reference

Examples: 3 keys = 3 credits. 10 keys = 10 credits.

Socioeconomic Data (20 base, geographic multiplier)

Endpoint	Reference
GET/POST /v1/socioeconomic-data	Reference
GET /v1/socioeconomic-data/by-geoid	Reference

Base cost is 20 credits, scaled by the geographic level requested:

Geography	Multiplier	Credits
Block group	1.0x	20
Tract	0.9x	18
County subdivision	0.8x	16
County	0.7x	14
All geographies	2.5x	50

Natural Hazards (20 base, geographic multiplier)

Endpoint	Reference
GET /v1/natural-hazards	Reference

Same geographic multiplier as socioeconomic data — 20 credits base, scaled by geography level.

Crime Data (10+ credits)

Endpoint	Credits	Reference
GET/POST /v1/crime-data	10 base	Reference

When include_crime_details returns incidents, additional credits are charged at 1 credit per 5 incidents returned (rounded up).

Incidents Returned	Base	Incident Cost	Total
0 (summary only)	10	0	10
1–5	10	1	11
6–10	10	2	12
11–20	10	4	14
21–50	10	10	20
51–100	10	20	30

Property Valuation (40 + comps)

Endpoint	Base	Variable	Formula	Reference
GET/POST /v1/avm/property	40	+1 per comp	40 + num_comps	Reference

Comps Requested	Total Credits
0	40
5 (default)	45
10	50
15 (Professional max)	55

Rental Valuation (30 + units + comps)

Endpoint	Base	Variable	Formula	Reference
GET /v1/avm/rental (single unit)	30	+1 per comp	30 + num_comps	Reference
POST /v1/avm/rental (multi-unit)	30 first unit, +10 per additional	+1 per comp (shared)	30 + (10 x extra_units) + num_comps	Reference

Multi-unit rental examples (5 comps):

Units	Base	Comps	Total
1	30	5	35
2	40	5	45
3	50	5	55
6	80	5	85
10	120	5	125

Multifamily Valuation (60–80 + comps)

Endpoint	Base	Variable	Formula	Reference
GET/POST /v1/avm/multifamily (2–4 units)	60	+1 per comp	60 + num_comps	Reference
GET/POST /v1/avm/multifamily (5+ units)	80	+1 per comp	80 + num_comps	Reference

Batch AVM (same per-item cost)

Batch endpoints charge the same credit cost per item as the corresponding single-call endpoint. There is no batch discount — the batch API is a convenience for submitting multiple valuations in a single request.

Endpoint	Per-Item Cost	Reference
POST /v1/avm/batch/property	40 + comps (per property)	Reference
POST /v1/avm/batch/rental	30 + units + comps (per property)	Reference
POST /v1/avm/batch/multifamily	60–80 + comps (per property)	Reference

Example: A batch of 10 property valuations with 5 comps each = 10 x 45 = 450 credits.

---

Quick-Reference Table (Sorted by Cost)

Credits	Endpoint	Notes
1/key	/v1/census-data	Per census key requested
10	/v1/flood-zone
10	/v1/storm-surge
10	/v1/fire-risk
10	/v1/sinkhole-risk
10+	/v1/crime-data	+1 per 5 incidents returned
14–50	/v1/natural-hazards	20 base, geographic multiplier
14–50	/v1/socioeconomic-data	20 base, geographic multiplier
30 + comps	/v1/avm/rental	Single unit. +1/comp
30/unit + comps	/v1/avm/rental (multi-unit POST)	+10 per extra unit. +1/comp
40 + comps	/v1/avm/property	+1/comp
60 + comps	/v1/avm/multifamily (2–4 units)	+1/comp
80 + comps	/v1/avm/multifamily (5+ units)	+1/comp

---

Dollar Cost Examples

Typical Call	Credits	Standard ($0.10)	Professional ($0.06)
Census (3 keys)	3	$0.30	$0.18
Flood zone lookup	10	$1.00	$0.60
Fire/storm/sinkhole risk	10	$1.00	$0.60
Socioeconomic (block group)	20	$2.00	$1.20
Socioeconomic (all geographies)	50	$5.00	$3.00
Natural hazards (block group)	20	$2.00	$1.20
Crime summary	10	$1.00	$0.60
Crime report + 50 incidents	20	$2.00	$1.20
Single rental (5 comps)	35	$3.50	$2.10
6-unit rental (5 comps)	85	$8.50	$5.10
Property valuation (5 comps)	45	$4.50	$2.70
Small MF valuation (5 comps)	65	$6.50	$3.90
Large MF valuation (5 comps)	85	$8.50	$5.10

---

Usage Scenarios

Standard (1,000 API Credits/month)

Scenario	Credits Used
15 property valuations (5 comps) + 30 flood checks + 20 crime summaries	675 + 300 + 200 = 1,175 (175 overage)
Data-only: 100 flood zone lookups	1,000
20 single-unit rentals (5 comps) + 10 census (3 keys each)	700 + 30 = 730

Professional (5,000 API Credits/month)

Scenario	Credits Used
60 property valuations (5 comps) + 100 flood checks + 50 crime summaries + 50 socioeconomic (block group)	2,700 + 1,000 + 500 + 1,000 = 5,200 (200 overage)
30 large MF (10 comps) + 30 six-unit rentals (5 comps)	2,700 + 2,550 = 5,250 (250 overage)
Data-only: 500 flood zone lookups	5,000

---

Credit Response Metadata

Every API response includes credit information in the metadata.credits object:

{
  "metadata": {
    "credits": {
      "charged": 45,
      "remaining": 4955,
      "pool": "api",
      "breakdown": {
        "base": 40,
        "variable": 5,
        "description": "Property valuation: 40 base + 5 comps"
      }
    }
  }
}

Field	Description
charged	Total API credits deducted for this request
remaining	API credits left in your monthly pool
pool	Always "api" for REST API calls
breakdown	Human-readable cost explanation

Failed requests return "charged": 0. Deduplicated requests within the 5-minute idempotency window also return "charged": 0.

---

Top-Up & Overage

When your credit pool hits zero:

• Auto-top-up OFF (default): requests return 402 insufficient_credits
• Auto-top-up ON: credits are replenished automatically and charged to your card

Top-up pricing is the same as your plan rate — no penalty. Configure auto-top-up, block sizes, and spending caps in your dashboard.

Notifications are sent at 80% usage, 100% usage, and when auto-top-up triggers.

Unused credits do not roll over at cycle reset.