Obly
Asset libraryUse casesStylesLicenseRequest
Home/Request

Request loop

Request the object you could not find.

The MVP catalog is intentionally narrow. Search misses, refinement needs, and repeated use-case requests should become the signal for what Obly creates next.

Search current catalogCheck license status
SignalSearch gaps and refinements
QueueMVP-3 demand candidates
ScopeObject assets, not full scenes

Catalog links

Relevant public previews

Open the watermarked detail page first, then use the request path when the catalog is close but not exact.

Library
Refinement Controls thumbnail

Refinement Controls

Watermarked clean 3D refinement controls for adjustment controls visuals.

View preview
Agent Task Queue thumbnail

Agent Task Queue

Watermarked clean 3D agent task queue for agent workflow visuals.

View preview
Search Result Cluster thumbnail

Search Result Cluster

Watermarked clean 3D search result cluster for search results visuals.

View preview
Design Review Loupe thumbnail

Design Review Loupe

Watermarked clean 3D magnifier for review visuals.

View preview
Experiment Lab thumbnail

Experiment Lab

Watermarked clean 3D experiment lab for testing workflow visuals.

View preview
Email Campaign Stack thumbnail

Email Campaign Stack

Watermarked clean 3D email campaign stack for newsletter visuals.

View preview

What to request

A good request names the deliverable, object concept, style direction, and placement constraint. This is more useful than a broad image prompt.

  • Example: a clean 3D empty-state object for a failed billing screen.
  • Example: a premium landing page object with more empty space on the left.
  • Example: a darker dashboard-friendly variant of an existing analytics object.

How requests affect the catalog

In MVP-3, no-result searches and refinement choices are planned to become generation queue inputs with demand scoring.

  • Repeated requests can prioritize a new object candidate.
  • Specific placement constraints help avoid one-off assets that are hard to reuse.
  • License and download eligibility still need the MVP-1/MVP-2 layers before originals ship.

FAQ

Questions this route should answer

Is there a live request form?

Not yet. This page defines the public request path and points users back to catalog search while the generation queue is being connected.

Can I request brand or character lookalikes?

No. Obly should prioritize reusable business and product objects and avoid trademark, character, or near-copy requests.

Related routes

Continue through crawlable pages

Landing page objectsStart from a high-intent use case before asking for variants.App empty state objectsNarrow request language for product UI states.