API Usage Policy

MultiMuse API Usage Policy

Last updated: June 3, 2026

Provider: TeaHouse Media (“we”, “us”, “our”)

Applies to: The public HTTP API at https://api.multimuse.app and API keys issued through MultiMuse (/api generate and related Discord commands).

This policy is part of how we keep MultiMuse free for the community. By creating or using an API key, you agree to this policy in addition to our Terms of Service.

For technical details, see the HTTP API reference.

Summary

MultiMuse and its core features are free. The API exists so members and server communities can build personal, server, and hobby tools — not so third parties can sell access to MultiMuse functionality or ship a paid replacement for our product.

You may not charge users for access to MultiMuse API capabilities or operate a paid product whose main value is MultiMuse features delivered through the API.

You may build free helpers (bots, trackers, scripts) for yourself or your server, as long as you follow this policy and the API reference.

What the API is for

The API is intended for:

  • Personal automation — Your own muses, tracking, and workflows

  • Server and community tools — Free bots or utilities for a Discord server you help run

  • Accessibility and convenience — Scripts, desktop helpers, or private dashboards for people who already use MultiMuse

  • Good-faith integrations — Tools that clearly add to Discord roleplay without replacing paid MultiMuse features (there are none today — the bot stays free)

The API is not a license to build a commercial platform on top of MultiMuse.

Prohibited uses

You must not use the API (directly or through an app, site, or bot you operate) to do any of the following:

Paid access to API features

  • Charge money, subscriptions, tips-as-access, paywalls, or “premium tiers” for using MultiMuse via your integration (for example paid API keys, paid dashboards, or paid “pro” API features)

  • Bundle API access into a paid product where MultiMuse functionality is a material selling point

  • Operate a marketplace or hosting service that resells or sublicenses API access to MultiMuse

Competing paid front-ends

  • Ship a paid website or app that reproduces core MultiMuse experiences (muse management, cards, proxy posting, thread tracking, scene tools) primarily by calling our API, when MultiMuse itself is free

  • Present your product as an official MultiMuse app, dashboard, or replacement without our written permission

  • Use the API to drive a commercial SaaS whose primary purpose is muse/proxy/RP management powered by MultiMuse

Abuse and circumvention

  • Scrape, bulk-harvest, or systematically export other users’ data beyond normal integration needs

  • Share or publish API keys; embed keys in public client-side code

  • Circumvent rate limits, consent, private-muse rules, or authentication

  • Use the API in any way that violates Discord’s Terms of Service or Community Guidelines

  • Use the API for unlawful, harassing, or deceptive purposes

If you are unsure whether a project crosses these lines, contact us before you launch or charge anyone.

Allowed uses (examples)

These are generally allowed when offered without charging for MultiMuse API access as described above:

  • A free Discord bot for your RP server that tracks threads or posts as muses via the API

  • A private script or desktop tool only you or your friends use

  • A free open-source utility published with clear “unofficial / not affiliated with TeaHouse Media” labeling

  • Server-specific dashboards visible only to admins of that community, with no fee for API-powered features

You may still run ads or sell unrelated goods on your server or site (for example merch, commissions, or event tickets) as long as users are not paying you to unlock MultiMuse API features or a paid MultiMuse-like client.

Commercial and partnership requests

If you want to:

  • Charge for a product that uses the API in any way

  • Offer a hosted or white-label MultiMuse experience

  • Use MultiMuse branding in a commercial product

  • Exceed normal API volume for a business

you must obtain prior written permission from TeaHouse Media. Without that permission, commercial use of the API is not allowed.

Contact: use the contact method listed on multimuse.app (Terms of Service / support channels).

Branding and attribution

  • Do not imply that your project is official, endorsed, or operated by TeaHouse Media or MultiMuse unless we agree in writing.

  • We recommend stating clearly: “Unofficial tool; not affiliated with MultiMuse or TeaHouse Media.”

  • Do not use our logos, bot avatar, or trademarks in a way that suggests ownership or partnership without permission.

Privacy and consent

API use must respect:

  • Mutation consent — Do not trick users into approving keys; explain what your tool does

  • Private muses — Do not attempt to expose private muses through workarounds

  • Other users’ data — Only collect and display data needed for your stated, allowed purpose

Our Privacy Policy describes how we handle data on our services. You are responsible for your own tool’s privacy practices if you store or display user data outside Discord.

Enforcement

We may, at our sole discretion:

  • Revoke or disable API keys

  • Block IP addresses or integrations that abuse the API

  • Suspend access to MultiMuse or related services

  • Update technical limits (rate limits, authentication, scope of endpoints)

Violations may also be addressed under the general Restrictions on Use in our Terms of Service.

We are not obligated to provide notice before enforcement in cases of clear abuse, fraud, or risk to users or infrastructure.

Changes

We may update this policy from time to time. The “Last updated” date at the top will change when we do. Continued use of the API after changes means you accept the updated policy.

Material restrictions will also be reflected in the HTTP API reference where relevant.

Relationship to other documents

If this policy and the API reference conflict on commercial or licensing questions, this policy controls. If they conflict on technical behavior (rate limits, auth), the API reference and live API behavior control.

Quick checklist for integrators

Before you ship:

  • My tool is free for end users regarding MultiMuse API features (no paywall for API-powered muse/tracking/post features)

  • I am not selling a paid replacement dashboard or “MultiMuse Pro” built on the API

  • I label the project unofficial and do not imply TeaHouse endorsement

  • I keep API keys secret and server-side where possible

  • I respect consent, private muses, and rate limits

  • If I want to charge money or run a business on top of this API, I have written permission