API access
Your AI client reaches Treasury Opportunity Zones through one ParcelOps MCP endpoint, so there is no separate key to hold for it and no per-source client to write. Reaching it takes no credentials of your own.
Where it came from
Freshness and coverage
What this source cannot tell you
- ⚠ Anything outside United States and territories represented in each official QOZ table. A request past that edge comes back empty rather than approximated.
- ⚠ Which years it spans, because the covered period is not declared.
- ⚠ Anything U.S. Treasury and CDFI Fund Qualified Opportunity Zone files does not publish. ParcelOps returns this source as it stands and never fills a blank field from a different one.
- ⚠ A published tract match is designation evidence, not tax advice, a calculation of gain deferral, or confirmation that a project or taxpayer qualifies.
- ⚠ A 2018 designation zero-match is checked against the complete official 8,764-tract CDFI list using 2010 Census tract boundaries.
- ⚠ The 2018 designation round and 2027 nomination cycle are separate datasets and are never merged into one status.
- ⚠ Confirm the relevant notice, tract-boundary vintage, effective period, parcel geography, and transaction facts.
Methods (3)
A method is one call your agent can make against this source.
listDesignationFiles
readList supported official QOZ designation and nomination workbooks.
Records returnedqoz-data-fileHow to get more resultsoffset (offsetField: offset, limitField: limit)FreshnessScheduled (source-level)Input schema
{ "type": "object", "properties": { "limit": { "type": "integer", "minimum": 1, "maximum": 100 }, "offset": { "type": "integer", "minimum": 0, "maximum": 50000 } }, "required": [], "additionalProperties": false }checkTract
readCheck one tract against the complete 2018 list or a requested nomination vintage.
What you must providetractGeoidRecords returnedqualified-opportunity-zone-tractHow to get more resultsoffset (offsetField: offset, limitField: limit)FreshnessScheduled (source-level)Input schema
{ "type": "object", "properties": { "tractGeoid": { "type": "string", "pattern": "^\\d{11}$" }, "status": { "type": "string", "enum": [ "designated", "nominated" ] }, "vintage": { "type": "integer", "minimum": 2010, "maximum": 2100 }, "limit": { "type": "integer", "minimum": 1, "maximum": 100 }, "offset": { "type": "integer", "minimum": 0, "maximum": 50000 } }, "required": [ "tractGeoid" ], "additionalProperties": false }- ⚠ Designation evidence only; not tax or investment advice.
- ⚠ The complete 2018 designation list uses 2010 Census tract boundaries; later GEOIDs must be reconciled to that vintage.
- ⚠ Nomination-cycle zero-matches apply only to the named nomination file.
getServiceInfo
readReturn files, vintages, designation semantics, and tax-use limitations.
FreshnessScheduled (source-level)Input schema
{ "type": "object", "properties": {}, "required": [], "additionalProperties": false }
Where this source is used
- Housing program eligibility checks
Check tax credit designations, rural program maps, and existing affordable inventory for an address from your own code.
- Data center siting
Power, water, transport, airspace, and hazard screening for a site before anyone signs anything.
- Commercial real estate
Parcel and assessment records, building programs, and the entity on the other side of the deal.
- Realtors and brokerages
The facts behind a listing, the programs a buyer may qualify for, and your own files in the same place.
- Is this address in an opportunity zone?
