# Super Calendar Landing Index

Structured interpretation of the public Super Calendar landing page for agents and tooling.

This Markdown document is generated from `/agents/landing.index.json`. The JSON file remains canonical.

## Authority

- **Canonical Html:** `/`
- **Machine Index:** `/agents/index.json`
- **Http Contract:** `/api/docs/json`
- **Io Contract:** `/io/ioapi.json`
- **Language Contract:** `/common/i18n/manifest.json`

## Production Surfaces

| Surface | Path | Purpose |
| --- | --- | --- |
| Home | `/` | Primary product explanation and feed entry point. |
| Importing | `/importing/` | Human import instructions for calendar clients. |
| Io | `/io/` | Low-level I/O contract documentation. |
| Agents | `/agents/` | Agent-facing discovery and behavior contracts. |

## Sections

- **Hero** (primary-proposition): Transform real-world data into calendar feeds.
- **Feeds** (feed-catalog): Known public feed domains include weather, exchange, moon, holidays, seasons, religion, events, custom, trivia, sports, crypto, and earnings.
- **How-It-Works** (workflow): Choose data, generate a URL, subscribe in a calendar client.
- **Developers** (developer-entry): Use OpenAPI for HTTP contracts and I/O docs for low-level node access.

## Agent Rules

- Do not infer private routes from UI-only controls.
- Use /api/docs/json before constructing HTTP URLs.
- Use /io/ioapi.json before addressing I/O nodes.
- Use /common/i18n/manifest.json for language availability.
- Treat private WebCal URLs as credentials.