api.blu.luxe200 OK

GET /v1/creators
{ data: { list: […] },
  hasMore: true }

26 endpoints · cursor pagination

Tracking links

IG Reels+19 fans

212 clicks · this week

ClaudeMCP ✓

▸ blu · transactions

“This week: $12,480 — +18%.”

One bill−30%

CRM + API + MCP included. vs Infloww, every month.

One platform · one bill

OnlyFans API + CRM + MCP.i

Take your agency to the next level — your way.

The data API, the agency CRM and the AI — in one platform, one price. Run it from Claude, from the API or from the CRM.

Start free See what's live today

Works withClaudeChatGPTManus

26

documented API endpoints

3

AI assistants via MCP

−30%

vs Infloww — API included

<24h

full agency migration

[ THE PRODUCT ]

This is what you actually run

Not just an API — the full agency cockpit. Every number below also comes back through the API and your AI.

app.blu.luxe/managementSample data

Overview · Last 30 daysLive

Revenue · 30d

$48,320+18%

Active fans

2,847+6%

Active chatters

7+1

Refund rate

1.2%−0.4%

Daily revenuelast 14 days

Top creators

Valentina R.$12,480

Sofía M.$9,140

Camila T.$7,320

Luna B.$5,010

Live activity

@valentinaPPV purchase$42.00

@sofia_mNew subscriber$9.99

@camilaTip — Sophie closed$120.00

@luna.bRenewal$14.99

Ask your AI about this

On this page:Live = you can use it todayBuilding = we're building it — not here yet

[ THE COMBO ]

Stop paying for two tools

Today agencies pay Infloww for the CRM and a separate service for the OnlyFans API. BLU is both — plus AI — in one.

[ Like OnlyFansAPI.com ]

The OnlyFans API + MCP

Your data by API
Claude · ChatGPT · Manus (MCP)
Keys, scopes, security

[ Like Infloww ]

The agency CRM

Chatting, mass DMs, scripts
Earnings & team management
The full day-to-day ops

[ Only BLU ]

+ AI built in

Sophie — your AI seller
Ask your AI anything about the agency
All of it, one price

Infloww + OnlyFansAPI.com = two bills. BLU = one.

The other way

A CRM (Infloww)bill #1

A separate OnlyFans APIbill #2

AI that sellsnot included

→

The BLU way

CRM + API + MCP + Sophieone bill

−30%vs just the CRM — and the API's included

You save paying for an entire second platform.

[ LIVE TODAY ]

What you can use right now

Everything in this section is running in production today. Green dot = real.

The MCP — Claude, ChatGPT, Manusi

Live

Plug BLU into your assistant and it answers from your real, live numbers.

The read API — 26 endpointsi

Live

Creators, transactions, refunds, sales records, fan analytics, invoices — every number.

Sophie — AI seller in the CRMi

Live

An AI trained on your style, working chats inside the platform. Infloww doesn't have this.

Tracking links & attributioni

Live

Links, daily clicks, subscribers and which fans came from each campaign.

Per-chatter statsi

Live

Sales and chatting stats per employee, plus reassigned-sales logs.

Scoped keys + full docsi

Live

Keys scoped by data type, creator and PII, with an IP allowlist. Full docs + changelog.

Claude — connected to BLU via MCPSample data

A real MCP session looks like this — with your numbers instead of the sample ones.

ClaudeLive

“Build my agency's weekly report.”

via MCP, on your real data

ChatGPTLive

“Which creator grew the most this month?”

via MCP, on your real data

ManusLive

“Check this month's refunds — anything odd?”

via MCP, on your real data

Also ask it:“How many refunds this month?”“Which fans spend the most?”“Pull September's invoice.”“Which mass message performed best?”“Which creator grew most in profile visits?”“Which sales got reassigned today?”

Dev? The raw API call lives in the docs →

[ WHAT YOU CAN DO ]

Explore what BLU unlocks

Four things agencies run on BLU today — not someday.

Run the agency from your AI

Live

Connect Claude, ChatGPT or Manus by MCP and ask anything — it answers from your live numbers.

“How much did we bill this week?”
“Which chatter closed the most?”
No dashboards, no scraping.

See who's really working

Live

Per-chatter sales and chat stats, plus reassigned-sales logs — the whole team, transparent.

Spot a slow shift the day it happens.
Credit each sale to the right person.
No more “trust me, we're on it.”

Know which traffic pays

Live

Tracking links, daily clicks and which campaign brought each paying fan — real attribution.

Stop guessing where fans come from.
Put budget where it converts.
By creator and by link.

Build your own tools

Live

Clean read API, cursor pagination, OpenAPI spec — plug BLU into your own dashboards and reports.

26 documented endpoints.
curl, JavaScript, Python examples.
Your AI can build it for you.

[ SECURITY & INFRA ]

Built so a leaked key can't hurt you

The cleanest key model in the business — because BLU reads, it doesn't act on your account.

Scoped keys

