At this time, I'm developing a new kind of social network based in: Movies, TV Shows and Books data. For my proposes, I'll develop a new kind of resources and filters. Then will be necessary to fill my own database with Movies, TV Shows and Books. It means, a long-term, I'll have my own data collection.

Books will be find in another database provider. For Movies and TV Shows, TMDb provides a lot of data. My ideia is:

1. The Movies, TV Shows and Books data will be indexed by my plataform inside my own database;
2. My users will find for Movies, TV Shows and Books in my plataform;
3. The resulted data will be from my database;
4. If they don't find what they want, there will be an option "Didn't find a Movie, TV Show or Book? Add it by clicking here".
5. Then, by clicking on there, they will be able to type a title and my plataform will get the right data from existing repositories (for Movies and TV Shows, will be TMDd).
6. Now, there will have a copy of TMDd information in my database. And I'll not use anymore data from TMDd for Movies and TV Show that already exists in my database.

USES OF TMDd API So... I just will use TMDd API when some user want to add a Movie/TV Show! In this way, they won't have to fill all information alone, the plataform will find it for them. For anything else, like: searches in plataform, movie page or tv series page, my own resources... the accessed data would be from my own database.

IMPORTANT CONSIDERATIONS When a user select "Didn't find a Movie, TV Show or Book? Add it by clicking here" there will have an information saying "We're using TMDd to collect data!".

Is that right? In another words... can I use the TMDb API to do that (only get data to create my own repository)? And... most important one: is this the better way of do this or you all recommend that I use the API to manage all data without a full copy inside my database?

I would be grateful if someone could help me!