We're working on the mechanics of deploying and scaling all the amazing prompt-based backends everyone is building --- chaining, prompt-search-prompt, image & audio generation.
This link is a simplified hosting harness we built building & launching a Python + Prompt API endpoint.
Especially for the set of problems with "Step 1: Hosting embeddings for some large corpus", it feels like there's a really useful role for offering static query/AKNN search atop popular datasets.
Please provide an alternative to ShipQL or just drop it entirely. Most developers I know are very allergic to learning new company-specific DSLs.
Re: DSLs -- what's the famous saying? "All services that survive eventually grow large enough to re-implement email"? :) We hear you though; if there's a way to support a standard QL atop the domain we're serving, we'll give it a good look.
Right now our examples are pretty simple. But you can chain prompts manually and/or pull in services like DALL-E or voice gen.
We're working on the rails to do that in a way that'll scale well cleanly across API users of your app.