Cults
for LuumenAI

Cults is a digital marketplace for 3D printing models, offering a platform for designers to share and sell their creations.

Operate Cults from the same conversation as the hosts it runs on. Check jobs, queues, and interfaces without a second console; run diagnostic reports; and restart or update with the change previewed, approved, and logged.

The Cults toolbox

3 tools: 2 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadGet Approved OriginsInspects the Cults creation page to detect any sharing origin information.
  • ReadShare on Create (FR)Generate a one-click share URL for publishing a 3D file to Cults (French locale).
  • WriteCults GraphQL POSTExecute GraphQL queries and mutations against the Cults3D API. Approval by default

Questions

How does LuumenAI connect to Cults?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Cults on its own?

Read actions answer immediately. Anything that writes — cults graphql post — is shown as a plan and requires approval by default. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Cults — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put Cults to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.