# Is the "AI" capability in FMS "Metered" like the Data API?

**URL:** <https://the.fmsoup.org/t/is-the-ai-capability-in-fms-metered-like-the-data-api/5203>\
**Category:** Questions\
**Created:** [January 7, 2026, 11:34pm UTC](https://the.fmsoup.org/t/is-the-ai-capability-in-fms-metered-like-the-data-api/5203 "2026-01-07T23:34:13Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [January 7, 2026, 11:34pm UTC](https://the.fmsoup.org/t/is-the-ai-capability-in-fms-metered-like-the-data-api/5203/1 "2026-01-07T23:34:13Z")

</div>

Just wanted to ask if Claris “meters” (hopefully can charge a surcharge) AI usage when you enable the AI functionality in FMS.

Considering what they do with the _Data API_ (actually _meter_ software you’ve paid for), I wanted to check what they might be doing with FMS now before even considering using the AI feature. I’ve never used the Data API either because of the metering.

It’s very easy to use AI functionality in FileMaker without this FMS AI feature enabled. I’ve been using AI in FileMaker (LLMs, only) using external methods long before Claris implemented this latest feature.

Thanks in advance,

---

<div class="post-metadata">

**Author:** ![steve\_ssh](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/steve_ssh/32/160_2.png) [@steve\_ssh](https://the.fmsoup.org/u/steve_ssh)\
**Post date:** [January 8, 2026, 1:04am UTC](https://the.fmsoup.org/t/is-the-ai-capability-in-fms-metered-like-the-data-api/5203/2 "2026-01-08T01:04:18Z")

</div>

Hi @OliverBarrett

**Related to this:**

It might be worth revisiting the topic of Data API metering. I believe that the metering limits were removed for on-premise production installations starting around one major version ago.

[This KB article](https://support.claris.com/s/article/Understanding-the-Data-API-Annual-Limits?language=en_US) could help clarify.

HTH.

---

<div class="post-metadata">

**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\
**Post date:** [January 8, 2026, 4:33am UTC](https://the.fmsoup.org/t/is-the-ai-capability-in-fms-metered-like-the-data-api/5203/3 "2026-01-08T04:33:53Z")

</div>

You will utilise an existing account with one of the major AI providers, or you will use a custom LLM. Presumably a custom LLM will be in-house and will not be metered.

If you have an account with an AI provider then it is being monitored and billed. That is completely separate to Claris.

Some of the tools that Claris provides allows you to track token usage. The training tutorials also provide advice around token usage and ways to minimise token usage.

---

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [January 8, 2026, 11:01am UTC](https://the.fmsoup.org/t/is-the-ai-capability-in-fms-metered-like-the-data-api/5203/4 "2026-01-08T11:01:38Z")

</div>

Thanks Steve.

This paragraph was confusing at the top of that KB article:

”For customers using Claris FileMaker Server 21 or later versions in an on-premise environment, the Data API and OData usage restrictions have been removed. **FileMaker Developer Subscription and FileMaker Cloud continue to be restricted.** ”

So, I’m using FileMaker Devleoper but it’s “on-prem” (AWS). So, is that restricted (metered) or not?

Thanks very much for your reply.

---

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [January 8, 2026, 11:02am UTC](https://the.fmsoup.org/t/is-the-ai-capability-in-fms-metered-like-the-data-api/5203/5 "2026-01-08T11:02:31Z")

</div>

Thank you Malcolm. 😀

---

<div class="post-metadata">

**Author:** ![steve\_ssh](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/steve_ssh/32/160_2.png) [@steve\_ssh](https://the.fmsoup.org/u/steve_ssh)\
**Post date:** [January 8, 2026, 6:30pm UTC](https://the.fmsoup.org/t/is-the-ai-capability-in-fms-metered-like-the-data-api/5203/6 "2026-01-08T18:30:01Z")

</div>

> [@OliverBarrett](#):
>
> **FileMaker Developer Subscription and FileMaker Cloud continue to be restricted.** ”

Hi @OliverBarrett . I would interpret that line as saying that the Developer Subscription version still has the original restrictions, i.e., the metering.

---

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [January 9, 2026, 12:35pm UTC](https://the.fmsoup.org/t/is-the-ai-capability-in-fms-metered-like-the-data-api/5203/7 "2026-01-09T12:35:36Z")

</div>

Yep, me too. That’s OK, I never use Data API anyway.

Thanks Steve.

---

<div class="post-metadata">

**Author:** ![steve\_ssh](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/steve_ssh/32/160_2.png) [@steve\_ssh](https://the.fmsoup.org/u/steve_ssh)\
**Post date:** [January 9, 2026, 3:54pm UTC](https://the.fmsoup.org/t/is-the-ai-capability-in-fms-metered-like-the-data-api/5203/8 "2026-01-09T15:54:27Z")

</div>

Understood that it may never be the case, but, should you ever start working with a production version of FileMaker Server (i.e. not the developer subscription), I would suggest shifting any potential attention that would have gone to the Data API to instead try out the OData API. I suspect it that might be a better fit.

---

<div class="post-metadata">

**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\
**Post date:** [January 10, 2026, 7:58am UTC](https://the.fmsoup.org/t/is-the-ai-capability-in-fms-metered-like-the-data-api/5203/9 "2026-01-10T07:58:53Z")

</div>

> [@steve\_ssh](#):
>
> I would suggest shifting any potential attention that would have gone to the Data API to instead try out the OData API.

Claris has been signalling that we should be planning to move to OData API.

---

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [January 10, 2026, 12:43pm UTC](https://the.fmsoup.org/t/is-the-ai-capability-in-fms-metered-like-the-data-api/5203/10 "2026-01-10T12:43:35Z")

</div>

I use the Data API in one place in a client app to run a script programmatically. If Claris breaks that support, as in stop supporting the Data API, that would break the client’s application.

For me, in 99.999% of all cases, I’ll stick with JDBC which has full read/write access, also a long-standard, and the full Java language behind it. So much more powerful. SQL is such a better and universal way of table CRUD ops (READ, UPDATE, INSERT, and DELETE).

---

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [January 10, 2026, 12:46pm UTC](https://the.fmsoup.org/t/is-the-ai-capability-in-fms-metered-like-the-data-api/5203/11 "2026-01-10T12:46:04Z")

</div>

Posting removed. Issues resolved.

---

<div class="post-metadata">

**Author:** ![flybynight](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/flybynight/32/1023_2.png) [@flybynight](https://the.fmsoup.org/u/flybynight)\
**Post date:** [January 12, 2026, 4:06pm UTC](https://the.fmsoup.org/t/is-the-ai-capability-in-fms-metered-like-the-data-api/5203/12 "2026-01-12T16:06:35Z")

</div>

> [@OliverBarrett](#):
>
> I use the Data API in one place in a client app to run a script programmatically. If Claris breaks that support, as in stop supporting the Data API, that would break the client’s application.

The indication has been that Claris will not drop support for the Data API. They just won’t be putting any new resources into it. Very similar to ESS/ODBC. It’s still there, but not getting any attention. If your existing DAPI solution is working, probably not worth changing it. But if you are going to be doing any new integration, it would be worth looking into the OData API.

---

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [January 12, 2026, 8:02pm UTC](https://the.fmsoup.org/t/is-the-ai-capability-in-fms-metered-like-the-data-api/5203/13 "2026-01-12T20:02:45Z")

</div>

I use JDBC for read/write stuff.

OData is read-only and very limited.

---

<div class="post-metadata">

**Author:** ![flybynight](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/flybynight/32/1023_2.png) [@flybynight](https://the.fmsoup.org/u/flybynight)\
**Post date:** [January 12, 2026, 10:43pm UTC](https://the.fmsoup.org/t/is-the-ai-capability-in-fms-metered-like-the-data-api/5203/14 "2026-01-12T22:43:51Z")

</div>

In older versions, that was true. But OData can now be used for full CRUD operations.

> **[Write OData API calls](https://help.claris.com/en/odata-guide/content/write-odata-api-calls.html)**

---

<div class="post-metadata">

**Author:** ![steve\_ssh](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/steve_ssh/32/160_2.png) [@steve\_ssh](https://the.fmsoup.org/u/steve_ssh)\
**Post date:** [January 12, 2026, 11:37pm UTC](https://the.fmsoup.org/t/is-the-ai-capability-in-fms-metered-like-the-data-api/5203/15 "2026-01-12T23:37:24Z")

</div>

I do not recall any version of OData which was read-only. It certainly has various aspects to consider, and its roll-out has been in phases, but, as far as I recall, from the start, it was supporting full CRUD operations, as well as Batch and Change-Set operations to allow for atomic/transactional updates.

I mention this not to try to persuade anyone to prefer one API over another, but just as a point of clarification.

If I am mistaken, and there ever has been a version of OData which was read-only, I would appreciate someone pointing me to that documentation or version so that I could then clarify my own mistaken notions.

---

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [January 13, 2026, 11:55am UTC](https://the.fmsoup.org/t/is-the-ai-capability-in-fms-metered-like-the-data-api/5203/16 "2026-01-13T11:55:44Z")

</div>

Apparently, I was mistaken. Apologies. I did get some online info that said read-only, but that was clearly incorrect.

Thank you for pointing this out.

---

<div class="post-metadata">

**Author:** ![OliverBarrett](https://avatars.discourse-cdn.com/v4/letter/o/f19dbf/32.png) [@OliverBarrett](https://the.fmsoup.org/u/OliverBarrett)\
**Post date:** [January 13, 2026, 11:56am UTC](https://the.fmsoup.org/t/is-the-ai-capability-in-fms-metered-like-the-data-api/5203/17 "2026-01-13T11:56:22Z")

</div>

That must have been what I saw. Thank you for pointing this out. I had never used ODATA before a few days ago.
