Joint research model for surface cutting and UV unwrapping. It predicts mesh-edge seam probabilities with flow matching; public code, weights and production access are not yet established.
Flow matching on mesh-edge probabilities. A 28-block DiT uses width 1024, 16 attention heads and a 4096-wide SwiGLU feed-forward layer; local edge tokens attend to global shape features.Source for Architecture (opens in a new tab)
Endpoint pricing has not been collected. Check the provider for applicable rates.
Data & enterprise terms
No model-specific commercial access, retention or hosting policy verified; Meshy API terms are not assumed to govern this joint research model.
Caching
Caching can reuse earlier input processing. Availability, lifetime and billing depend on the endpoint. A cache hit still generates a new response.
01 / INITIAL INPUTProcess & retain
The system processes eligible input and retains reusable state.
02 / LATER REQUESTCheck available state
Reuse depends on matching input, session state and the cache policy.
03 / CACHE HITReuse & generate
Reusing state can reduce repeated work. Any charges follow the billing rules below.
SeamFlow research collaboration
Not verified
No model-specific prompt-cache contract or discounted cache rate documented.
How it works
Not collected
No model-specific prompt-cache contract or discounted cache rate documented.
Minimum reusable input
Not collected
No model-specific prompt-cache contract or discounted cache rate documented.
Lifetime & refresh
Not collected
No model-specific prompt-cache contract or discounted cache rate documented.
How to enable it
Not collected
No model-specific prompt-cache contract or discounted cache rate documented.
Usage fields
Not collected
No model-specific prompt-cache contract or discounted cache rate documented.
Billing rules
Not collected
No model-specific prompt-cache contract or discounted cache rate documented.
Limits & data boundaries
Not collected
No model-specific prompt-cache contract or discounted cache rate documented.
No verified cache rate for this endpoint. An empty rate is not a zero charge.
Caching reviewed 14 Oct 2026
What the measurements say
No benchmark observations have been added for this model. We do not turn a vendor description into a performance score.
Latency and throughput depend on the host, request size, reasoning settings and load. There is no measured speed or global usage figure in this record.
The record behind the model
Why it is included
The authors’ project page explicitly marks code and models as forthcoming. This record describes currently unreleased weights, not a permanently proprietary license. Recheck when the promised release appears. The project-page template license does not license model weights.