Freie und Hansestadt Hamburg

The Free and Hanseatic City of Hamburg (Freie und Hansestadt Hamburg), the German city-state, publishes the Urban Data Platform Hamburg datasets as open OGC API - Features services at api.hamburg.de: a catalog of 416 dataset APIs (environment, mobility, building plans, heritage, energy, social services) each with its own OpenAPI 3.0.3 definition, conformance declaration (OGC API Common/Features parts 1-3, 6, 8 and CQL2) and anonymous GeoJSON access. Five representative dataset contracts are captured here.

Freie und Hansestadt Hamburg publishes 3 API contracts indexed on the APIs.io network: Access data API, Capabilities API, and Discover data collections API. Tagged areas include Government, Open Data, Geospatial, OGC API Features, and Smart City.

The Freie und Hansestadt Hamburg catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Freie und Hansestadt Hamburg’s developer surface includes authentication, API reference, documentation, and 17 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

35.6/100 thin Agent 20/100 agent aware Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

6 published contracts

Government Open Data Geospatial OGC API Features Smart City GermanyUrban Data Platform

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 35.6/100 · thin

Contract Quality 13.0 / 21

Developer Ergonomics 4.9 / 17

Access Clarity 1.4 / 17

Operational Transparency 1.0 / 11

Contract Governance 2.2 / 10

Discoverability 6.7 / 9

Regulatory Posture 3.1 / 15

Agent readiness — 20/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 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 4 / 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

MCP Tool Quality 6 / 6

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 does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.

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/hamburg-de/"><img src="https://apis.io/badge/hamburg-de/card.svg" alt="Freie und Hansestadt Hamburg 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 Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented) Ask about this →
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented) Ask about this →

7 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 8.5 — up to +18.3 composite points Ask about this →
Developer Ergonomics scores 28.6 — up to +14.3 composite points Ask about this →
Operational Transparency scores 9.5 — up to +11.8 composite points Ask about this →

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 →

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/hamburg-de/apis.yml: open an issue on github.com/api-evangelist/hamburg-de 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 1

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.

OpenAPI

measured — observed by APIs.io (published)

APIs 3

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

Freie und Hansestadt Hamburg Access data API

The Access data API from Freie und Hansestadt Hamburg — 40 operation(s) for access data.

Freie und Hansestadt Hamburg Capabilities API

The Capabilities API from Freie und Hansestadt Hamburg — 3 operation(s) for capabilities.

Freie und Hansestadt Hamburg Discover data collections API

The Discover data collections API from Freie und Hansestadt Hamburg — 81 operation(s) for discover data collections.

Semantic Vocabularies 1

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

Hamburg De Context

48 classes · 24 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.

Freie und Hansestadt Hamburg API Rules

48 rules · 45 error-severity 2 warn-severity 1 info-severity

SPECTRAL

3 properties

JSON SCHEMA

Scroll for all 24

Security Posture 2

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

Freie und Hansestadt Hamburg Authentication

http · 1 scheme

SECURITY

Freie und Hansestadt Hamburg Domain Security

TLSv1.2 · DNSSEC · DMARC

SECURITY

Agentic Access (API Evangelist recommendations) 1

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

Freie und Hansestadt Hamburg Agentic Access

140 operations

140 operations · 0 acting

AGENTIC

Resources

Documentation 2

Reference material describing how the API behaves

APIReference

APIReference

Documentation

Documentation

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

WellKnown

WellKnown

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions

Spectral

JSONLD

Vocabulary

DataModel

ErrorCatalog

Conformance

Scroll for all 7

Access & Security 4

Authentication, authorization, and security posture

SecurityTxt

SecurityTxt

Authentication

DomainSecurity

Commercial 1

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Company 1

The organization behind the API

Website

Website

Other 3

Properties that don't map to a standard resource type

Hosts

Hosts

APIsCatalog

APIsCatalog

Imprint

Imprint

Source (apis.yml)

