# Stsezhka: public product and agent guide

> Canonical origin: https://stsezhka.com
>
> Purpose: help riders plan bicycle and outdoor routes while keeping private account and
> activity data outside public agent interfaces.

## Product overview

Stsezhka is a web-based outdoor and bicycle route planner. A rider can build a route from
waypoints, choose a riding profile, inspect distance and elevation, understand likely surface
types, add points of interest, prepare a multi-stop ride plan, and export artifacts for use
away from the browser.

The primary human interface is the map at https://stsezhka.com/. Documentation is published at
https://stsezhka.com/docs/ and is rendered as crawlable HTML.

## Public workflows

### Point-to-point route planning

1. Open https://stsezhka.com/.
2. Search for a place or position the map.
3. Add at least two waypoints.
4. Select road, gravel, MTB, commute, or direct routing.
5. Review the route geometry, distance, elevation, and surface estimate.
6. Adjust waypoints and re-check the route before riding.

### Loop generation

1. Select a start point.
2. Set a target distance and riding profile.
3. Choose an elevation preference and direction bias.
4. Generate a loop, review it, and adjust the result as needed.

### Ride preparation

Routes can be expanded with points of interest, planned stops, timing estimates, cue sheets,
GPX export, and printable roadbook output. These are planning aids. Trail access, closures,
weather, traffic, construction, and local rules must be verified separately.

## Public documentation

- Rider guide: https://stsezhka.com/docs/user-guide/
- Feature index: https://stsezhka.com/docs/features/
- Use cases: https://stsezhka.com/docs/usecases/
- Agent integration guide: https://stsezhka.com/docs/agents/
- Changelog: https://stsezhka.com/changelog
- Support: https://stsezhka.com/support
- Privacy: https://stsezhka.com/privacy
- Terms: https://stsezhka.com/terms
- Data deletion: https://stsezhka.com/data-deletion

## Discovery protocol

The homepage advertises machine-readable resources through RFC 8288 Link response headers.
The API catalog at https://stsezhka.com/.well-known/api-catalog follows RFC 9727 and points to:

- the OpenAPI document at https://stsezhka.com/openapi.json;
- public service documentation at https://stsezhka.com/docs/agents/;
- the health endpoint at https://stsezhka.com/api/healthz.

The following curated text resources are also available:

- https://stsezhka.com/llms.txt
- https://stsezhka.com/llms-full.txt
- https://stsezhka.com/agents.md

Requests for the homepage with an Accept header containing text/markdown receive a Markdown
representation with Content-Type: text/markdown and Vary: Accept.

## Read-only MCP

Server card: https://stsezhka.com/.well-known/mcp/server-card.json
Endpoint: https://stsezhka.com/mcp
Transport: stateless Streamable HTTP using JSON-RPC 2.0
Protocol version: 2025-06-18
Authentication: none

The MCP endpoint exposes only two static, read-only tools:

- get_stsezhka_guide
- get_stsezhka_feature_guide

It also exposes public guide and discovery resources. It cannot read browser state, cookies,
account records, saved routes, activities, garage data, private shares, or third-party fitness
data. It cannot create, modify, share, export, or delete user content.

## Agent Skill

Discovery index: https://stsezhka.com/.well-known/agent-skills/index.json
Skill: https://stsezhka.com/.well-known/agent-skills/stsezhka-public-guide/SKILL.md
Integrity: sha256:963aecdeba6d5764379889a37eb7fbff3dccc09e1d685b6c8c50899d86da5c8b

The skill directs agents to public documentation and repeats the private-data boundary. Its
artifact is versioned through a SHA-256 digest.

## Content usage signal

Public, crawlable content declares:

- ai-train=no
- search=yes
- ai-input=yes

This permits public search and agent use while declining model-training use. Private and
authenticated routes are excluded from robots.txt and are not part of the public agent layer.

## Privacy and Strava boundary

Agents must not request, infer, expose, transform, or transmit:

- account identifiers or authentication material;
- saved route or trip records;
- activity histories or precise private locations;
- garage and maintenance records;
- private share tokens or private shared content;
- Strava data or anything derived from Strava data.

Stsezhka does not publish OAuth, OIDC, Protected Resource Metadata, or auth.md registration for
agents because authenticated product APIs are not offered as agent APIs. A discovery score must
not be improved by advertising an authorization flow that the product does not safely support.

## Operational notes

The public MCP and WebMCP tools return product-authored static content only. Tool outputs do not
include user-generated content and do not execute remote side effects. The MCP server validates
browser Origin headers, is rate-limited, and does not create sessions.