There's a lot of misunderstanding here. As someone that has been in a similar situation:
1. It's not Apple, it was Workflows that wrote the tool.
2. It's not an integration, it's an example of how to use Shortcuts.
3. The biggest pain point won't be bandwidth (OP seems to know what they're doing with caching) but fielding user requests/complaints/spam without the upside of the web traffic. iOS 12 has only been up for a few days and he's already getting a ukulele request. Tip of the iceberg.
> We can work together to make this experience even better.
This isn't "working together". This is someone at Workflows finding a neat, unauthenticated API endpoint and using it in a demo. I doubt Apple knows about it.
1. It's not Apple, it was Workflows that wrote the tool.
2. It's not an integration, it's an example of how to use Shortcuts.
3. The biggest pain point won't be bandwidth (OP seems to know what they're doing with caching) but fielding user requests/complaints/spam without the upside of the web traffic. iOS 12 has only been up for a few days and he's already getting a ukulele request. Tip of the iceberg.
> We can work together to make this experience even better.
This isn't "working together". This is someone at Workflows finding a neat, unauthenticated API endpoint and using it in a demo. I doubt Apple knows about it.