Databases as Components—provided by component developers

As a developer, I should be able to create a component that attaches a database schema and records to an app.
For example, as a No-Code creator I may determine that I need access to a book database. I should be able to install a book database component which will then allow me to browse each API method below the same way as I browse any other table/view in Adalo.
Additionally, I should be able to see if the record is read-only and it’s relationship to other table records.

auth.user   —   Get id of user who authorized OAuth.
author.books   —   Paginate an author's books.
author.show   —   Get info about an author by id.
author_following.create   —   Follow an author.
author_following.destroy   —   Unfollow an author.
author_following.show   —   Show author following information.
book.isbn_to_id   —   Get Goodreads book IDs given ISBNs.
book.id_to_work_id   —   Get Goodreads work IDs given Goodreads book IDs.
book.review_counts   —   Get review statistics given a list of ISBNs.
book.show   —   Get the reviews for a book given a Goodreads book id.
book.show_by_isbn   —   Get the reviews for a book given an ISBN.
book.title   —   Get the reviews for a book given a title string.

As a developer, I would be responsible for defining this API in such a way that Adalo understands what is read-only, how records are related to one another, etc.
No-Code creators would then be able to create a relationship between a native record that they own (Users for example) and the API record.