> For the complete documentation index, see [llms.txt](https://doc.api.tieto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.api.tieto.com/features/limits-fees-and-monetization.md). # Fees and Monetization The Platform offers a suite of detailed API usage reports to facilitate billing TPPs by tenant banks and by Platform Operator (in case you offer your own products). The platform is also capable of reporting traffic per tenant, which allows you to leverage our reporting capabilities for billing your tenants. ## Pricing models for TPPs Fees are set by whoever publishes the product — a tenant bank for its own APIs, you for yours — because pricing describes a relationship between a publisher and its third parties. Two fee types combine. | Fee type | Behavior | | ------------- | --------------------------------------------------------------------------------------------------------------------------- | | Recurring fee | Charged per period — daily, weekly, monthly or quarterly, per the publisher's billing preference. | | Per-call fee | Either flat, or progressive — for example free for the first thousand calls in a period, then charged per call beyond that. | Fees attach to an individual API product rather than to a subscription as a whole, so a third party subscribing to several products can be on different terms for each. ## Custom Billing IDs The Platform's API Management UI allows administrators to assign custom billing IDs to APIs, so billing reports aggregate traffic not only by endpoint, but also by billing ID. In this way a commercial line that spans a dozen endpoints arrives as one figure instead of a sum someone assembles by hand. ## Transparency to the buyer The Developer Portal shows the fees against each product — recurring fee, per-call fee and the counter period. This matters commercially: a developer evaluating an API can see the price without a conversation. Third parties can then track what they have accrued through their own fee reports. API providers see what is owed to them through outstanding fee reports. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://doc.api.tieto.com/features/limits-fees-and-monetization.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.