Tallinn

The City of Tallinn (Tallinna linn), capital of Estonia, publishes municipal open data through the Avaandmed API at avaandmed.tallinn.ee, a universal read-only GET /data/ query endpoint over city datasets that are documented on the Estonian Open Data Portal, plus a public city design system at design.tallinn.ee.

Tallinn publishes 1 API contract indexed on the APIs.io network: Data API. Tagged areas include Government, Municipal, Open Data, Estonia, and Smart City.

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

Tallinn’s developer surface includes documentation and 13 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

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

2 published contracts

Government Municipal Open Data Estonia Smart City Public Sector

Kin Score

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

Composite quality — 24.3/100 · emerging

Contract Quality 10.4 / 21

Developer Ergonomics 1.6 / 17

Access Clarity 0.0 / 17

Operational Transparency 2.1 / 11

Contract Governance 2.2 / 10

Discoverability 5.3 / 9

Regulatory Posture 0.7 / 15

Agent readiness — 21/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 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 3 / 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/tallinn-ee/"><img src="https://apis.io/badge/tallinn-ee/card.svg" alt="Tallinn 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 →
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) Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 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 →

6 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 0.0 — up to +20.0 composite points Ask about this →
Developer Ergonomics scores 9.5 — up to +18.1 composite points Ask about this →
Contract Quality scores 49.0 — up to +12.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/tallinn-ee/apis.yml: open an issue on github.com/api-evangelist/tallinn-ee 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 1

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

Tallinn Data API

The Data API from Tallinn — 1 operation(s) for data.

Tallinn API pricing

Rate limits

Concurrent requests: 5 concurrent reqests allowed
Query timeout: Max query timeout 20s

Rate-limit details →

Rate Limits 1

Documented rate limits and quota policies.

Tallinn Rate Limits

2 limits

RATE LIMITS

Semantic Vocabularies 1

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

Tallinn Ee Context

2 classes · 4 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.

Tallinn API Rules

33 rules · 31 error-severity 1 warn-severity 1 info-severity

SPECTRAL

Security Posture 1

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

Tallinn Domain Security

TLSv1.3 · DMARC

SECURITY

Agentic Access (API Evangelist recommendations) 1

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

Tallinn Agentic Access

1 operation

1 operations · 0 acting

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

DataModel

ErrorCatalog

Conformance

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Company 1

The organization behind the API

Website

Website

Other 3

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

DesignSystem

DesignSystem

Source (apis.yml)

aid: tallinn-ee
name: Tallinn
description: The City of Tallinn (Tallinna linn), capital of Estonia, publishes municipal open data through the Avaandmed
  API at avaandmed.tallinn.ee, a universal read-only GET /data/ query endpoint over city datasets that are documented on the
  Estonian Open Data Portal, plus a public city design system at design.tallinn.ee.
url: https://artifacts.apis.io/tallinn-ee/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
  probe_state: covered
  source:
  - rate-limits
  - security
  generated: '2026-11-13'
  method: derived
specificationVersion: '0.20'
created: '2026-11-10'
modified: '2026-11-10'
tags:
- Government
- Municipal
- Open Data
- Estonia
- Smart City
- Public Sector
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: AgenticAccess
  url: agentic-access/tallinn-ee-agentic-access.yml
- type: RateLimits
  url: rate-limits/tallinn-ee-rate-limits.yml
- type: Spectral
  url: rules/tallinn-ee-rules.yml
- type: JSONLD
  url: json-ld/tallinn-ee-context.jsonld
- type: Vocabulary
  url: vocabulary/tallinn-ee-vocabulary.yml
- type: DataModel
  url: data-model/tallinn-ee-data-model.yml
- type: ErrorCatalog
  url: errors/tallinn-ee-problem-types.yml
- type: Conformance
  url: conformance/tallinn-ee-conformance.yml
- type: Hosts
  url: hosts/tallinn-ee-hosts.yml
- type: Vendors
  url: vendors/tallinn-ee-vendors.yml
- type: DomainSecurity
  url: security/tallinn-ee-domain-security.yml
- type: Website
  url: https://www.tallinn.ee
- type: Documentation
  url: https://avaandmed.tallinn.ee/
- type: DesignSystem
  url: https://design.tallinn.ee/
apis:
- aid: tallinn-ee:tallinn-ee-data-api
  name: Tallinn Data API
  description: The Data API from Tallinn — 1 operation(s) for data.
  humanURL: https://avaandmed.tallinn.ee/
  baseURL: https://avaandmed.tallinn.ee/avaandmed/api
  tags:
  - Data
  properties:
  - type: OpenAPI
    url: openapi/tallinn-ee-data-api-openapi.yml
  - type: Documentation
    url: https://avaandmed.tallinn.ee/docs
x-enrichment:
  date: '2026-11-10'
  status: enriched
  artifacts_added: 12
  pass: local-v6
x-coverage:
  state: covered
  reason: covered
  detail: Avaandmed open-data API contract harvested from avaandmed.tallinn.ee; www.tallinn.ee answers a Cloudflare bot challenge
    to our probes.
  evidence:
  - url: https://avaandmed.tallinn.ee/openapi.json
    status: 200
  - url: https://www.tallinn.ee
    status: 403
  checked: '2026-11-10'

Tallinn API — frequently asked questions

Does Tallinn have an API?

Yes. APIs.io lists 1 API from Tallinn, including Tallinn Data API.

Is there an OpenAPI specification for the Tallinn API?

Yes. APIs.io indexes 1 OpenAPI specification for Tallinn, each linked for download from this page.

Is the Tallinn API ready for AI agents?

Tallinn has a Kin Score of 24.3 out of 100 (emerging) and an Agent Readiness score of 20.8 (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/tallinn-ee"

All providers

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

Every operation they expose

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

How their score was established

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