aid: hamburg-de
name: Freie und Hansestadt Hamburg
description: 'The Free and Hanseatic City of Hamburg (Freie und Hansestadt Hamburg), the German city-state, publishes the
  Urban Data Platform Hamburg datasets as open OGC API - Features services at api.hamburg.de: a catalog of 416 dataset APIs
  (environment, mobility, building plans, heritage, energy, social services) each with its own OpenAPI 3.0.3 definition, conformance
  declaration (OGC API Common/Features parts 1-3, 6, 8 and CQL2) and anonymous GeoJSON access. Five representative dataset
  contracts are captured here.'
url: https://artifacts.apis.io/hamburg-de/apis.yml
x-type: company
x-source: harvest:eu-gov-keynote-2026-11-10
x-tier: profiled
x-tier-reason: enrichment pass 2026-11-10 (local-v6; was harvest)
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
specificationVersion: '0.20'
created: '2026-11-10'
modified: '2026-11-10'
tags:
- Government
- Open Data
- Geospatial
- OGC API Features
- Smart City
- Germany
- Urban Data Platform
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Conventions
  url: conventions/hamburg-de-conventions.yml
- type: AgenticAccess
  url: agentic-access/hamburg-de-agentic-access.yml
- type: Spectral
  url: rules/hamburg-de-rules.yml
- type: JSONLD
  url: json-ld/hamburg-de-context.jsonld
- type: Vocabulary
  url: vocabulary/hamburg-de-vocabulary.yml
- type: DataModel
  url: data-model/hamburg-de-data-model.yml
- type: ErrorCatalog
  url: errors/hamburg-de-problem-types.yml
- type: Conformance
  url: conformance/hamburg-de-conformance.yml
- type: SecurityTxt
  url: well-known/hamburg-de-www-security.txt
- type: SecurityTxt
  url: well-known/hamburg-de-security.txt
- type: WellKnown
  url: well-known/hamburg-de-well-known.yml
- type: Hosts
  url: hosts/hamburg-de-hosts.yml
- type: Authentication
  url: authentication/hamburg-de-authentication.yml
- type: DomainSecurity
  url: security/hamburg-de-domain-security.yml
- type: Website
  url: https://www.hamburg.de/
- type: APIReference
  url: https://api.hamburg.de/datasets/v1?f=html
- type: APIsCatalog
  url: https://api.hamburg.de/datasets/v1?f=json
- type: Documentation
  url: https://www.urbandataplatform.hamburg/daten-finden/
- type: PrivacyPolicy
  url: https://www.hamburg.de/datenschutz-dsgvo-66302
- type: Imprint
  url: https://www.hamburg.de/impressum-240706
apis:
- aid: hamburg-de:hamburg-de-access-data-api
  name: Freie und Hansestadt Hamburg Access data API
  description: The Access data API from Freie und Hansestadt Hamburg — 40 operation(s) for access data.
  humanURL: https://api.hamburg.de/datasets/v1/badegewaesser?f=html
  baseURL: https://api.hamburg.de/datasets/v1/badegewaesser
  tags:
  - Access data
  properties:
  - type: OpenAPI
    url: openapi/hamburg-de-access-data-api-openapi.yml
  - type: Conformance
    url: https://api.hamburg.de/datasets/v1/badegewaesser/conformance?f=json
  - type: Conformance
    url: https://api.hamburg.de/datasets/v1/baustellen/conformance?f=json
  - type: Conformance
    url: https://api.hamburg.de/datasets/v1/bplaene/conformance?f=json
  - type: Conformance
    url: https://api.hamburg.de/datasets/v1/denkmalschutz/conformance?f=json
  - type: Conformance
    url: https://api.hamburg.de/datasets/v1/emobility/conformance?f=json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-geo-json-badegewaesser-proben-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-collection-geo-json-badegewaesser-proben-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-collection-geo-json-badegewaesser-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-geo-json-badegewaesser-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-geo-json-tns-steckbrief-visualisierung-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-geo-json-baustelle-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-collection-geo-json-tns-steckbrief-visualisierung-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-collection-geo-json-baustelle-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-collection-geo-json-hh-hh-festgestellt-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-collection-geo-json-prosin-imverfahren-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-geo-json-hh-hh-festgestellt-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-geo-json-prosin-imverfahren-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-geo-json-juedischer-friedhof-altona-grabmal-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-collection-geo-json-kd-juedischer-friedhof-altona-quadrant-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-collection-geo-json-juedischer-friedhof-altona-grabmal-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-collection-geo-json-denkmalobjekte-symbolhaft-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-collection-geo-json-kd-flaechen-aussenanlagen-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-collection-geo-json-flaechen-gartendenkmale-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-geo-json-stromnetz-emobility-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-feature-collection-geo-json-stromnetz-emobility-schema.json
