Product · · 5 min read · kriyaworks
Why we built Kriops
Agents are becoming buyers. The marketplace thesis behind Kriops: creative assets packaged the way software is packaged — versioned, documented, licensed, and installable from inside your agent.
Every creative marketplace on the internet was designed for the same customer: a human being, browsing thumbnails, on a Tuesday. That customer still exists. But increasingly the thing doing the browsing is an agent — a coding assistant resolving a task, mid-run, that needs a template, a UI section, a prompt pack or a skill right now. And for that customer, the entire existing aisle is unusable.
The thesis
An agent can't squint at a preview image. It needs assets that behave like software: a versioned payload, real documentation, an explicit license, an install path it can execute. Almost nothing sold on today's marketplaces clears that bar — files arrive as zips of mystery, licensing lives in a FAQ nobody can parse, and 'installation' means a human dragging folders around. Kriops is our bet that the next marketplace is built agent-first: every listing packaged the way the studio packages its own production work, ready to be evaluated and pulled by a person or a machine with equal ease.
What sits on the shelves
- Designs, brand kits and social assets — with source files, not just exports.
- Premium prompts and prompt bundles — versioned production text, not one-liners.
- Templates and UI sections for the stacks people actually ship with.
- 3D elements ready to drop into real scenes.
- Claude Code skills, agents and MCP servers — tooling as merchandise.
The common thread isn't a file type — it's a standard of packaging. Documentation, versioning, license and attribution travel inside every payload. If an asset can't be picked up cold and used without a conversation, it isn't ready for the shelf.
The marketplace is an endpoint, not a tab
The part we care about most is the MCP connection. Connect Kriops to your agent and the catalog stops being a website you visit and becomes a capability your tools have — search from the editor, evaluate a listing mid-task, pull the payload without breaking flow. A browser tab is where work goes to pause; an endpoint is where it keeps moving. We built for the endpoint first and the tab second, which is roughly the opposite of everyone else's ordering.
Curated, honestly
The catalog is first-party for now: assets built and packaged by the studio, held to the same craft bar as this site. Seller accounts and creator uploads come later — that's the plan, plainly labeled as a plan, not dressed up as a feature. When creators do come aboard, the packaging standard is the deal: we would rather run a small shelf you can trust than a large feed you have to outguess. If the thesis is right, the agents will notice before the humans do.