LHMT (Lithuania)

LHMT (Lithuania) operates the national meteorological service, providing weather forecasts, climate data, and a public API (api.meteo.lt) that offers access to current observations, forecasts, and historical weather information for Lithuania. The service supports developers with JSON endpoints and documentation, enabling integration of meteorological data into applications and research.

LHMT (Lithuania) is listed with 1 API on the APIs.io network. Tagged areas include Company, Weather, Meteorology, API, and Lithuania.

The LHMT (Lithuania) catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

🌐 Visit website 📡 Profile data on GitHub

13.9/100 emerging Agent 13/100 agent aware Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

1 API

Company Weather MeteorologyAPILithuania Government

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 13.9/100 · emerging

Contract Quality 5.0 / 21

Developer Ergonomics 0.0 / 17

Access Clarity 0.0 / 17

Operational Transparency 0.0 / 11

Contract Governance 2.2 / 10

Discoverability 4.9 / 9

Regulatory Posture 1.6 / 15

Agent readiness — 13/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 0 / 3

Regulatory Posture applies to this provider. Its tags matched the Government & Public Sector regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/lhmt/"><img src="https://apis.io/badge/lhmt/card.svg" alt="LHMT (Lithuania) on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes

13 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Developer Ergonomics scores 0.0 — up to +20.0 composite points
Access Clarity scores 0.0 — up to +20.0 composite points
Contract Quality scores 23.5 — up to +19.1 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/lhmt/apis.yml: open an issue on github.com/api-evangelist/lhmt to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

LHMT (Lithuania) API

LHMT (Lithuania) API as documented publicly: 12 operations. Contract generated from the documentation by API Evangelist (2026-10-28); not the provider's own document.

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Lhmt Context

12 classes · 34 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

LHMT (Lithuania) API Rules

9 rules · 7 errors 1 warnings 1 info

SPECTRAL

JSON Schema 6

Standalone JSON Schema definitions for this provider's data models.

GetHydroStationsStationcodeObservationsObservationtypeRespon

8 properties

JSON SCHEMA

GetHydroStationsStationcodeObservationsResponse

8 properties

JSON SCHEMA

GetPlacesPlacecodeForecastsForecasttypeResponse

21 properties

JSON SCHEMA

GetPlacesPlacecodeForecastsResponse

10 properties

JSON SCHEMA

GetStationsStationcodeObservationsDateResponse

17 properties

JSON SCHEMA

GetStationsStationcodeObservationsResponse

7 properties

JSON SCHEMA

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Lhmt Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

DataModel

Conformance

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Company 1

The organization behind the API

Website

Website

Other 1

Properties that don't map to a standard resource type

Hosts

Hosts

Source (apis.yml)

aid: lhmt
name: LHMT (Lithuania)
image: https://www.meteo.lt/app/themes/slyva/images/social-default.png
description: LHMT (Lithuania) operates the national meteorological service, providing weather forecasts, climate data, and
  a public API (api.meteo.lt) that offers access to current observations, forecasts, and historical weather information for
  Lithuania. The service supports developers with JSON endpoints and documentation, enabling integration of meteorological
  data into applications and research.
url: https://artifacts.apis.io/lhmt/apis.yml
website: https://www.meteo.lt
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-28 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-28'
modified: '2026-10-28'
tags:
- Company
- Weather
- Meteorology
- API
- Lithuania
- Government
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Spectral
  url: rules/lhmt-rules.yml
- type: JSONLD
  url: json-ld/lhmt-context.jsonld
- type: Vocabulary
  url: vocabulary/lhmt-vocabulary.yml
- type: DataModel
  url: data-model/lhmt-data-model.yml
- type: Conformance
  url: conformance/lhmt-conformance.yml
- type: Hosts
  url: hosts/lhmt-hosts.yml
- type: DomainSecurity
  url: security/lhmt-domain-security.yml
- type: Website
  url: https://meteo.lt/
apis:
- aid: lhmt:lhmt-api
  name: LHMT (Lithuania) API
  description: 'LHMT (Lithuania) API as documented publicly: 12 operations. Contract generated from the documentation by API
    Evangelist (2026-10-28); not the provider''s own document.'
  humanURL: https://api.meteo.lt
  properties:
  - type: OpenAPI
    url: openapi/_ae-authored/lhmt-openapi-generated.yml
    x-provenance: generated
  - type: JSONSchema
    url: json-schema/lhmt-get-places-placecode-forecasts-forecasttype-response-schema.json
  - type: JSONSchema
    url: json-schema/lhmt-get-stations-stationcode-observations-date-response-schema.json
  - type: JSONSchema
    url: json-schema/lhmt-get-places-placecode-forecasts-response-schema.json
  - type: JSONSchema
    url: json-schema/lhmt-get-hydro-stations-stationcode-observations-observationtype-respon-schema.json
  - type: JSONSchema
    url: json-schema/lhmt-get-stations-stationcode-observations-response-schema.json
  - type: JSONSchema
    url: json-schema/lhmt-get-hydro-stations-stationcode-observations-response-schema.json
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  detail: All attempts to fetch OpenAPI specifications from the API host returned 404, indicating no machine‑readable contract
    is published.
  evidence:
  - url: https://api.meteo.lt/openapi.json
    status: 404
  - url: https://api.meteo.lt/openapi.yaml
    status: 404
  - url: https://api.meteo.lt/swagger.json
    status: 404
  - url: https://api.meteo.lt/v1/openapi.json
    status: 404
  checked: '2026-10-28'
x-submission-probe: 200, 2026-10-26
x-enrichment:
  date: '2026-10-28'
  status: enriched
  artifacts_added: 19
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

LHMT (Lithuania) API — frequently asked questions

Does LHMT (Lithuania) have an API?

Yes. APIs.io lists 1 API from LHMT (Lithuania), including LHMT (Lithuania) API.

Is there an OpenAPI specification for the LHMT (Lithuania) API?

Yes. APIs.io indexes 1 OpenAPI specification for LHMT (Lithuania), each linked for download from this page.

Is the LHMT (Lithuania) API ready for AI agents?

LHMT (Lithuania) has a Kin Score of 13.9 out of 100 (emerging) and an Agent Readiness score of 12.7 (agent-aware), scored by API Evangelist on 2026-10-31.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/lhmt"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/lhmt/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/lhmt/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.