# Models management

**URL:** <https://support.prodi.gy/t/models-management/1488>\
**Category:** Uncategorized\
**Tags:** usage, ner, spacy, solved\
**Created:** [May 6, 2019, 7:21pm UTC](https://support.prodi.gy/t/models-management/1488 "2019-05-06T19:21:24Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [May 6, 2019, 9:22pm UTC](https://support.prodi.gy/t/models-management/1488/4 "2019-05-06T21:22:35Z")

</div>

What happens if you actually call the function instead of trying to serve it? See here:

> [@using prodigy.serve for textcat.batch-train](https://support.prodi.gy/t/using-prodigy-serve-for-textcat-batch-train/1405/12):
>
> Btw, no idea why I didn’t think of this earlier but… prodigy.serve is really mostly intended for serving the Prodigy application. The batch\_train recipe is just a regular function, so the easiest way to use it is to import it and call it as a function. from prodigy.recipes.textcat import batch\_train batch\_train(...) # etc.

Sorry I didn't think of this explanation earlier – this is also how Prodigy does it under the hood.

---

_[View the full topic](https://support.prodi.gy/t/models-management/1488)._