You can turn a Cortese screen into a reviewable source record

POST /api/cortese/check returns the fields you need to document a first-pass public-source screen. Keep the resolved input, source URL, source version, query time, result state, returned record, and limitation together. That record lets a reviewer reopen the source and follow your project-specific conclusion.

Perminal accepts a street address or latitude,longitude pair. APN lookup returns 422 input_unresolved while licensed parcel geometry remains unavailable.

The API response gives you the source record fields

Response field What you retain Why the reviewer needs it
outcome The exact overall state Shows whether candidates returned, all sources returned zero candidates, the input failed, or source coverage remained incomplete
input.normalized The matched address or supplied coordinate text Identifies the location that Perminal screened
input.method US Census Bureau Geocoding API or user-supplied coordinates Separates geocoded input from a supplied point
input.point The latitude and longitude used in source queries Preserves the actual search center
sources[].source and sources[].url The publisher/source name and direct source URL Lets the reviewer reopen the source
sources[].version and sources[].retrieved_at The snapshot or service version and source time Binds the result to the source state used
sources[].result records_returned, no_record_returned, or source_unavailable Preserves each source’s own result state
sources[].records The records returned from that named source Keeps the reported source facts available for review
sources[].source_documents The two Cortese PDF names, URLs, and SHA-256 values Identifies the exact PDFs behind a Cortese snapshot result
limitation The returned locality-candidate boundary Keeps the source result separate from parcel and CEQA determinations

The current production response uses GeoTracker snapshot 2026-09-01-93f63469bdef and Cortese snapshot 2026-02-03-09ff27156893. EnviroStor identifies its request-time query of FeatureServer layers 0, 1, and 2.

You capture the resolved input before reviewing the results

  1. Save input.normalized, input.method, and input.point from the response.
  2. Compare a geocoded address to the address in your project file.
  3. Resolve any material address mismatch before interpreting the source results.
  4. Record the 402.336-meter search distance from the method record.

The screen uses a point and radius. Your later project review supplies the parcel and footprint relationship.

Each source row carries its own result state

Read the source rows before the overall outcome.

Source result What the response establishes What you review next
records_returned The named source returned one or more records within its configured point screen. Open each returned record and evaluate its project relationship.
no_record_returned The named source returned zero records within its configured point screen. Confirm the source, version, method, and other applicable section 65962.5 categories.
source_unavailable The request, pointer, manifest, or required shard failed the source contract. Repeat the source check or retrieve the public source directly.

Copy the row’s source, url, version, retrieved_at, result, and records together. A source-specific zero-record result keeps its meaning only while those fields remain attached.

The overall outcome tells you whether source coverage completed

Overall outcome Response meaning Documentation treatment
locality_candidates_returned At least one available source returned a candidate and every required source completed. Record each candidate and continue to the underlying public records.
no_locality_candidates_returned Every required source completed and returned zero candidates within the configured point screen. Record every source row and the limits of the point screen.
source_unavailable At least one required source failed its contract. Identify the unavailable source and leave the source question open.
input_unresolved The input was empty, malformed, unmatched by the Census geocoder, or an APN. Correct the input or use an accepted address or coordinate.

An overall candidate outcome does not establish parcel inclusion. An overall zero-candidate outcome does not establish parcel clearance. Government Code section 65962.5 covers agency list categories beyond any one portal or export.

You open each returned public record

For every candidate, open the source URL from the response. Match the returned identifier, program, status, location, and source date to the public record. Compare that source record with the project footprint and current site information.

The Cortese PDF-derived snapshot uses coordinates from the source rows. Treat each returned row as a locality candidate until an authoritative parcel or agency record establishes the project relationship.

Your setting sentence names the verified source fact

Write the setting from the public record you opened. Name the agency, program or dataset, record identifier, relevant source fact, and source date. Cite the direct record or source file.

Keep the screen method in the supporting record. Use it in the setting sentence only when the query distance or source version is material to the statement.

Your review record keeps the decision owner visible

Use this worksheet in the project file:

Field Project entry
Screen input and method
Query time and 402.336-meter point screen
Overall outcome
Source name, URL, version, time, and result
Returned record identifier and source fact
Project relationship reviewed
Limitation or unavailable-source follow-up
Initial Study sentence and direct citation
Reviewer and review date

Store the response and worksheet under the project’s access controls. The anonymous API response uses Cache-Control: no-store and X-Robots-Tag: noindex, nofollow. Perminal returns it only in the response and supplies no persistent result URL.

You document the next screen with one source record

Run the screen with an accepted address or coordinate. Complete one worksheet row for each returned source before drafting the Hazards and Hazardous Materials setting.

These sources let you verify the method

Relatedcortese list 65962 5
Published 2026-09-09 · Last reviewed 2026-09-09. Review record.