Skip to content
MirrorFirm

What licence questions should we resolve before using generated material in an agent pipeline?

Buyers should clarify permitted uses across training, evaluation, derived artifacts and redistribution, including how rights apply when content is accessed through different delivery channels.

**Does access to a sample establish permission for every downstream use?**

Do not assume it does. Ask which uses the applicable licence permits, including internal evaluation, model training, fine-tuning and incorporation into development fixtures. The scope should match your intended pipeline.

**What about artifacts produced during agent runs?**

Clarify treatment of derived task variants, execution traces, screenshots, embeddings and reports containing record excerpts. A team may need to share these with contractors or infrastructure providers even when the original dataset stays in its own storage.

**Does the delivery channel change the rights?**

Ask whether the same permissions apply to website content, downloadable exports and content retrieved through MirrorFirm's public MCP server. Technical accessibility does not by itself answer whether redistribution or inclusion in another product is permitted.

**What should we request before a pilot?**

Describe the intended users, storage locations, transformations and sharing paths, then ask for the relevant licence scope and any limits. Also clarify what happens to retained copies and derived artifacts when access ends. These are questions to resolve with MirrorFirm, not assumed contract terms or a claim that any particular permission is currently offered.

Match the requested licence to the way your team will actually store, transform and share generated material.

Audience:
Agent developers
Content type:
FAQ
Buyer question:
Scope and getting started

Content release: r-a220eb6e099b243b

More on Ledger adjustment