|You pay||You receive||Average corrections|
|$1||1 megabyte of input/output||5,917 addresses|
|$10||10 megabytes of input/output||59,171 addresses|
|$100||100 megabytes of input/output||591,715 addresses|
|Get nearest Tiger line||57|
|Get Geo record||156|
(most common request)
|Get GUI record||172|
|Get city-ZIP record||190|
|Get account statistics||403|
All requests can send and receive different numbers of bytes to and from ZP4 servers. For example, you might send address correction transactions requesting only a latitude and longitude as output, or you might request many dozens of available output fields. ZP4 uses compression to minimize the number of bytes per transaction.
For each $1 you pay, 1,000,000 bytes are added to the input/output balance for your account. As you perform requests, the count of bytes sent and received are deducted from your account's balance.
While using ZP4, detailed reports are available indicating your actual input/output consumption. Once your account's balance reaches zero, your account will be locked out of further address processing transactions until more funds are supplied to increase your account's balance. Account locking may be slightly delayed if you're processing data faster than servers can reconcile your account.
After 30 days notice, ZP4 processing rates and fees for an account's unused balance are subject to change.