Status: Accepted for the checked-in default; each rejection names what would
reopen it (2026-09-15)
Date: 2026-09-15
Owner: @GreyChimp
Authors: Isis Runtime Engineering (tracker item T.22.09)
Related: ADR-0008 (capability ownership, provider boundary); tracker
ISIS_CHROMA_RUNPOD_MVP_TODOS_2026-09-11.md T.22.01 (lane policy), T.22.03 (API
lane), T.19–T.21 (agent transports and their isolation rules); Task 14.2 owner
attestation
docs/audits/eve-sota-provider-subprocessor-review/owner-attestations/2026-09-15-isis-hosted-media.json
1. Context#
Meshy is an optional hosted lane in the Isis generation API. It is operator only (the owner's final decision), SFW only, never a benchmark or training input, and bounded by the Meshy credit ledger's daily budget. Each output is stored byte for byte with provenance. The owner attestation admits Meshy for exactly that path: the Isis generation API, the operator tenant, and operator-owned non-personal material.
Meshy also offers channels that let an agent or a DCC tool reach its service directly. T.22.09 asks for each to be adopted or rejected against T.19–T.21's rules, with a recorded reason. Those rules require that credentials never sit in an agent's context, that spend is capped, and that no bridge bypasses the cost, content-policy, artifact or provenance gates ("Neither bridge gets to bypass the existing cost, content-policy, artifact or provenance gates", tracker §Execution contract).
Sources read 2026-09-15: https://docs.meshy.ai/llms.txt, https://docs.meshy.ai/api/ai.md, https://www.meshy.ai/integrations, https://www.meshy.ai/integrations/blender, https://www.meshy.ai/integrations/unity, https://docs.meshy.ai/en/unity-plugin/introduction, https://github.com/meshy-dev/meshy-unity-plugin and Meshy terms of use §2.6.
2. The rule every channel is measured against#
An agent reaches Meshy only through the Isis generation API's meshy:*
workflows, exposed as T.08's provider-independent tools and called with an
operator-scoped Isis credential. That path is the only one that runs all of the
following:
- T.22.01's policy at submit, every chain step, retry and execution;
- the Meshy ledger's daily budget, checked at submit and again before create;
- task-id resume, so a retry never pays twice;
- the output store and provenance record;
- T.01.05 lineage;
- the Task 14.2 source gate.
A channel that holds MESHY_API_KEY itself skips every one of them.
3. Decisions#
3.1 Meshy MCP server (@meshy-ai/meshy-mcp-server, github.com/meshy-dev/meshy-mcp-server)#
Rejected.
- The key sits in the agent's context. The server reads
MESHY_API_KEYfrom the MCP client's environment (claude mcp add meshy --env MESHY_API_KEY=… -- npx -y @meshy-ai/meshy-mcp-server), so the agent process holds the credential, contrary to the T.19–T.21 rule. - Spend is uncapped. "Every MCP tool call maps to a single REST call and consumes credits at the exact same rate." The Isis Meshy ledger never sees those calls, so the daily budget does not bound them.
- Policy and provenance are bypassed. The server's tools (text, image and multi-image to 3D, refine, remesh, retexture, rig, animate, text and image to image, task management, workspace listing) create tasks without the operator, SFW-rating, prohibited-use or material-origin checks. Outputs land outside the output store and provenance.
- Owner-excluded tools are exposed. Its printing tools ("send to slicer, analyze printability, process multi-color") are a group the owner removed on 2026-09-15.
- The install floats.
npx -ypins no version, which fails T.01's admission rule against floating pins.
Reopens when: Isis ships its own MCP facade over the generation API's
meshy:* tools, using the Isis credential and never the Meshy key. That facade
is a T.19–T.21 transport decision, not an adoption of this server.
3.2 add-mcp CLI and the meshy-3d-agent skill pack (npx skills add meshy-dev/meshy-3d-agent)#
Rejected, for the same reasons as §3.1. The CLI auto-detects clients to install the MCP server into, and the skill pack drives agents through that server. Both put the Meshy key in agent configuration and install unpinned code.
Reopens when: §3.1 reopens and the pack is pinned by commit and re-pointed at the Isis facade.
3.3 A standalone Meshy CLI#
Not available. Neither llms.txt nor the AI integration page documents a
Meshy command-line client for the generation API on 2026-09-15. The only CLI
named is add-mcp (§3.2). Nothing is adopted. A CLI that appears later is
judged by §2.
3.4 Meshy for Blender (official plugin, DCC Bridge)#
Rejected as an Isis channel.
- The bridge feeds from the web workspace, not the API. It "runs a small local service on port 5326 and only accepts connections from meshy.ai" and pushes models from a person's Meshy web workspace into Blender. It requires Pro or above. Work done that way is Meshy web usage under the owner's account: it produces no Isis job, credit booking, provenance or lineage.
- Excluded tools ship with it. The plugin bundles 3D-print preparation tools, the group the owner excluded.
- Bridge assets escape the output store. In a live-session setting (T.20) the bridge would be a second path into the scene that bypasses the output store, which the execution contract forbids.
Isis route instead: lane outputs (GLB and FBX in the output store, recorded by sha256) are imported through T.20's pinned headless Blender runner.
Reopens when: never as a pipeline channel. A person may use the plugin manually in their own Meshy account, outside Isis.
3.5 Meshy for Unity (official plugin, Bridge Edition, github.com/meshy-dev/meshy-unity-plugin)#
Rejected as an Isis channel, on §3.4's grounds. It is a one-click import from the Meshy web workspace into the Unity Editor through the same local Bridge. It does not use the Isis credential, ledger, policy or output store.
Isis route instead: T.16.04 and T.19 import lane outputs from the output store into Unity through the Unity CLI and Pipeline.
Reopens when: never as a pipeline channel; manual use stays outside Isis.
4. Consequences#
- The checked-in picture does not change: one Meshy client
(
@isis/ai-providers), one lane (the generation API), one policy, one ledger. - Terms §2.6 (vi) forbids shared accounts. Handing the one Meshy key to several agent clients would amount to sharing it, which this record also avoids.
- T.21's acceptance matrix lists these channels as rejected with this ADR as the reason, so none of them counts toward agent-tool qualification.