Integrations are where many AI-generated apps either become useful or fall apart. PromptUI's integration catalog gives Builder provider-aware context before files are written, so generated apps can include more realistic packages, environment variables, server/client boundaries, and setup notes.
Current catalog coverage
The catalog covers 30+ provider contracts across payments, auth, databases, email, AI models, AI media, voice, CRM, CMS, search, storage, analytics, scraping, RAG, and workflow tools. Current examples include Stripe, Supabase, Clerk, OpenAI, Anthropic, Gemini, Firebase, Neon, MongoDB Atlas, Shopify, PayPal, Slack, Notion, HubSpot, Sanity, Algolia, S3/R2, Replicate, fal.ai, and ElevenLabs.
Why typed contracts help
A provider-aware prompt can tell the Builder which package matters, which environment variables are expected, what belongs server-side, and what should be mocked or stubbed when credentials are missing. That is better than asking the model to invent integration glue from memory every time.
Provider-aware does not mean fully activated
This coverage should be described precisely. PromptUI can generate provider-aware app flows and starter-pack context. Native OAuth dashboards, credential health checks, and production smoke tests for every provider are deeper activation work, not something every catalog entry should claim today.
Where to explore it
The public provider surface lives at PromptUI integrations. The Builder uses the same catalog to keep integration intent visible inside generated app briefs.