btp-service-metadata
A machine-readable catalogue of the services available in an SAP BTP pay-as-you-go account, published as JSON files curated per persona, starting with the developer persona and an inventory list.
Finding what a BTP service offers usually means reading the Discovery Center by hand, one service at a time. This repository publishes the metadata as JSON files instead, curated per persona: the developer persona under v1/developer, with an inventory list giving an overview of all available services. The data moved to v1 on 8 January 2025 and the v0 directory is no longer updated. What is covered is what the developer persona needs, kept current by regular fetches; the maintainers say further personas and further curated metadata follow from feedback.
Facts
Where it sits
Who is behind it
In the atlas: maintains 222@SAP-samplesmaintainerAjinkya PatilContributes to this
In the atlas: contributes to 112@ajinkyapatil8190DJ AdamsContributes to this
Developer Advocate
In the atlas: contributes to 20, wrote 22@qmacroChristian LechnerContributes to this
In the atlas: contributes to 12, wrote 2@lechnerc77Rui NogueiraContributes to this
In the atlas: contributes to 6@rui16104 contributors
What it declares
Every artifact
- Type
- Doc source
- Origin
- By SAP
- Use as
- A reference
Connections
Finding answers in written documentation, and writing what is missing
Download
README
quoted from SAP-samples/btp-service-metadata under Apache-2.0, readbtp-service-metadata
Description
Important
08.01.2025: We updated the metadata to v1. The
v0directory will no longer be updated. The schema of the data changed e.g., you can now also find the commercial model per service plan is part of the data.
You are working with SAP BTP and looking for the metadata of the services in a machine-readable format? Then you are at the right place: this repository contains the metadata of the SAP BTP services.
As different personas need different metadata when exploring the service metadata we decided to curate it for you. As criterion we use a persona-based approach as we are convinced that this will give the optimal support for the task at hand.
We start with the persona "developer". Based on the requirements of this persona we collected the metadata per service in the folder v1/developer as JSON files. In addition, we provide an inventory list as an overview of all available services to enable to have a quick overview what is available and what is not.
Based on your feedback we will add additional personas and additional curated metadata.
Feedback
You may ask: what is your intention? The answer is that we would love to hear your feedback on:
- the data itself (is there something missing etc.).
- the ways how you would like to see the data provisioned for you. We are aware that plain JSON can only be a first step.
You do not know where to start? Need some inspiration? Then this section could be of interest to you.
Are you using the metadata?
Of course we leverage the information ourselves in the btp-setup-automator to generate the JSON schemas for the input files used in this open-source tool. Take a look at the repository to get some inspiration on how to leverage the data for your scenarios.
Update cycle
The data is fetched regularly to be up-to-date. If you experience that something is not up-to-date, please let us know via an issue
How to get support
Create an issue in this repository if you find a bug 🐞.
In case you would like to see an additional feature 🚀, feel free to open a feature request
In case of questions, we also have GitHub discussions activated 😎. This is the place to:
- Ask questions you’re wondering about
- Share ideas
- Engage with other community members
Contributing
If you wish to contribute code, offer fixes or improvements, please send a pull request. Due to legal reasons, contributors will be asked to accept a DCO when they create the first pull request to this project. This happens in an automated fashion during the submission process. SAP uses the standard DCO text of the Linux Foundation.
License
Copyright (c) 2026 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
History in the atlas
- First seen.
For your agent
- Ref
artifact:sap-samples-btp-service-metadata- JSON
- /artifacts/sap-samples-btp-service-metadata.json
- MCP
- Connecting an agent