Verify before booking

01 / A practical proposal for Corpus Christi

Verify the license.
Then accept
the booking.

Before committing to a large annual software package, test a focused alternative: require booking facilitators to verify a property's license through a free City API.

The slide describes listing monitoring, inspection, licensing, and nuisance reporting software. The agenda memo estimates $190,000. These are proposed package costs, not a signed contract price. Sources & scope

02 / Spend on the outcome

Price a smaller system.
Make the full package justify its cost.

The goal is to stop unlicensed bookings. A live permit registry and automated checks could meet that goal on participating services at a fraction of the recurring software budget. Get actual build and support bids, then measure the result.

City's proposed package
$200,000per year in the staff presentation

The agenda memo uses approximately $190,000 and describes additional services, including a complaint hotline and portals. Staff salaries are separate.

Presentation, slide 18 · Agenda memo, pp. 4–5

Explore a smaller budget$25,000
12.5%of the $200,000 software figure
$175,000difference before other program costs

Scenario, not an estimate or vendor quote. Actual hosting, live data integration, maintenance, security, and support costs need bids. Initial development, legal work, 311 allocations, and enforcement staff are additional. This is not a forecast of total program savings.

Buy only the functions the City actually needs. Inspections are outside this proposal; complaints can use the existing 311 channel.

03 / Put the check into the transaction

One City registry.
A check at every covered booking.

An API is a simple way for a booking service to ask the City: does this license currently authorize this exact property and unit?

  1. 01

    The City maintains the record

    License number, standardized address, unit, expiration date, and effective suspension or revocation status.

  2. 02

    The booking service verifies

    Before accepting a booking, the facilitator submits the license and property details to the City's free verification service.

  3. 03

    The response controls the booking

    A valid match allows the transaction. An invalid license or property mismatch blocks it. Ambiguous data and outages follow a defined review and retry process.

  4. 04

    Existing properties are rechecked

    Require weekly portfolio checks and checks when permit details change, so later expirations and suspensions are detected. Seven days is this proposal's interval.

Coverage follows the booking activity.

Define a covered facilitator by its compensated role in conducting, facilitating, or completing Corpus Christi STR bookings. Include qualifying marketplaces and direct-booking engines, regardless of branding. A company's actual role and control determine whether it is covered; simply displaying an advertisement is different.

Platforms collect permit details from hosts for verification. The City can return an eligibility result without guest names or payment information. A production ordinance must define duties, outage handling, notice, and review.

04 / Use the systems already in place

311 for complaints.
Verification for bookings.

311

One complaint channel

The City already directs STR complaints to 311, its online Code Enforcement service, and its STR complaint email. Route reports through those existing channels.

City STR guidance →
Cost / call

Charge the program for its use

Tag STR-related calls and cases. Propose an allocation from the STR fund to cover documented handling costs, using a supportable per-call rate or actual staff time.

A proposed internal cost allocation, subject to finance and legal review. This is not a fee charged to the caller.

Audits

Focus staff on exceptions

Check whether booking services comply, investigate reported bypasses, resolve permit-data errors, and follow up on repeat nuisance cases.

Track call volume, response time, staff hours, and outcomes so the public can see where the money goes.

Start with the channels that actually generate bookings.

Broad adoption can make unlicensed properties harder to book without finding every advertisement first. Measure platform coverage and outcomes; offline bookings, evasive operators, and nonparticipating services still require targeted enforcement.

Free verification for platforms. Existing 311 for residents. Documented costs for the STR fund.

06 / The request to City Council

Price it. Pilot it.
Publish the results.

Direct staff to evaluate a focused verification ordinance and obtain a fixed-price build proposal plus an annual support quote before committing to the larger software package.

Build the minimum useful service

  • Connect the current City license registry and correct addresses and units.
  • Provide free, documented single-property and batch verification.
  • Define platform duties, notice, appeals, outages, and data correction.
  • Use existing 311 and a documented allocation for STR complaint handling.
  • Exclude inspections from this proposal.

Measure the enforcement result

  • Booking services connected and coverage achieved.
  • Invalid or mismatched booking attempts blocked.
  • Incorrect denials corrected and time to resolution.
  • Service availability, response times, and support hours.
  • Total build cost, ongoing cost, and staff time per resolved case.

The question for the City: what does it cost to prevent an unlicensed booking?

See the working proof of concept →

07 / A working proof of concept

—Active in the snapshot
—Permit records, including history
May 20, 2026Permit status date

Try the working API

One property or a whole portfolio.

Property details

Use the City license number and the actual rental address. Include a condo or apartment unit when applicable.

Corpus Christi, Texas. Street abbreviations are accepted; different units remain separate properties.

Try an example

Verification result

Ready to check

Submit the example property or enter a permit and address from the map.

The response will always identify itself as a demonstration and report current validity as unknown.

This demonstration does not change permits or listings, contact booking platforms, or issue enforcement notices. The live City data connection and platform integrations are proposed next steps.

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.

GET/api/permits/v1/Source metadata & examples
POST/api/permits/v1/verify.phpCheck a permit and address
POST/api/permits/v1/batch.phpCheck 1–100 properties
Copy a single-property request
cURL
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
ResultWhat the snapshot says
active_in_snapshotPermit, street, and unit match a record marked Active.
inactive_in_snapshotThe record is expired, suspended, closed, or otherwise inactive in the source.
address_mismatch / unit_mismatchThe submitted property does not match the permit's recorded property.
unit_requiredThe permit is for a specific unit; the request omitted it.
not_foundThe number is absent from this snapshot. This does not establish a violation.
needs_reviewIncomplete, 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.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. New Orleans implementation. The City announced that platform verification began August 1, 2025. Official announcement.
  6. 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.