Skip to main content

Public data freshness manifest

Tell crawlers when public-source claims are fresh enough to publish.

TenVur turns source-radar feeds into freshness policies, server-cache expectations, stale-data handling, and partner copy guardrails. The manifest keeps live probes, keys, private pulls, and cash commissions out of the public surface.

Freshness contract

GET /api/agents/public-data-freshness-manifest
  ?domain=weather
  &credentialless=1
  &format=markdown

schemaVersion: tenvur.public-data-freshness-manifest.v1
sources: 2
nearRealTime: 1
serverOnly: 1
sourceClock: provider_cadence_only
probe: not_run_public_manifest

Sources

2

Near real-time

1

Server-only

1

Claim ready

1

Source clock

provider_cadence_only

SLA without overclaiming

Freshness policy travels with every source-backed placement.

This manifest publishes TenVur's source freshness, cache, and stale-data handling policy for official public-data feeds. It does not perform live uptime probes, expose credentials, store private pulls, certify current upstream availability, approve partner claims, or activate cash commissions.

Serve the manifest with public, max-age=60, s-maxage=300. Cache actual source pulls by each policy's sourceCacheWindow, not by this manifest TTL.

If a source is stale, keep evergreen source labels but pause current-value, urgency, ranking, safety, eligibility, or revenue claims until refreshed.

release bound / low

NASA POWER API

NASA Langley Research Center POWER Project

86

Freshness

86400 seconds to provider release cycle

Stale after: Climatology and temporal dataset dependent

Stale action

Use as historical context with release-window labels and avoid customer-specific conclusions.

Publish source cards and partner briefs with release-window labels, claim boundaries, and account-credit disclosure.

near real time / high

National Weather Service API

National Weather Service

74

Freshness

300 to 1800 seconds

Stale after: 30 minutes for current claims; 24 hours for historical context

Stale action

Pause current-value, urgency, safety, and scheduling claims until a fresh server pull succeeds.

Attach a fresh server-side pull before publishing current claims, then route the source through source cards, distribution feed, and CRM handoff.

Failure posture

Stale public data degrades to context, not claims.

Do not downgrade or approve partner claims automatically from this public manifest.

Do not publish live-status badges from this manifest without a separate probe result.

Do not use freshness policy as payout, commission, Stripe, tax, or partner-network approval.

Guardrails

Do not claim this manifest proves an upstream source is currently available.

Do not expose private pulls, API keys, required headers, customer identifiers, or raw lead data through freshness endpoints.

Do not turn public-data recency into guaranteed demand, safety, compliance, eligibility, revenue, ranking, or property-level claims.

Do not treat source freshness as live cash commission approval, payout eligibility, or billing configuration.