Hlido

Hlido s.r.o., based in Prague, Czech Republic, provides satellite‑derived Earth‑observation data and AI‑driven automation solutions for infrastructure, insurance, banking and other businesses. The company offers ground‑movement screening, landslide risk analysis, and custom AI services, operating across the EU and internationally with a focus on independent AI review and partner‑delivered projects.

Hlido publishes 4 API contracts indexed on the APIs.io network, including Directory API, Incidents API, Ops API, and 1 more. Tagged areas include Satellite, Artificial Intelligence, Earth Observation, Czech, and Startups.

The Hlido catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Hlido’s developer surface includes CLI, changelog, sandbox, documentation, engineering blog, authentication, getting-started guide, and 22 more developer resources.

48.2/100 developing Agent 41/100 agent ready Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →
1 published contract 1 MCP Servers
SatelliteArtificial IntelligenceEarth ObservationCzechStartups

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) 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. Kin Score badge preview for Hlido It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/hlido-eu/"><img src="https://apis.io/badge/hlido-eu/card.svg" alt="Hlido 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):
5 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
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.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
Ask about:
Hlido Eu · a person reads this and replies by email.
or email info@apis.io
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/hlido-eu/apis.yml: open an issue on github.com/api-evangelist/hlido-eu 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 →

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (conformant)
measured — observed by APIs.io (documented)
measured — observed by APIs.io (published)

APIs 4

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

Hlido Directory API

Read-only access to the canonical review corpus.

Hlido Incidents API

