ScheduleObservation v1 · design access

Answer schedule questions with fields you can audit.

A normalized, read-only schedule observation API for comparing offered starts, posted prices, booking horizons, and public inventory states over time. Every released row is bound to observation time, a versioned derivation, and opaque provenance.

Request API access Inspect the contract

This product is not live. The response at right is synthetic documentation only.

Synthetic responseschema v1

{
  "schemaVersion": "sll.schedule-observation.v1",
  "recordId": "synthetic-record-0001",
  "observation": { "observedAt": "2026-09-05T14:30:00Z", "publicBookingHorizonDays": 21 },
  "slot": { "startsAtUtc": "2026-09-12T18:00:00Z", "observationToStartMinutes": 10170, "lastObservedAvailableLeadTimeMinutes": null },
  "price": { "amount": "24.00", "currency": "USD" },
  "publicInventory": { "state": "available" },
  "lineage": { "lineageId": "synthetic-lineage-0001" }
}

Not collected dataOpen full synthetic JSON

GET

/v1/schedule-observations?source_key={source_key}&service_date={YYYY-MM-DD}

Planned endpoint shape only. Access is closed until source, field, proof, rights, product-cache, entitlement, and payment gates pass.

Last updatedSynthetic example: 2026-09-05

Schemasll.schedule-observation.v1

Read pathProof-bound cache only

Response grainOne observed offered start

Fields preserve the difference between observed and derived.

Observed fields describe a public surface at a time. Derived fields are explicit, deterministic, versioned transformations. Missing evidence stays null rather than becoming zero, unavailable, or a guess.

Field	Type	Classification	Meaning and boundary
`observation.observedAt`	timestamp	Observed	When Fron Research captured the public surface. It is not the time a customer made a purchase.
`observation.publicBookingHorizonDays`	integer \| null	Derived	Latest completely enumerated offered service date relative to the observation. Null when complete enumeration is not proven.
`slot.startsAtUtc`	timestamp	Observed or normalized time	The offered service start, with local-source time normalized to UTC where a reliable mapping is available.
`slot.observationToStartMinutes`	integer \| null	Derived	Time from observation to the offered start. It is a public booking-horizon measure, not actual customer purchase lead time.
`slot.lastObservedAvailableLeadTimeMinutes`	integer \| null	Derived	Lead time at the last comparable observation where an available state was observed. It does not show who booked, when they booked, or why a state changed.
`price.amount`	decimal string \| null	Observed	A displayed public price with currency and basis. It is not a payment, completed sale, or realized revenue.
`publicInventory.state`	enum \| null	Observed or approved mapping	A provider-returned public state or a documented mapping. It never means demand, capacity, occupancy, utilization, bookings, or revenue.
`lineage.lineageId`	opaque string	Provenance	Non-public pointer to retained source evidence and the pinned normalizer and derivation versions.

Null is a documented result.

The API does not turn unknown facts into tidy numbers. Consumers receive a nullable field plus a reason where the distinction matters.

Null semantics

null means the source did not expose a value, the observation was incomplete, the mapping was not approved, or a comparable prior observation was unavailable.

It does not mean zero, sold out, not offered, no price, no change, or a failed collection.

Provenance and delivery

Each eligible record carries provider-native identity, observation time, source-key scope, lineage ID, normalizer version, and derivation version. API reads never trigger a provider request.

Planned delivery formats are JSON, CSV, Parquet, scheduled files, and webhooks. Raw provider responses are not a delivery format.

Versioning makes change reviewable.

Every response declares its schema version. Additive, backward-compatible fields are introduced within the v1 line. A change to row grain, field meaning, enum semantics, or null semantics requires a new major version and a migration note.

ScheduleObservation v1

Defines normalized schedule, price, public-inventory, change, and lineage fields. The contract describes future cleared outputs. It does not make any source eligible for publication.

Free coverage metadata

The free metadata page documents public provider-surface coverage and evidence boundaries. It is a separate static technical sample, not a normalized ScheduleObservation response and not paid API access.

Pricing hypotheses, not active offers.

These are inactive product tests. No checkout, payment, entitlement, or access is available from this page.

Monitor hypothesis

$149 / month

Potential access for a small supported-location cohort, cached observations, and scheduled delivery.

Inactive pending gates

Portfolio hypothesis

$499 / month

Potential access for a larger cleared cohort, longer history, cached API reads, and webhook delivery.

Inactive pending gates

Data hypothesis

$999 / month

Potential access for a rights-cleared cohort, bulk export, and defined cached-read limits.

Inactive pending gates

Release stays closed until the evidence is ready.

Product access fails closed. A request for a source or field that has not cleared the gates below is not fulfilled through this API.

Source and field allowlist. Commercial distribution rights, source terms, customer authorization where required, and field-level publication status are documented.

Proof-bound derivation. The source mapping, null behavior, versioned normalizer, and opaque lineage are reproducible against retained evidence.

Isolated read plane. A released response is served from a cache that cannot call a provider, including on cache miss.

Product controls. Schema compatibility, freshness policy, entitlement, support, seller, payment, privacy, refund, and takedown controls are approved.

Request the first cleared scope.

Tell us the decision, sources or locations, required fields, history, and delivery format. We will respond only when the requested surface can be evaluated against the release gates.

Request access or a scope review

No payment is taken here. Customer requests do not authorize new collection, source publication, or data delivery.