{
  "id": "p_biZT2Cs4ObafGVuR",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_biZT2Cs4ObafGVuR",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apisio"
  },
  "body": "You are building a small app that needs weather data, and you have an afternoon to choose a provider. You want a first successful call before you commit to anything. You do not want a sales call or a credit card form, and you do not want to find out on day three that the units change between cities.\n\nSo you open a post from Foreca, the Finnish weather company, titled \"API Documentation You'll Love: Test Our Sandbox for Free.\" It starts with a complaint you already share: \"Integrating a new weather API shouldn't feel like deciphering an ancient manuscript.\"\n\nThe answer comes as three commitments. The first is \"Predictable Data Models,\" with JSON outputs \"uniform across all global locations,\" so that \"you will never need to write custom exception handlers for missing fields or shifting units.\" The second is \"Plug-and-Play Endpoints.\" The third is a \"Real-Time Testing Environment\" built into the documentation itself.\n\nYou notice the post gives no figures. What it gives you is the onboarding, and that is where it is strongest. There is a 30-day free trial with no credit card and no sales call. You get an API key in the portal \"in under two minutes.\" The endpoints are listed in the developer documentation. A Test Request button runs the call live and generates cURL, Python and Node.js snippets. All requests go to one host. Support comes from engineers \"alongside our core API codebase,\" not \"an automated ticketing bot.\" When you are ready for production, it is a self-serve subscription by card.\n\nFor a weather API, you think, that is the right shape. There is no gate between curiosity and a first working call. The APIs.io post says as much.\n\nThen the post turns, and the turn is about the catalog's own record. APIs.io looked at Foreca, and there is almost nothing there to hold the promise up. The provider page carries a single page, Foreca, and every one of the nineteen Agent Readiness dimensions is unlit.\n\nTwo of those matter to you directly. Spec presence is unlit, which means the catalog has found no machine-readable description of the endpoints the post describes. The rate limit signal is unlit too, even though the post invites readers to ask about \"optimal polling frequencies.\"\n\nThe scores follow. The Kin Score is 5.6, in the minimal band, with discoverability at 46.4 and developer ergonomics at 11.9. Every other facet is at zero. The Agent Readiness score is 0.0, which the catalog labels human-only.\n\nYou might read that and decide the catalog is being harsh, and the post anticipates that. It explains the gap by what the rubric reads. \"Predictable data models\" and \"uniform\" outputs are claims about a schema. The way to prove a schema claim to a machine is to publish the schema. The post also notes that an interactive console that generates snippets is usually built on an OpenAPI document. Such a document may already exist behind Foreca's developer portal without being linked from anywhere a probe would look. So the post does not say Foreca has no contract. It says the catalog has not found one.\n\nThat changes how you use the post. The trial is real, by Foreca's own account, and you can test the sandbox for free this afternoon. But the uniform-fields promise is a vendor claim you cannot yet check from outside, because there is no published schema to check it against. If you are writing an agent, or generating a client from a spec, the thing you would want first is not in the catalog.\n\nWhat you take away is a habit. When a provider says its documentation is something you will love, ask where the contract is. Foreca has built the experience a developer would love. The contract that would let an agent love it too has not been found.\n\nRead the original: https://apis.io/2026/10/22/foreca-says-api-documentation-youll-love-and-publishes-no-contract/",
  "title": "You read the pitch, then you look for the contract: Foreca's API documentation",
  "topics": [
    "api-documentation",
    "weather-apis",
    "openapi",
    "agent-readiness"
  ],
  "published_at": "2026-10-22T13:41:12.222Z",
  "expires_at": null,
  "policy_version": "2026.09.25-1"
}