Tokyo Metropolitan Open Data

Tokyo Metropolitan Open Data is a regional government open-data portal for Japan running CKAN. It exposes the CKAN catalog API, a standardized machine-readable interface over approximately 9,675 datasets, supporting programmatic dataset search, metadata retrieval, and resource access. Because it runs CKAN, it shares a consistent API surface with every other CKAN portal, making it uniformly harvestable and integrable.

Tokyo Metropolitan Open Data is listed with 1 API on the APIs.io network. Tagged areas include Open Data, CKAN, Data Catalog, DCAT, and Government Data.

Tokyo Metropolitan Open Data’s developer surface includes documentation and 6 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

9.1/100 minimal ▬ flat Agent 1/100 human only saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFree

1 API

Open Data CKAN Data Catalog DCAT Government Data Regional Government Japan

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 9.1/100 · minimal

Contract Quality 0.0 / 21

Developer Ergonomics 1.6 / 17

Access Clarity 0.9 / 17

Operational Transparency 0.6 / 11

Contract Governance 0.0 / 10

Discoverability 5.6 / 9

Regulatory Posture 0.9 / 15

Agent readiness — 1/100 · human only

Machine-Readable Contract 0 / 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 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 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 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 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/catalog-data-metro-tokyo-lg-jp/"><img src="https://apis.io/badge/catalog-data-metro-tokyo-lg-jp/card.svg" alt="Tokyo Metropolitan Open Data 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):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
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)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes

12 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 5.3 — up to +18.9 composite points
Developer Ergonomics scores 9.5 — up to +18.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/catalog-data-metro-tokyo-lg-jp/apis.yml: open an issue on github.com/api-evangelist/catalog-data-metro-tokyo-lg-jp 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.

The CKAN Action API 2.11.4

tested — the operations were called against a live endpoint

63 core of 134 operations graded · api-commons/open-data

APIs 1

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

Tokyo Metropolitan Open Data CKAN Action API

CKAN Action API for Tokyo Metropolitan Open Data, a consistent JSON-over-HTTP interface over a catalog of 9,675 datasets. Standard actions include package_search, package_show, ...

Tokyo Metropolitan Open Data API pricing

Not yet checked against Tokyo Metropolitan Open Data's own pricing page. Compiled by API Evangelist on 2026-06-04 from raw.githubusercontent.com/api-evangelist/catalog-data-met...; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Free / Open Data free	Free

Plan details, limits and sources →

Rate limits

Default: see portal documentation requests per minute

Compiled by API Evangelist, not yet checked against Tokyo Metropolitan Open Data's documentation. Rate-limit details →

Pricing Plans 1

Published pricing tiers and plan structures.

Catalog Data Metro Tokyo Lg Jp Plans Pricing

1 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Catalog Data Metro Tokyo Lg Jp Rate Limits

1 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Catalog Data Metro Tokyo Lg Jp Finops

FINOPS

Security Posture 1

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

Catalog Data Metro Tokyo Lg Jp Domain Security

TLSv1.3

SECURITY

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 1

The organization behind the API

Website

Website

Other 1

Properties that don't map to a standard resource type

Review

Review

Source (apis.yml)

aid: catalog-data-metro-tokyo-lg-jp
name: Tokyo Metropolitan Open Data
description: Tokyo Metropolitan Open Data is a regional government open-data portal for Japan running CKAN. It exposes the
  CKAN catalog API, a standardized machine-readable interface over approximately 9,675 datasets, supporting programmatic dataset
  search, metadata retrieval, and resource access. Because it runs CKAN, it shares a consistent API surface with every other
  CKAN portal, making it uniformly harvestable and integrable.
kind: government
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: free
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Free
  confidence: low
  source:
  - plans
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/catalog-data-metro-tokyo-lg-jp.png
url: https://raw.githubusercontent.com/api-evangelist/catalog-data-metro-tokyo-lg-jp/refs/heads/main/apis.yml
x-docs-platform: readthedocs
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-09-21
tags:
- Open Data
- CKAN
- Data Catalog
- DCAT
- Government Data
- Regional Government
- Japan
created: '2026-06-04'
modified: '2026-06-04'
specificationVersion: '0.23'
apis:
- aid: catalog-data-metro-tokyo-lg-jp:catalog
  name: Tokyo Metropolitan Open Data CKAN Action API
  description: CKAN Action API for Tokyo Metropolitan Open Data, a consistent JSON-over-HTTP interface over a catalog of 9,675
    datasets. Standard actions include package_search, package_show, package_list, organization_list, group_list, tag_list,
    and resource_search; datastore_search is available where the DataStore extension is enabled. Base URL https://catalog.data.metro.tokyo.lg.jp/api/3/action/.
  humanURL: https://catalog.data.metro.tokyo.lg.jp
  baseURL: https://catalog.data.metro.tokyo.lg.jp/api/3/action
  tags:
  - CKAN
  - Action API
  - Open Data
  - Catalog
  - REST
  - JSON
  properties:
  - type: Documentation
    url: https://docs.ckan.org/en/latest/api/
  - type: Website
    url: https://catalog.data.metro.tokyo.lg.jp
  - type: x-api-endpoint
    url: https://catalog.data.metro.tokyo.lg.jp/api/3/action/status_show
common:
- type: DomainSecurity
  url: security/catalog-data-metro-tokyo-lg-jp-domain-security.yml
- type: Website
  url: https://catalog.data.metro.tokyo.lg.jp
- type: Documentation
  url: https://docs.ckan.org/en/latest/api/
- type: Plans
  url: plans/catalog-data-metro-tokyo-lg-jp-plans-pricing.yml
- type: RateLimits
  url: rate-limits/catalog-data-metro-tokyo-lg-jp-rate-limits.yml
- type: FinOps
  url: finops/catalog-data-metro-tokyo-lg-jp-finops.yml
- type: Review
  url: review.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Tokyo Metropolitan Open Data API — frequently asked questions

Does Tokyo Metropolitan Open Data have an API?

Yes. APIs.io lists 1 API from Tokyo Metropolitan Open Data, including Tokyo Metropolitan Open Data CKAN Action API.

How much does the Tokyo Metropolitan Open Data API cost?

APIs.io lists 1 pricing plan for Tokyo Metropolitan Open Data, with each plan's price, limits and inclusions under Pricing on this page.

Is the Tokyo Metropolitan Open Data API ready for AI agents?

Tokyo Metropolitan Open Data has a Kin Score of 9.1 out of 100 (minimal) and an Agent Readiness score of 0.6 (human-only), scored by API Evangelist on 2026-11-06.

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/catalog-data-metro-tokyo-lg-jp"

All providers

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

Every operation they expose

curl "https://apis.io/api/v1/providers/catalog-data-metro-tokyo-lg-jp/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/catalog-data-metro-tokyo-lg-jp/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.