Use Cults from Claude
Add the Cults connection to a Space that runs Claude, then use it from every channel in that Space.
ConnectorCults
Cults integration for Claude and Codex
Create a Cults connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
CategoryCommerce & Payments
Use Cults from Codex
Add the Cults connection to a Space that runs Codex, then use it from every channel in that Space.
Use Cults from Sidekick
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
Commerce & Payments
What the Cults connector can do
Cults is a marketplace where designers sell 3D printable models, with metadata like titles, tags, and creator profiles queryable through GraphQL. With a Cults connection in type.com, the agent can run a GraphQL query to browse or search designs, check whether a sharing origin has been approved, or build a one-click share link for a new file, so a creator or community team can manage marketplace presence from a thread.
One connection, many Spaces
Connect Cults once, then decide which Spaces can use it in threads, skills, automations, and coding work.
What teams do with Cults in type.com
Research designs in a category
Ask the agent to query Cults for popular designs in a given category to spot trends before publishing something new.
Query Cults for the top designs in the miniatures category and summarize what's trending.
Check if a sharing origin is approved
Have the agent check approved origins before relying on the Share on Create feature for a new integration.
Check whether our site's origin is approved for Cults' Share on Create feature.
Generate a share link for a new file
Get the agent to build a pre-filled share URL so a creator can push a new 3D file to Cults in one click.
Generate a Cults share link for this new STL file so our designer can publish it in one click.
Representative actions
- Get Approved Origins
Checks a Cults creation page for sharing origin information that support has approved.
- Cults GraphQL POST
Runs GraphQL queries or mutations to browse designs, profiles, or marketplace data.
- Share on Create (FR)
Builds a one-click share URL that pre-fills a 3D file on the Cults creation page.
Connection
API and auth details
Cults provides a GraphQL API for the Cults3D marketplace. Public docs note that files remain hosted by Cults, while metadata such as photos, titles, descriptions, tags, users, designs, sales-oriented analytics, and marketplace discovery data can be queried programmatically.
- Source
- type.com catalog metadata
- Auth schemes
- API key
- Official site
- https://cults3d.com/
Source links
FAQ
Questions people ask before connecting Cults
Can Claude query the Cults marketplace from type.com?
Yes. Once a Cults connection is shared with a Space, the agent can run marketplace queries, check sharing origins, and build share links in any thread, visible to the team.
How does type.com authenticate with Cults?
Cults uses an API key. An admin adds it once when creating the connection and chooses which Spaces can use it.
Can Cults marketplace research run on a schedule?
Yes. A Cults prompt can become a type.com automation, such as a weekly scan of trending designs in a category, posted to a channel.
Is this the same as a Cults MCP server?
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
More commerce & payments connectors
All Commerce & Payments integrationsConnect Shipday to Claude in type.com to add drivers, check delivery availability and estimates, and edit existing orders.
Connect Shipengine to Claude in type.com to tag shipments, batch orders for labels, and cancel shipments from a shared team thread.
Connect Shippo to Claude in type.com to validate addresses, pull live carrier rates, and prep customs items from a shared thread.
Connect Skyfire to Claude in type.com to issue identity and payment tokens for agent transactions, and browse services from a thread.