- aid: hamburg-de:hamburg-de-capabilities-api
  name: Freie und Hansestadt Hamburg Capabilities API
  description: The Capabilities API from Freie und Hansestadt Hamburg — 3 operation(s) for capabilities.
  humanURL: https://api.hamburg.de/datasets/v1/badegewaesser?f=html
  baseURL: https://api.hamburg.de/datasets/v1/badegewaesser
  tags:
  - Capabilities
  properties:
  - type: OpenAPI
    url: openapi/hamburg-de-capabilities-api-openapi.yml
  - type: Conformance
    url: https://api.hamburg.de/datasets/v1/badegewaesser/conformance?f=json
  - type: Conformance
    url: https://api.hamburg.de/datasets/v1/baustellen/conformance?f=json
  - type: Conformance
    url: https://api.hamburg.de/datasets/v1/bplaene/conformance?f=json
  - type: Conformance
    url: https://api.hamburg.de/datasets/v1/denkmalschutz/conformance?f=json
  - type: Conformance
    url: https://api.hamburg.de/datasets/v1/emobility/conformance?f=json
  - type: JSONSchema
    url: json-schema/hamburg-de-conformance-declaration-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-landing-page-schema.json
- aid: hamburg-de:hamburg-de-discover-data-collections-api
  name: Freie und Hansestadt Hamburg Discover data collections API
  description: The Discover data collections API from Freie und Hansestadt Hamburg — 81 operation(s) for discover data collections.
  humanURL: https://api.hamburg.de/datasets/v1/badegewaesser?f=html
  baseURL: https://api.hamburg.de/datasets/v1/badegewaesser
  tags:
  - Discover data collections
  properties:
  - type: OpenAPI
    url: openapi/hamburg-de-discover-data-collections-api-openapi.yml
  - type: Conformance
    url: https://api.hamburg.de/datasets/v1/badegewaesser/conformance?f=json
  - type: Conformance
    url: https://api.hamburg.de/datasets/v1/baustellen/conformance?f=json
  - type: Conformance
    url: https://api.hamburg.de/datasets/v1/bplaene/conformance?f=json
  - type: Conformance
    url: https://api.hamburg.de/datasets/v1/denkmalschutz/conformance?f=json
  - type: Conformance
    url: https://api.hamburg.de/datasets/v1/emobility/conformance?f=json
  - type: JSONSchema
    url: json-schema/hamburg-de-collection-schema.json
  - type: JSONSchema
    url: json-schema/hamburg-de-collections-schema.json
x-enrichment:
  date: '2026-11-10'
  status: enriched
  artifacts_added: 12
  pass: local-v6

Freie und Hansestadt Hamburg API — frequently asked questions

Does Freie und Hansestadt Hamburg have an API?

Yes. APIs.io lists 3 APIs from Freie und Hansestadt Hamburg, including Freie und Hansestadt Hamburg Access data API, Freie und Hansestadt Hamburg Capabilities API and Freie und Hansestadt Hamburg Discover data collections API.

Is there an OpenAPI specification for the Freie und Hansestadt Hamburg API?

Yes. APIs.io indexes 3 OpenAPI specifications for Freie und Hansestadt Hamburg, each linked for download from this page.

How do I authenticate with the Freie und Hansestadt Hamburg API?

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

Is the Freie und Hansestadt Hamburg API ready for AI agents?

Freie und Hansestadt Hamburg has a Kin Score of 35.6 out of 100 (thin) and an Agent Readiness score of 20.3 (agent-aware), 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/hamburg-de"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/hamburg-de/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.

GitHub Google LinkedIn

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