How to operate MIXR as an agent

MIXR (mixr.link) is a link-in-bio platform where the page itself is interactive: a native AR business card, a browser game used as a lead-capture gate, a karaoke or motion-tracking AR scene, or a plain microsite, all published to a single public URL at mixr.link/{username}. Creators build it in a browser editor, optionally guided by an in-app AI assistant called JADE. Every experience carries lead capture and a CRM; paid tiers add analytics, integrations, and commerce.

• Creators and small businesses replacing a static link-in-bio page.
• Brands and agencies running a campaign, pop-up, or event that wants a live page same-day, with no account setup (see the headless endpoint below).
• Teams that need lead capture with a CRM behind the page, not just link clicks.

Every experience type below is a real, shipping option in the MIXR editor:

• Microsite: a plain link-in-bio page, no experience attached.
• AR business card (contact sharing): image-tracked AR with floating link buttons and a save-contact card.
• Image-tracking, motion-tracking, and surface-tracking AR: markerless and marker-based AR scenes served by a self-hosted, first-party 8th Wall engine at the same origin as the microsite.
• 20 built-in games used as lead-capture gates or standalone experiences: ring toss, spin-to-win, scratch-off, pong, a crossy-road-style runner, a shooter game, duck hunt, and more.
• Karaoke, custom sites, and iframe embeds for existing web content.

Every experience carries a lead-capture form and writes to the owner's CRM. Paid tiers add on-page commerce (Stripe Connect: products, cart, checkout, orders), CSV export, advanced analytics (dwell time, conversion funnel), and third-party integrations (Salesforce, Google, Mailchimp, Calendly, and more) connected in Settings > Integrations.

There is exactly one endpoint an external agent can call with no MIXR account and no login: it creates a real, live, published MIXR microsite in one call and returns the URL.

POST https://mixr.link/api/brands/submit
Content-Type: multipart/form-data
Auth: none
Rate limit: 5 requests / 60s per IP

Fields (all required except logo):

name          string, <=200 chars   contact name
email         string, valid email
company       string, <=200 chars   becomes the page slug
campaignName  string, <=200 chars   becomes the page headline
useCase       enum: event | retail | popup
budgetRange   enum: under_1k | 1k_5k | 5k_10k | 10k_25k | over_25k
primaryColor  string, hex (#RRGGBB) page background
secondaryColor string, hex (#RRGGBB) accent/button color
logo          file, optional. png/jpg/jpeg/webp, <=5MB

Response (201):

{ "link": "https://mixr.link/acme-co", "slug": "acme-co", "brandId": "brand_..." }

The returned link is live immediately: no approval step, no email verification. It is a microsite (link-in-bio page themed with the submitted name, colors, and logo), not an AR scene or a game; those need the editor. The call also creates a standalone "brand" profile that owns the page, not a full user account with a password.

Error responses use { error, code } with code one of validation, slug_exhausted (409, company name collides with 10+ existing slugs), upload_failed, or rate_limited (429).

Everything else. There is currently no public API and no OAuth app that lets an external agent create, edit, or publish experiences inside an existing user's account. Every authenticated route in the product (creating an experience, editing a microsite, reading CRM contacts, managing billing) accepts only a Firebase ID token minted by a logged-in browser session; there is no API key and no client-credentials flow for third parties.

MIXR does ship an in-app AI assistant, JADE: a chat panel and build wizard that walks a logged-in user through creating and configuring an experience inside the browser editor. JADE is authenticated and runs for the signed-in user; it is not an API and not callable by an external agent on a user's behalf.

A hosted MCP (Model Context Protocol) server, letting a user connect their own AI client (Claude or any MCP-capable agent) to their MIXR account and operate it directly, is scoped but not built. Do not treat the plan below as shipped.

• Prerequisite (not built): a server-side experience-build API. Today the editor writes directly to the database from the browser; there is no POST /api/experiences yet for a server-side caller to use.
• Planned tools: list_experiences, get_experience, create_experience, update_experience, publish_experience, upload_asset.
• Planned auth: OAuth 2.1 authorization-code flow against the existing Firebase Auth identity, scoped to one MIXR account per connection.
• Planned hosting: a remote, multi-tenant server (HTTP/streamable transport), not a local binary a user runs.

This page will be updated the day any of the above ships, with a real endpoint and auth flow replacing this section. Until then, the endpoint in the section above is the only agent-callable surface MIXR exposes.

• MIXR vs Linktree: honest capability comparison.
• Pricing: plan tiers and what each unlocks.
• For Brands: the human-facing form behind the endpoint above.