Oslo kommune

Oslo kommune (the City of Oslo, Norway) is the municipal government of Norway's capital. Its public machine-readable surface is Statistikkbanken, a PxWeb statistics bank whose PxWeb JSON API serves Oslo population, housing, income and welfare tables, plus the Origo Dataplatform (api.data.oslo.systems) used through the first-party okdata-sdk and okdata-cli Python packages, whose APIs require Keycloak credentials.

Oslo kommune is listed with 2 APIs on the APIs.io network. Tagged areas include Government, Municipality, Norway, Open Data, and Statistics.

Oslo kommune’s developer surface includes support and 12 more developer resources.

15.9/100 emerging Agent 3/100 human only Heartbeat 100/100 alive Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →
2 APIs
GovernmentMunicipalityNorwayOpen DataStatisticsPxWebPublic Sector

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 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. Kin Score badge preview for Oslo kommune It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/oslo-kommune-no/"><img src="https://apis.io/badge/oslo-kommune-no/card.svg" alt="Oslo kommune 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 Ask about this →
  • 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 →
  • Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author 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 →
  • 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) Ask about this →
  • Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
12 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:
Oslo Kommune No · 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/oslo-kommune-no/apis.yml: open an issue on github.com/api-evangelist/oslo-kommune-no 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 2

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

Oslo Statistikkbanken PxWeb API

PxWeb JSON API behind Oslo kommune Statistikkbanken, listing statistical databases and tables (Befolkning, Inntekt, Boliger ...) that can be queried as JSON; the statistics bank...

Oslo Origo Dataplatform API

Origo Dataplatform services (metadata/datasets, data-exporter, pipeline, status-api, permission API) at api.data.oslo.systems, consumed via the okdata-sdk and okdata-cli; anonym...

Oslo kommune API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Oslo kommune Rate Limits

0 limits

RATE LIMITS

Security Posture 2

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

Oslo kommune Domain Security

TLSv1.3 · HSTS · DNSSEC

SECURITY

Oslo kommune Vulnerability Disclosure

security.txt · contact published

SECURITY

Resources

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: oslo-kommune-no
name: Oslo kommune
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  probe_state: unreadable
  source:
  - security
  generated: '2026-11-13'
  method: derived
image: https://ukeweb-public.s3.dualstack.eu-central-1.amazonaws.com/assets/FallbackImage4.png
description: Oslo kommune (the City of Oslo, Norway) is the municipal government of Norway's capital. Its public machine-readable
  surface is Statistikkbanken, a PxWeb statistics bank whose PxWeb JSON API serves Oslo population, housing, income and welfare
  tables, plus the Origo Dataplatform (api.data.oslo.systems) used through the first-party okdata-sdk and okdata-cli Python
  packages, whose APIs require Keycloak credentials.
url: https://artifacts.apis.io/oslo-kommune-no/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)
specificationVersion: '0.20'
created: '2026-11-10'
modified: '2026-11-10'
tags:
- Government
- Municipality
- Norway
- Open Data
- Statistics
- PxWeb
- Public Sector
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Security
  url: https://www.oslo.kommune.no/security-policy/
- type: SecurityTxt
  url: well-known/oslo-kommune-no-security.txt
- type: WellKnown
  url: well-known/oslo-kommune-no-well-known.yml
- type: Hosts
  url: hosts/oslo-kommune-no-hosts.yml
- type: Vendors
  url: vendors/oslo-kommune-no-vendors.yml
- type: SDKs
  url: packages/oslo-kommune-no-packages.yml
- type: Packages
  url: packages/oslo-kommune-no-packages.yml
- type: VulnerabilityDisclosure
  url: security/oslo-kommune-no-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/oslo-kommune-no-domain-security.yml
- type: Website
  url: https://www.oslo.kommune.no
- type: GitHubOrganization
  url: https://github.com/oslokommune
- type: PrivacyPolicy
  url: https://www.oslo.kommune.no/personvern-og-informasjonskapsler/
- type: Support
  url: https://www.oslo.kommune.no/oxlo/kontakt-oss/
apis:
- aid: oslo-kommune-no:statistikkbanken-pxweb-api
  name: Oslo Statistikkbanken PxWeb API
  description: PxWeb JSON API behind Oslo kommune Statistikkbanken, listing statistical databases and tables (Befolkning,
    Inntekt, Boliger ...) that can be queried as JSON; the statistics bank page points users to the API for Excel/PowerBI
    retrieval.
  humanURL: https://statistikkbanken.oslo.kommune.no/
  baseURL: https://statistikkbanken.oslo.kommune.no/statbank/api/v1/no/db1/
  tags:
  - Statistics
  - PxWeb
  - Open Data
  properties:
  - type: Documentation
    url: https://statistikkbanken.oslo.kommune.no/
- aid: oslo-kommune-no:origo-dataplatform-api
  name: Oslo Origo Dataplatform API
  description: Origo Dataplatform services (metadata/datasets, data-exporter, pipeline, status-api, permission API) at api.data.oslo.systems,
    consumed via the okdata-sdk and okdata-cli; anonymous requests are refused (403) and access uses Oslo kommune Keycloak
    credentials.
  humanURL: https://github.com/oslokommune/okdata-sdk-python
  baseURL: https://api.data.oslo.systems
  tags:
  - Data Platform
  - Datasets
  properties:
  - type: SourceCode
    url: https://github.com/oslokommune/okdata-sdk-python
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  detail: Oslo kommune exposes a live PxWeb JSON API behind Statistikkbanken but publishes no OpenAPI or other contract for
    it, and developer.oslo.kommune.no now says the page no longer exists; the Origo Dataplatform answers 403 anonymously.
  evidence:
  - url: https://statistikkbanken.oslo.kommune.no/statbank/api/v1/no/db1/
    status: 200
  - url: https://developer.oslo.kommune.no/
    status: 200
  - url: https://api.data.oslo.systems/metadata/datasets
    status: 403
  checked: '2026-11-10'
x-enrichment:
  date: '2026-11-10'
  status: minimal
  artifacts_added: 4
  pass: local-v6

Oslo kommune API — frequently asked questions

Does Oslo kommune have an API?

Yes. APIs.io lists 2 APIs from Oslo kommune, including Oslo Statistikkbanken PxWeb API and Oslo Origo Dataplatform API.

Is the Oslo kommune API ready for AI agents?

Oslo kommune has a Kin Score of 15.9 out of 100 (emerging) and an Agent Readiness score of 2.5 (human-only), 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/oslo-kommune-no"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/oslo-kommune-no/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/oslo-kommune-no/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.