The agenda memo uses approximately $190,000 and describes additional services, including a complaint hotline and portals. Staff salaries are separate.
For developers & City staff
A public, read-only JSON API.
No API key is required for this demonstration. Both single checks and batches use the same matching rules and source data.
/api/permits/v1/Source metadata & examples/api/permits/v1/verify.phpCheck a permit and address/api/permits/v1/batch.phpCheck 1–100 propertiesCopy a single-property request
curl 'https://ccstra.org/api/permits/v1/verify.php' \
-H 'Content-Type: application/json' \
--data '{"permit_number":"27200","address":"505 Scotland Drive"}'Understand the results
| Result | What the snapshot says |
|---|---|
active_in_snapshot | Permit, street, and unit match a record marked Active. |
inactive_in_snapshot | The record is expired, suspended, closed, or otherwise inactive in the source. |
address_mismatch / unit_mismatch | The submitted property does not match the permit's recorded property. |
unit_required | The permit is for a specific unit; the request omitted it. |
not_found | The number is absent from this snapshot. This does not establish a violation. |
needs_review | Incomplete, conflicting, or ambiguous source information prevents a decision. |
passes_snapshot_check is true, false, or null. current_validity always remains unknown. An HTTP 200 means a check completed, not that a permit passed. Batch entries with invalid input carry their own 422 status.
Integration limits & receipts
Maximum request body: 64 KiB. Maximum batch: 100 properties. Supply a string reference to correlate each batch entry. Malformed JSON returns 400; invalid fields return 422; unsupported content types return 415; an unavailable snapshot returns 503.
Each completed check includes a random demo receipt ID, a check timestamp, the source date, and its SHA-256 version. Receipts are not signed, retained, or issued by the City. A fresh receipt is not proof of fresh permit data.
GET is also supported for single checks. POST is preferable because it keeps the submitted address out of the URL. This demo is public and does not require authentication. A production service would need operational monitoring, access and rate-limit policies, correction procedures, and a live City data connection.
Check the underlying documents
Sources, assumptions & scope
Reviewed November 22, 2026. Cost scenarios above are illustrations, not procurement quotes. This proposal targets license compliance at booking and uses existing complaint channels; it does not claim to replace every service in the City's proposed software package.
- City staff STR presentation, slide 18. Shows $200,000 for software and $556,977 in recurring staffing costs, totaling $756,977 annually. Official presentation PDF.
- Agenda memo for item 26-1676, updated November 5, 2026, pp. 4–5. Estimates approximately $190,000 annually for software, subject to vendor selection and monitoring scope, and describes the bundled functions. Official agenda memo PDF.
- City of Corpus Christi STR guidance. Directs complaints to online Code Enforcement, 311, or STRComplaints@CorpusChristiTX.gov. The per-call or staff-time allocation proposed here is not represented as an existing City arrangement. Official STR information.
- Bodin v. New Orleans, No. 25-30524 (5th Cir. Aug. 5, 2026). The platform analysis appears on pp. 10–14; p. 3 discusses the separate reporting claim. Official opinion PDF · October 30 rehearing order · Fifth Circuit jurisdiction.
- New Orleans implementation. The City announced that platform verification began August 1, 2025. Official announcement.
- CCSTRA demonstration data. The existing May 20, 2026 historical permit snapshot powers the examples; it cannot establish current eligibility or later suspensions. Live source metadata · Map methodology.