StreetProof Physical Brand Index™ (PBI)

Add a real-world citation layer to your entity graph

Evidence-firstPrivacy-scrubbedMachine-readable

Search and SEO platforms spend enormous effort crawling, evaluating, and filtering backlinks, listings, reviews, and websites. Those signals matter, but parts of the online reputation economy can be purchased, exchanged, copied, or manufactured. Most entity graphs still have no independent physical anchor.

StreetProof adds that missing layer. Each accepted sighting becomes a physical citation: a business-independent, privacy-safe record with provenance, time, location scope, verification state, and a place in an append-only ledger. It is the real-world counterpart to an online brand mention, not an HTML link or a ranking promise.

Query the StreetProof PBI through public REST and MCP interfaces. Use the evidence as a harder-to-manipulate input for entity resolution, local-search quality, AI answers, underwriting, due diligence, and market intelligence. StreetProof reports what was observed and leaves the decision logic to the consuming system.

Run a live queryCall REST or MCP against a current public record.Open →OpenAPI 3.1Inspect the executable public contract.Open →Sample JSONDownload the validated versioned fixtures.Open →Connect MCPCopy the endpoint and client configuration.Open →

Brand visibility without false addresses

Every observation exposes presence_kind: location_presence, mobile_presence, or brand_mention. A Coca-Cola sign inside a venue is useful evidence of Coca-Cola visibility at that venue. It is not evidence of a Coca-Cola office there. Consumers can count the citation without making the wrong entity-location claim.

Integration surfaces

REST API

Entity profiles, presence scores with per-component breakdowns, paginated observation ledgers, city and industry rankings, and Observation and StreetPulse change events. Reviewed opening, closure, rebrand, and vacancy transitions are planned. Public, low-volume read access stays free for AI, search, research, and people.

MCP server

Native tools for agent frameworks: get_physical_presence, compare_presence, check_physical_evidence, city_index. Each returns evidence summaries with a ready-made citation string so agents quote correctly. MCP server — available now in public beta.

Future verification requests

Stage Two may let platforms commission fresh ground-truth checks on a business or address. That service is not accepting requests during the points-only Pioneer stage.

Data guarantees

A verification layer that asks to be trusted has failed before it starts. Ours is built to be checked instead.

Append-only, hash-chained ledger

Observations are never updated or deleted — legal removals flip a redaction flag, they don't rewrite history. Each row carries a hash chained to the previous one. Signed checkpoints are submitted for external timestamp verification; their real-time status and the public-beta limitation are published on the transparency page.

Corroboration before publication

Scout submissions from low-trust accounts sit in a provisional state and never enter public counts until independently corroborated evidence — a fleet camera, telematics feed, or high-trust scout — observes the same asset. Fleet-camera observations anchor the whole trust economy.

Uncertainty is in the payload

Every response carries coverage_confidence, evidence_claim_boundary, data_as_of, and methodology_url. Coverage describes the dataset. It never turns “not observed” into proof of absence.

Provenance on the evidence

In-app-only capture with device attestation, GPS at shutter time, and perceptual-hash dedupe against every image ever submitted. Faces and licence plates are blurred before any image becomes retained evidence, enters the recognition archive, or appears publicly. Unsanitized frames are processed transiently in the private privacy pipeline and are not retained as evidence. Methodology and error rates are published, not implied.

Access and launch state

Public read access — entity lookups, scores, rankings, and ledger views — is free and stays free. Ingestion into AI systems is the point of the index, so StreetProof will not paywall basic citation retrieval. Paid platform plans can cover higher quotas, signed bulk datasets, service levels, webhooks, usage reporting, support, and negotiated licences. Payment never changes the underlying evidence or ranking.

And to be straight about launch state: StreetProof is in public beta. The ledger, REST API, machine-readable pages, and Scout collection app are live; coverage is still low, and StreetProof does not make absence claims at any coverage tier. We would rather show a small honest record than pad an empty one. For integration access, write to [email protected].

Integrating, in practice

The intended flow is short. Your agent or ranking system hits /search with a name and city, gets back candidate entities with public IDs. A follow-up to /entity/{id} or /presence-score/{id} returns the score, its components, physical-citation counts and types, first/last-seen dates, and the coverage confidence for that city. Positive citations document when and where a brand or asset was observed. No matching citation means only that StreetProof has no accepted match; do not infer absence, closure, inactivity, legitimacy, or quality. A future verification-request service may collect fresh evidence under separately published Stage Two terms. MCP provides the current record through tool calls, so an AI agent can run the check mid-conversation without custom glue. Full request and response shapes are in the API docs.

Partner portal

API-key partners can inspect their own integration state without waiting on a support thread: quota usage, recent request logs, active key prefixes, webhook endpoints, sample code, OpenAPI and MCP links, support notes, and required attribution text are available from GET /api/v1/partner/portal. StreetPulse webhook endpoints are configured through POST /api/v1/partner/webhooks and get a signing secret shown once at setup.

Citation monitoring

StreetProof monitors API and MCP usage, known crawler hits, backlinks, press references, and partner attribution compliance. The point is not to hide the data behind a wall. The point is to know which records, studies, and machine surfaces are being consumed, and whether partners are giving the required attribution when they reuse aggregate stats.