Open Data Value by Jarkko Moilanen

For developers and AI agents

One value model. Multiple ways to access it.

Open Data Value exposes the same portfolio evidence through live agent tools, stable HTTP APIs, machine-readable resources and standards-based SDK workflows.

Read-only by design.
Value Portfolio connected to MCP, REST API, Open Data Products SDK and Direct Resources.

Choose your access path

Four ways to connect

Access the same portfolio data through the method that fits your needs.

MCP

Live tool-based access for AI agents.

 REST API

Read-only HTTP endpoints for applications and scripts.

 SDK

Python workflows for the Open Data Products standards family.

 Direct Resources

Files, indexes and context resources generated for each portfolio.

What you can access

What you can access

The same portfolio evidence, available across all access paths.

ProductsOpen data products and their metadata
Use CasesDocumented use cases and value narratives
DatasetsSource datasets and processed metadata
GraphRelationships between products, use cases and datasets
OpportunitiesIdentified opportunities for data reuse
Standards BoundaryClear scopes aligned with open standards
Agent ResourcesAgent-optimized files, indexes and context resources

For AI agents

A clear path for agent workflows

Follow this sequence to get the best results.

  1. Read llms.txtUnderstand capabilities and guidance for agents.
  2. Read catalog-index.jsonDiscover available resources and structure.
  3. Use MCP for focused retrievalQuery specific portfolio information using agent tools.
  4. Use direct resources for bulk contextAccess machine-readable files for larger context and analysis.
  5. Use the SDK for standards-family workflowsIntegrate into automated workflows and applications.

Read-only by design

Trusted, open access

Public access to Open Data Value is read-only and does not mutate source catalogs or review decisions. It provides a trusted view of portfolio evidence for exploration, analysis and reuse.

MCPRead-only tools and retrieval.
RESTRead-only HTTP endpoints.
ResourcesRead-only files and exports.
SDKRead-only workflows and local integration.
Trust rules
  • Source metadata is evidence from public catalogs.
  • Generated products and use cases remain reviewable by humans.
  • Standards exports should be read with the standards boundary.
  • Public access does not change source data, curation or review outcomes.

Start here

Explore the developer and agent access model

Open MCP endpoint View resource types