Two questions:
1) In the example you show above, how are you figuring out which twitter accounts are linked to the channel ?
2) API integration is a one-time effort and largely done using libraries. Do you have a real world use case example ? My sense is most calls are isolated - for example I want to read my last few trasactions from Stripe or get last few tickets from Zendesk. Would it make sense to go through an intermediary like you and pay another monthly fee ?
For 1), we're parsing links the creator added on the about page of their YouTube channel.
For 2), a great example is https://heysavvy.com/, a company building omni-search across all your SaaS apps. Before OneGraph, they invested a lot of time learning the idiosyncrasies of the underlying API for each new integration they added. Now, they just open up the Explorer in GraphiQL and find exactly the fields they need without needing to look at documentation or install any new packages.
Hopefully it's also a bit of an answer to #2, showing how easy it is to explore and iterate an API, even without a library, so that should help speed up the initial one-time effort, and then we handle things like rate-limiting, inter-service dependency, and per-service optimization (like automatically switching between Salesforce's REST api and their Batch API, both of which have radically different implementations that would require an entire re-arch if you build on them directly).