The integration gap
Your product needs images.
Building an image pipeline is not your core competency.
Users expect to describe what they want — "heroic sunset over mountains" — and get images that match. Building that means: semantic search, commercial licensing, quality curation, generation pipelines, and ongoing maintenance.
That's a product in itself. You have a product to ship.
OKSLOP gives you the infrastructure. Semantic search API, generation endpoints, commercial license passthrough, and a curated library — so you can ship the feature without building the stack.
Why developers use this
Ship the feature. Skip the infrastructure.
Semantic search
Describe a feeling, not keywords. "Cozy autumn morning" finds what users mean, not just what matches text.
Generation on demand
When the library doesn't have it, generate it. Same API, same licensing. Users don't notice the difference.
License passthrough
Commercial rights flow to your users. No per-seat fees, no usage audits, no surprise invoices.
Curated quality
50k+ images, growing daily. Quality-filtered, tagged, ready to serve. No moderation pipeline needed.
Integration patterns
From POC to production. Same day.
Get API key
Free tier for development. Upgrade when you ship. No credit card for the sandbox.
Search or generate
Natural language query → images. If library doesn't have it, generation kicks in automatically (or you call it explicitly).
Serve to users
CDN-backed URLs, responsive variants, commercial license included. Embed directly.
Scale with usage
Pay for what you use. No per-seat, no per-download. Volume discounts at scale.
What you can integrate
APIs for every modality. Same interface.
Semantic search API
Natural language → images. CLIP-based similarity, mood matching, style filtering. Sub-100ms response times.
Generation API
Text → image, image → variations, style transfer. Multiple models, same endpoint. Queue-based for long jobs.
3D & splat API
Image → 3D model, text → 3D. GLB/USDZ output. Gaussian splats for immersive. Early but functional.
Embed API
Deterministic image URLs from text. "cozy-cafe-morning" → same image every time. Great for documentation, fallbacks.
MCP server
Model Context Protocol for AI agents. Claude, Cursor, Windsurf can search and generate images directly in the IDE.
React picker
Drop-in component for image selection. Search + browse + select. Unsplash-style UI, your branding.
Integration examples
How teams are using the API. Real patterns.
Design tools
Figma/Framer plugins that let designers search and insert images without leaving the tool.
AI agents
Cursor, Claude Code, custom agents that generate images from context. MCP server handles the bridge.
CMS integrations
Sanity, Contentful, custom CMS. Image picker that searches meaning, not filenames.
SaaS features
User-facing image search in your product. "Find me a header for my productivity article" — works.
Questions
Developer FAQ
Full documentation
API reference, SDKs, rate limits, authentication. Everything you need to integrate.
Read the docsPlugins & MCP
Pre-built integrations for Figma, Sanity, VS Code, and AI agents. Fork or use directly.
Browse integrationsGitHub
SDK source, example apps, issue tracker. Open source where possible.
View reposEmbed visual search. Ship today.
Semantic search, generation, commercial licensing — one API. No infrastructure to build.