Each key is limited by data type, creator and PII. A leaked key only touches what you allowed.

IP allowlist

Keys only work from the IPs you approve — not from anywhere on the internet.

Read-only by design

The API reads your numbers; it can't act on your account. Nothing can be moved or deleted through it.

Clean errors + request IDs

Clear 401/403/429/503 with Retry-After, and an x-request-id on every call for support.

Full docs + OpenAPI

Documented endpoints generated from the live service, plus /openapi.json and a changelog.

Revoke anytime

Rotate or kill a key instantly from the BLU app — keys can expire or be revoked.

For the owner

Revenue, refunds and invoices from your phone — you ask your AI, no dashboard needed.

For the manager

Who's selling, which campaign works and which chatter needs help — one question.

For the chat team

Sophie works chats inside the CRM, and per-chatter stats keep the credit transparent.

Coming soon · 8 building

What we're building — not here yet

Nothing in this section works today. We say it out loud instead of dressing it up — when one ships, its tag turns green.

Write API & automations

Building

Send messages and act on your account by API — today BLU reads, it doesn't write.

Webhooks (live events)

Building

BLU calls YOU the moment a sale or fan event happens.

Official SDKs (JS/Python)

Building

Install a library instead of writing raw HTTP calls.

No-code (Zapier, Make, n8n)

Building

Automations without writing a single line of code.

Interactive playground

Building

Try every endpoint from the browser before writing code.

Smart Links (Meta/TikTok pixel)

Building

Feed conversions back to your ad pixels to cut ad costs.

Fansly coverage

Building

The same data API, for Fansly accounts too.

Sandbox & test keys

Building

A safe fake account to build against before going live.

[ HONESTLY COMPARED ]

BLU vs Infloww vs OnlyFansAPI.com

Where a competitor beats us today, we say so — hover the 'i'.

Capability	BLU	Infloww	OnlyFansAPI.com
CRM & operations (we win)
Full agency CRMi
AI seller inside the CRM (Sophie)
Turnkey migration <24h
Everything for one pricei
AI / MCP
MCP: Claude / ChatGPT / Manus
AI that answers from live data
Data coverage
Transactions, refunds, sales records
Tracking links & attribution
Per-chatter stats
Fansly coverage
API infrastructure (they win today)
Endpoint coveragei
Write API (actions)
Webhooks (live events)
Playground + SDKs
No-code (Zapier/Make/n8n)
Smart Links (Meta/TikTok pixel)
Security
Scoped keys + IP allowlist
Read-only (can't act on your account)i

Full API-to-API breakdown on /developers.

[ PRICING ]

30% below Infloww — and the API's included.

Same simple price we've always had — per creator you connect, 30% under the market. Except now the whole OnlyFans API and MCP come with it, at no extra charge. Everyone else charges that as a second bill on top of their CRM. You save paying for an entire second platform.

The CRM — 30% below Infloww
The OnlyFans API + MCP, included
Sophie, your AI seller
No second bill for the API

Start free Talk to us

Claude, ChatGPT and Manus are trademarks of their respective owners. BLU connects to them via MCP.

OnlyFans API + CRM + MCP.iMCP (Model Context Protocol) is the open standard that lets AI assistants like Claude or ChatGPT use your BLU data as live tools. In short: your agency, talking to your AI.

This is what you actually run

Stop paying for two tools

The OnlyFans API + MCP

The agency CRM

+ AI built in

What you can use right now

The MCP — Claude, ChatGPT, ManusiMCP (Model Context Protocol) lets an AI assistant use your live data directly as tools — the same AI integrations OnlyFansAPI.com offers.

The read API — 26 endpointsiDocumented endpoints generated from the live service, so the docs can never be out of date.

Sophie — AI seller in the CRMiBLU's AI lives inside the CRM and sells — not a bolt-on chatbot.

Tracking links & attributioniKnow which traffic source actually brought paying fans — real attribution, by API.

Per-chatter statsiSee who actually closes the money across your team — down to each chatter.

Scoped keys + full docsiA leaked key can only touch what you allowed — the cleanest key model in the business.

Explore what BLU unlocks

Run the agency from your AI

See who's really working

Know which traffic pays

Build your own tools

Built so a leaked key can't hurt you

Scoped keys

IP allowlist

Read-only by design

Clean errors + request IDs

Full docs + OpenAPI

Revoke anytime

For the owner

For the manager

For the chat team

What we're building — not here yet

Write API & automations

Webhooks (live events)

Official SDKs (JS/Python)

No-code (Zapier, Make, n8n)

Interactive playground

Smart Links (Meta/TikTok pixel)

Fansly coverage

Sandbox & test keys

BLU vs Infloww vs OnlyFansAPI.com

30% below Infloww — and the API's included.

OnlyFans API + CRM + MCP.i

The MCP — Claude, ChatGPT, Manusi

The read API — 26 endpointsi

Sophie — AI seller in the CRMi

Tracking links & attributioni

Per-chatter statsi

Scoped keys + full docsi