Autodesk is evolving how AEC teams can access and use project data, moving beyond files to more connected information that teams can put to work across systems, automated processes and AI-powered workflows. As these capabilities expand, we’ve seen questions about what Autodesk charges for, when additional costs apply, how API pricing relates to customer ownership of project information and what other access options remain available. We sat down to address these questions directly and explain the value of the AEC Data Model APIs and how Autodesk is approaching customer choice, transparency and predictability.
Sasha: A design file contains an enormous amount of information. With the AEC Data Model, that information becomes structured, granular data that teams can access programmatically rather than always having to work through the entire file. That means a team can query the specific objects and properties a workflow needs. If you are interested in doors, for example, you can retrieve information about those doors without downloading and opening multiple models just to find those properties. That can reduce manual work and automate repetitive tasks like reporting and quality checks. It also makes it easier to connect project information across systems and use that data for analytics and AI-powered workflows. Our Snowdon Towers sample illustrates the difference. The entire model is about 90 MB, while retrieving all doors and their properties requires just 1.55 MB, and all the windows just 1.12 MB.
The value is not simply moving a file. It is getting the right project information, in a structured form, when a workflow needs it.
This is also part of the broader direction we’re taking with Autodesk Forma: helping teams keep project information connected and useful as work moves from one workflow to the next. The AEC Data Model APIs give customers and developers another way to put that information to work in the tools and workflows they build.
Sasha: No. Customers have multiple ways to access their project information. You can continue opening models in Revit, downloading files through Forma Data Management or export to IFC. Those workflows do not use the AEC Data Model APIs and are not subject to this pricing. The APIs add another option for teams that need structured, granular and programmatic access for custom tools, integrations and automated workflows. A file may be the right approach for one task; a targeted API query may make more sense for another. The APIs expand customer choice. They do not replace existing file-based workflows.
Theo: The first thing I want to be clear about is that your data is yours. Customers own the content they create, and that does not change under this business model.
Autodesk is charging for a specific API service that structures, queries and delivers granular project information to the tools customers build. We are not monetizing ownership of the underlying information.
Qualifying subscriptions already include monthly Data Out usage. Customers only pay incrementally when they go beyond what’s included.
Theo: When customers need additional capacity, consumption-based pricing offers flexibility and a way to scale beyond the API usage included with their subscriptions. How much Data Out a workflow consumes depends on the amount of project information it retrieves, so focused queries can use significantly less data than working with an entire model. Included amounts vary by qualifying product and subscription, so customers should review our current APS guidance for their applicable allowance and rates.
Theo: Customers need visibility into what they are using so they can make informed decisions and plan. That is why we introduced APS Usage Insights in Autodesk Assistant. Teams can ask plain-language questions about their APS API usage, including what an application consumed, how usage breaks down by API, how different periods compare and which applications are driving the most consumption. We give customers clear information about what is included, visibility into their usage and costs, and advance notice of pricing changes so they have time to plan.
Sasha: Granular access means asking for the elements a workflow needs and adjusting the information you need without moving an entire model every time. Take the Snowdon Towers example: all the door data totaled just 1.55 MB. If a consultant needs to use that information in an external pricing system, the API can retrieve only the relevant door properties rather than the entire model. That targeted approach gives the team the information it needs while helping to limit Data Out usage.
Theo: I understand why customers are asking. As software, data, compute and AI become more connected, customers naturally want to understand how commercial models will evolve. I don’t want to speculate about future products, rates or licensing models. What I can say is that we’ll continue to give customers clear information about what’s included, visibility into their usage and advance notice of pricing changes so they have time to plan. And we’ll continue to give customers choices in how they access and use their information.
Sasha: Customers own their project information. The AEC Data Model APIs add a structured, granular and automated way to access and put that information to work without existing file-based workflows. Our job is to give customers useful, flexible ways to get the right information to the right people at the right time. Theo: Autodesk is charging for a service, not the underlying project information. Our responsibility is to provide clarity and support, so customers understand what they are paying for and why, what is included and what choices they have.
For details on current AEC Data Model API pricing and qualifying subscriptions, the Autodesk Platform Services pricing guidance has more information. To understand your APS consumption, the APS Usage Insights in Autodesk Assistant provides a way to explore historical API usage and plan ahead.
My Revit model is 800 MB. Am I billed for all of it?
No. You’re billed for the data your query returns, not for the size of the model. Take Snowdon Towers, the 90 MB sample Revit model: retrieving everything about its doors comes to 1.55 MB, and its windows just 1.12 MB. The more precisely you ask, the less data you use. How is included usage shared across my organization?
Autodesk pools usage into Autodesk account teams. Your team organization can be found at manage.autodesk.com. Users and usage with a team are calculated together. Will my Power BI dashboards, automated reports, or data pipelines cost money each month?
There are no changes at this time to Forma Construction dashboard usage or other data pipelines that do not use the AEC Data Model APIs. What happens if I go past my included usage?
Will my integrations stop working? If your usage exceeds what’s included with your subscriptions, you will be billed monthly or tokens will be consumed from your token pool. Included usage and rates can be found here.
