Offer a parametric weather guarantee at checkout for a hotel, attraction, or outdoor-event booking using the Sensible Weather API
domain: sensible.readme.io · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain API keys from Sensible Weather and call their authorization API (createAccessToken) to exchange the keys for a bearer access token before calling any other endpoint.
Cache the returned token using its `expires_in` value (default 24-hour expiration) and only request a new one when the cached token has expired or is about to expire.
Use the Quote Integration flow to generate a Weather Guarantee quote for the specific booking (dates, location, product type) at checkout.
Create the guarantee once the customer accepts the add-on, or use the Included Weather Guarantee flow if the guarantee ships bundled rather than as an add-on.
Handle guarantee lifecycle changes — accept, decline, cancel, or update a booking's guarantee — through the corresponding endpoints described in the "Altering a Weather Guarantee" docs.
Confirm up front whether Sensible Weather or your platform is the merchant of record, since payment handling and tax-assessment steps differ between the two documented scenarios.
Known gotchas
API calls return `401 Unauthorized` once the bearer token expires — a fresh token must be requested; the stale token cannot be retried.
The correct endpoints depend on your program's configuration (add-on vs. included guarantee, Merchant-of-Record scenario 1 vs. 2) — confirm which pattern applies with Sensible Weather before building against a specific flow.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?