Schema library gov-public-records

Return a property-tax record from a public page.

Pass this JSON Schema and a public source URL to/extract/json. Normalize public parcel, assessment, tax, owner, and date fields defined in the schema.

Use this schema The JSON file

tabstack.ai/pricing

TEXT

MARKDOWN

LINKS

extract.tsTypeScript

const res = await client.extract.json({
  url: 'https://example.com/pricing',
  json_schema: {
    type: 'object',
    properties: {
      plan: { type: 'string' },
      price: { type: 'number' },
    },
  },
})

res = client.extract.json(
    url='https://example.com/pricing',
    json_schema={
        'type': 'object',
        'properties': {
            'plan': {'type': 'string'},
            'price': {'type': 'number'},
        },
    },
)

tabstack extract json https://example.com/pricing \
  --schema '{"type":"object","properties":{"plan":{"type":"string"},"price":{"type":"number"}}}'

What it captures

Fields in this property-tax record.

Property tax assessment and payment record from a county assessor or tax collector.

Field	Type	What it holds
`parcel_number`	string, required	Assessor's parcel number (APN) or folio number.
`address`	string, required	Property street address.
`city`	string, required	City of the property.
`county`	string, required	County of the property.
`state`	string, required	State of the property.
`zip_code`	string	ZIP code of the property.
`latitude`	number	Latitude coordinate of the property.
`longitude`	number	Longitude coordinate of the property.
`owner_name`	string	Name of the property owner.
`owner_mailing_address`	string	Mailing address of the property owner.
`property_type`	string	Property use type (e.g., single family, commercial).
`land_value_usd`	number	Assessed value of the land in USD.
`improvement_value_usd`	number	Assessed value of improvements in USD.
`total_assessed_value_usd`	number, required	Total assessed value in USD.
`market_value_usd`	number	Estimated market value in USD.
`tax_year`	number, required	Tax year for this record.
`annual_tax_usd`	number, required	Annual property tax amount in USD.
`tax_rate_pct`	number	Effective tax rate as a percentage.
`exemptions`	array	Tax exemptions applied (e.g., homestead, senior).
`tax_status`	string	Current tax payment status.
`last_sale_price_usd`	number	Price from the most recent sale in USD.
`last_sale_date`	string	Date of the most recent sale.
`zoning`	string	Zoning classification of the property.
`page_title`	string	Title of the source page. Tabstack auto-fills this from page metadata when left empty.
`favicon`	string	Favicon URL of the source page. Tabstack auto-fills this from page metadata when left empty.

Example

Inspect and validate the response shape.

The example below is generated from the schema to demonstrate its structure. Edit the object or paste a real response to validate it in your browser.

What it checks

Pass or fail, and the first reason why.

Whether the text parses as JSON, whether the top level is an object, and whether each field the schema requires is present at the declared type. A null is allowed anywhere. Every key you ask for is present. A field the page does not state can come back null, empty, a placeholder number, or a guessed value. Validate values, not just keys.

Example data, not a live response.

Usage

Send the schema with your source URL.

The schema travels with the request rather than living on your account, so the same call can send a trimmed version for one page and the full one for another. Every key you ask for is present. A field the page does not state can come back null, empty, a placeholder number, or a guessed value. Validate values, not just keys.

property.tsTypeScript

import schema from './property-tax-record.json'

const res = await client.extract.json({
  url: 'https://example.com/pricing',
  json_schema: schema,
})

tabstack extract json 'https://example.com/pricing' \
  --schema @./property-tax-record.json

Adaptation

Make the schema match your application.

The schema is a starting point, not a guarantee that every source page contains every field. Three things are worth doing before you write one into your system, and the schema-authoring guide covers the rest.

Remove what you do not need

A shorter schema is a smaller response and fewer fields to handle.

Describe the ambiguous ones

A description tells Extract what to look for when a label could mean two things.

Validate before you store

Check the returned object against the schema rather than trusting it.

Related schemas

Other schemas in this category.

Same category: building permit.
Same category: business registration.
Same category: court filing / case.
The job rather than the object: the Extract API.