StreetProof
Claim

Machine readiness

Search & AI readiness center

This page is the short audit trail for search engines, AI platforms, agent developers, journalists, and data partners deciding whether StreetProof is ready to ingest. It lists the public machine surfaces, licenses, citation rules, freshness, coverage limits, and known gaps in one place.

12
public records
139
public observations
3
launched cities
low
coverage level

Machine surfaces

These are the current public integration surfaces. Read access is free for AI, search, and research use. API keys are for rate limiting, partner portal access, quota visibility, and attribution tracking.

llms.txt

published · text/plain
Short machine digest for AI crawlers and assistants.
→

llms-full.txt

published · text/plain
Extended digest with methodology summary, endpoints, cities and top records.
→

Sitemap

published · application/xml
Search discovery for city indexes, entity records, studies, stats and trust pages.
→

OpenAPI 3.1

published · application/json
REST contract for machine consumers.
→

MCP server

active · streamable-http
Typed agent tools for physical-presence checks and StreetPulse feeds.
→

Methodology metrics

published · html + json
Quarterly quality metrics and current measurement limits.
→

Citation monitoring

active · internal admin + public policy
Tracks API/MCP reads, crawler hits, citations and partner attribution compliance.
→

Bulk signed snapshots

queued · planned
Stable aggregate files with checksums for high-volume platform ingestion.
→

Freshness and coverage

StreetProof is still pre-launch. The ledger and API surfaces are live, but absence language must stay tied to coverage. A missing record is not proof a business is fake unless the city has high coverage confidence.

License and citation

Aggregate city statistics, rankings, and study stats are CC BY 4.0 with attribution. Entity facts should cite the Presence Record and the payload's data_as_of. Raw footage, private scout data, unblurred images, raw evidence URLs, and private request payloads are not public machine surfaces.

StreetProof Presence Record, {record_url}, as of {data_as_of}

Current consumption

The usage meter is already active, so StreetProof can see API/MCP reads, known crawler hits, and partner-key usage without logging scout tokens, magic links, raw evidence URLs, request bodies, or private payloads.

  • REST reads in the last 7 days: 173
  • MCP reads in the last 7 days: 8
  • Known crawler hits in the last 7 days: 81
  • Latest machine read: 2026-07-09T13:50:58.646Z

Machine-readable status

The same readiness report is available as JSON for agents and platform crawlers. It includes surface URLs, license rules, freshness, usage visibility, coverage semantics, and limitations.

curl https://streetproof.com/api/v1/search-ai-readiness

Known limits

  • StreetProof is an observation ledger, not a government registry.
  • "Not observed" is only meaningful where coverage_confidence.level is high.
  • Pre-launch data can include synthetic demonstration rows, always marked is_synthetic=true.
  • Closure, rebrand and vacancy alerts stay unpublished until reviewed lifecycle transitions exist.
  • OCR precision and recall remain not_yet_reportable until labeled holdout samples exist.
  • Raw footage, faces, plates, private scout data and raw evidence URLs are not public machine surfaces.