Incantory
Sign in

Content licenses

The licenses prompts on Incantory carry, what they let you do, attribution requirements, fork rules, imported collections and removal requests.

Every prompt on Incantory carries an SPDX license, shown on its page and returned by the API as licenseSpdx. The full texts are on the licenses page.

Licenses for prompts published here

When you create or fork a prompt you pick one of:

LicenseSPDXIn short
Creative Commons Attribution 4.0 (default)CC-BY-4.0Use, change and share, including commercially, with credit
Creative Commons Attribution-ShareAlike 4.0CC-BY-SA-4.0As CC-BY, and derivatives must use the same license
Creative Commons Zero 1.0CC0-1.0Public domain dedication; no conditions
MITMITPermissive; keep the copyright and license notice
Apache 2.0Apache-2.0Permissive, with a patent grant; keep notices and the NOTICE file

All-rights-reserved is not offered: forking and remixing are the point of the registry. The default is CC-BY-4.0 because it keeps credit flowing back to the author while allowing forks, remixes and commercial use.

Using prompts you fetch

What you may do with a prompt is set by its license, whether you read it on the site, through the API, an SDK, the CLI or MCP.

  • Attribution (CC-BY, CC-BY-SA, MIT, Apache): credit the author. Every prompt page, the API and exports carry the attribution chain and, for CC-BY content, the credit line to use.
  • Share-alike (CC-BY-SA): if you publish a derivative, it must use the same license.
  • Notices (MIT, Apache): keep the copyright and license text with copies; for Apache content keep the NOTICE contents, which the licenses page collects per source.

Rendering a prompt and sending the result to a model is using it; publishing a modified copy is making a derivative.

Forks

  • A fork keeps its parent in the attribution chain: original source, then each fork parent, then the current author. The same chain appears on the page, in the JSON-LD isBasedOn field, the API and exports.
  • A fork of a share-alike prompt must stay share-alike. The UI and API refuse a license that would break the parent's terms (license_not_allowed).

Imported collections

Part of the registry is imported from openly licensed collections on GitHub and elsewhere. Imported prompts:

  • keep their upstream license (CC0, CC-BY, MIT, Apache-2.0 and similar);
  • show the source repository pinned to a commit, the original author, whether the text was modified, and when it was last synced;
  • are listed per source at /sources/{source}.

If an imported prompt is yours, use "Is this yours? Claim it" on its page: a matching GitHub login is approved automatically, and ownership moves to you with the attribution kept.

Removal requests

We honour removal requests whatever the license, including for CC0 content. Use the removal request form; copyright notices can also go through the DMCA process at /dmca.