Developers
Beatnik Hiway An evidence-led field guide to literary and counterculture places.
San Francisco, selectively documented Dataset sf-reviewed-2026-09-28.2 Reviewed data Reviewed through Sep 28, 2026

Developer access

One publication layer, six public tools

REST, Remote MCP, HTML and export formats share the same domain services, evidence rules and dataset version.

Public tool registry

GET /api/v1/entities · 1 unit

search_cultural_entities

Find published cultural entities by name, alias, type, city or theme.

Limit: Use it to discover records in this dataset; do not use an empty result as proof that an entity does not exist.

GET /api/v1/entities/{entity_id} · 1 unit

get_entity_evidence

Retrieve reviewed claims, direct relationships and source locators for one entity.

Limit: It does not supply quotations or relationships absent from the published record.

POST /api/v1/visitability/check · 1 unit per distinct place

check_place_visitability

Evaluate scheduled access for one or more places at a specified offset-aware time.

Limit: The result is evidence-based planning information, not a live guarantee.

POST /api/v1/walks/plan · 10 units

build_cultural_walk

Build a time- and evidence-constrained cultural walk from reviewed places and route segments.

Limit: Missing segments remain unknown; distance, duration and geometry are never inferred.

POST /api/v1/research-packs/build · 20 units

build_research_pack

Create a deterministic JSON, Markdown or BibTeX pack from published claims.

Limit: Disputes, unknowns and rights limits remain in the export; it is not a generated narrative.

GET /api/v1/coverage · 1 unit

get_dataset_coverage

Inspect the actual scope, gaps and freshness distribution of the current dataset release.

Limit: Counts are computed from published data and never replaced by editorial target numbers.

Discovery endpoints

Start with coverage

Inspect dataset coverage, then search for stable entity IDs. Use evidence lookup before relying on a relationship, and check visitability before adding an indoor stop to a walk.

REST and MCP

The REST API uses a consistent response envelope. Remote MCP exposes the same six operations through Streamable HTTP. A domain result marked partial or unknown is a valid result, not a protocol failure.

OpenAPI describes REST operations. MCP tool discovery describes the enabled tool registry. Disabled tools must not appear in either surface.

Authentication and cost units

Small public reads can be anonymous. API keys extend configured quotas but are not OAuth and must never be placed in URLs, browser storage or public logs.

Cost units meter service use; they are not payments. The first release performs read-only computation and does not purchase, book, send or publish anything externally.

Stable formats

Core entities and evidence are available as HTML, Markdown and JSON. Every representation preserves sources, review dates, data version, unknowns and rights limits.