Public registry of agent failures (Wave 4 PR #44).

Hlido Ops API

Health, quota, and aggregate stats.

Hlido Recommendations API

Constraint-driven shortlist of reviewed agents.

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Hlido MCP Server

Remote MCP server at hlido.eu.

MCP SERVER

Semantic Vocabularies 1

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

Hlido Eu Context

15 classes · 44 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Hlido API Rules

49 rules · 46 error-severity 2 warn-severity 1 info-severity

SPECTRAL

JSON Schema 6

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

AgentDetail

10 properties

JSON SCHEMA

IncidentSubmitRequest

8 properties

JSON SCHEMA

RecommendRequest

3 properties

JSON SCHEMA

RecommendResponse

5 properties

JSON SCHEMA

StatsPublicResponse

5 properties

JSON SCHEMA

UsageResponse

6 properties

JSON SCHEMA

Security Posture 2

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

Hlido Authentication

http · 1 scheme

SECURITY

Hlido Domain Security

TLSv1.3 · DMARC

SECURITY

Agentic Access (API Evangelist recommendations) 1

Recommended x-agentic-access execution contracts for AI agents.

Hlido Agentic Access

11 operations · 2 acting

11 operations · 2 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 3

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: hlido-eu
name: Hlido
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-13'
  method: derived
image: https://hlido.eu/assets/space/country.jpg
description: Hlido s.r.o., based in Prague, Czech Republic, provides satellite‑derived Earth‑observation data and AI‑driven
  automation solutions for infrastructure, insurance, banking and other businesses. The company offers ground‑movement screening,
  landslide risk analysis, and custom AI services, operating across the EU and internationally with a focus on independent
  AI review and partner‑delivered projects.
url: https://artifacts.apis.io/hlido-eu/apis.yml
x-type: company
x-source: harvest:mcp-registry
x-tier: profiled
x-tier-reason: enrichment pass 2026-11-11 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-11-11'
modified: '2026-11-11'
tags:
- Satellite
- Artificial Intelligence
- Earth Observation
- Czech
- Startups
tags_raw:
- Satellite
- AI
- Earth-Observation
- Czech
- Startup
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: AgenticAccess
  url: agentic-access/hlido-eu-agentic-access.yml
- type: Spectral
  url: rules/hlido-eu-rules.yml
- type: JSONLD
  url: json-ld/hlido-eu-context.jsonld
- type: Vocabulary
  url: vocabulary/hlido-eu-vocabulary.yml
- type: DataModel
  url: data-model/hlido-eu-data-model.yml
- type: CLI
  url: cli/hlido-eu-cli.yml
- type: ChangeLog
  url: changelog/hlido-eu-changelog.yml
- type: ErrorCatalog
  url: errors/hlido-eu-problem-types.yml
- type: Conformance
  url: conformance/hlido-eu-conformance.yml
- type: LLMsTxt
  url: llms/hlido-eu-llms.txt
- type: AgentCard
  url: a2a/hlido-eu-a2a.yml
- type: MCPServer
  url: mcp/hlido-eu-mcp.yml
- type: WellKnown
  url: well-known/hlido-eu-well-known.yml
- type: Hosts
  url: hosts/hlido-eu-hosts.yml
- type: Vendors
  url: vendors/hlido-eu-vendors.yml
- type: TrustCenter
  url: https://hlido.eu/trust/
- type: Sandbox
  url: https://hlido.eu/mcp-docs/playground/
- type: Login
  url: https://hlido.eu/login/
- type: Documentation
  url: https://hlido.eu/docs/
- type: DeveloperPortal
  url: https://hlido.eu/developers/
- type: ChangeLog
  url: https://hlido.eu/changelog/
- type: Blog
  url: https://hlido.eu/blog/art50-marking-gap/
- type: Authentication
  url: authentication/hlido-eu-authentication.yml
- type: DomainSecurity
  url: security/hlido-eu-domain-security.yml
- type: Website
  url: https://hlido.eu/
- type: GettingStarted
  url: https://hlido.eu/about/
- type: Support
  url: https://hlido.eu/contact/
- type: TermsOfService
  url: https://hlido.eu/legal/terms.html
- type: PrivacyPolicy
  url: https://hlido.eu/legal/privacy.html
apis:
- aid: hlido-eu:hlido-eu-directory-api
  name: Hlido Directory API
  description: Read-only access to the canonical review corpus.
  humanURL: https://hlido.eu/developers/
  baseURL: https://hlido.eu/v1
  tags:
  - Directory
  tags_raw:
  - directory
  properties:
  - type: OpenAPI
    url: openapi/hlido-eu-directory-api-openapi.yml
  - type: JSONSchema
    url: json-schema/hlido-eu-recommend-request-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-incident-submit-request-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-agent-detail-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-stats-public-response-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-usage-response-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-recommend-response-schema.json
- aid: hlido-eu:hlido-eu-incidents-api
  name: Hlido Incidents API
  description: 'Public registry of agent failures (Wave 4 PR #44).'
  humanURL: https://hlido.eu/developers/
  baseURL: https://hlido.eu/v1
  tags:
  - Incidents
  tags_raw:
  - incidents
  properties:
  - type: OpenAPI
    url: openapi/hlido-eu-incidents-api-openapi.yml
  - type: JSONSchema
    url: json-schema/hlido-eu-recommend-request-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-incident-submit-request-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-agent-detail-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-stats-public-response-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-usage-response-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-recommend-response-schema.json
- aid: hlido-eu:hlido-eu-ops-api
  name: Hlido Ops API
  description: Health, quota, and aggregate stats.
  humanURL: https://hlido.eu/developers/
  baseURL: https://hlido.eu/v1
  tags:
  - ops
  properties:
  - type: OpenAPI
    url: openapi/hlido-eu-ops-api-openapi.yml
  - type: JSONSchema
    url: json-schema/hlido-eu-recommend-request-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-incident-submit-request-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-agent-detail-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-stats-public-response-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-usage-response-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-recommend-response-schema.json
- aid: hlido-eu:hlido-eu-recommendations-api
  name: Hlido Recommendations API
  description: Constraint-driven shortlist of reviewed agents.
  humanURL: https://hlido.eu/developers/
  baseURL: https://hlido.eu/v1
  tags:
  - Recommendations
  tags_raw:
  - recommendations
  properties:
  - type: OpenAPI
    url: openapi/hlido-eu-recommendations-api-openapi.yml
  - type: JSONSchema
    url: json-schema/hlido-eu-recommend-request-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-incident-submit-request-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-agent-detail-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-stats-public-response-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-usage-response-schema.json
  - type: JSONSchema
    url: json-schema/hlido-eu-recommend-response-schema.json
x-enrichment:
  date: '2026-11-11'
  status: enriched
  artifacts_added: 28
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

Hlido API — frequently asked questions

Does Hlido have an API?

Yes. APIs.io lists 4 APIs from Hlido, including Hlido Directory API, Hlido Incidents API and Hlido Ops API, and 1 more.

Is there an OpenAPI specification for the Hlido API?

Yes. APIs.io indexes 4 OpenAPI specifications for Hlido, each linked for download from this page.

How do I authenticate with the Hlido API?

Hlido uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Hlido Authentication.

Does Hlido have an MCP server?

Yes. APIs.io lists 1 MCP server for Hlido: Remote MCP server at hlido.eu.

Is the Hlido API ready for AI agents?

Hlido has a Kin Score of 48.2 out of 100 (developing) and an Agent Readiness score of 41.0 (agent-ready), scored by API Evangelist on 2026-11-13.

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/hlido-eu"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/hlido-eu/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/hlido-eu/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

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