MemeFlow Connect REST API v1 · SDK v1.4.0 · AI & Search Discoverable

How MemeFlow works & how to integrate the MemeFlow API to monetize your platform content.

MemeFlow enables both individual creators and external software platforms to turn articles, breaking news, 48kHz studio audio (WAV/MP3), videos, PDFs, and ZIP archives into canonical Smart Links (/m/{slug}). Integrated partner platforms keep 100% of their own site's native ad revenue while earning 80% of net Google AdSense revenue (or a chosen application-specific revenue share) generated when users open, stream, or download content through MemeFlow Smart Links.

Open Developer Portal Ask MF AI Integration Architect

01. How Platform Double-Monetization Works

External platforms use MemeFlow as a secondary monetization and content delivery layer without losing their own site traffic.

STAGE 01 · YOUR PLATFORM

Keep 100% of Your Own Native Site Revenue

Users browse your website or app normally. When they click Download File, Listen in Studio Quality, Watch Clip, or Read Full Article, your backend calls the MemeFlow API.

STAGE 02 · MEMEFLOW SMART LINK (/m/{slug})

Sponsor Gate & Policy-Safe Content Viewer

MemeFlow returns a canonical Smart Link (/m/{slug}). Human visitors view the Sponsor Gate and proceed to /m/{slug}/view to download, stream, or read the content.

STAGE 03 · 80% REVENUE ATTRIBUTION

80% Net Google Ads Share + Browser Session Cleanup

MemeFlow attributes 80% of net Google AdSense revenue (or your application's negotiated percentage) to your Developer Ledger (20% platform service fee). Temporary partner content is delivered directly to the visitor's browser for the active session and automatically wiped when the visitor leaves or returns, with defensive cleanup for abandoned sessions.

02. Machine-Readable Specs for AI Agents & Search Engines

Building with Cursor, Claude, ChatGPT, Perplexity, or Windsurf? Point your AI coding agent directly to these public endpoints or copy the verified system prompt below.

llms.txt (AI Overview)

Concise LLM discovery index

/llms.txt

llms-full.txt (Full Spec)

Complete API & code reference

/llms-full.txt

openapi.json (OpenAPI 3.1)

Machine-readable REST schema

/openapi.json

developer-sdk.md

Markdown SDK & client guide

/developer-sdk.md

developer-sdk.json

JSON endpoint & scope contract

/developer-sdk.json

Copy-Paste Prompt for Cursor / Claude / ChatGPT / CopilotZero external dependencies

You are an expert full-stack engineer integrating the MemeFlow Connect API (v1) into our platform to monetize our content via MemeFlow Smart Links.
Use the following verified production specification:
- API Base URL: https://creator-connect-earn.lovable.app
- Auth Header: Authorization: Bearer <MEMEFLOW_API_KEY> (or x-api-key: <MEMEFLOW_API_KEY>)
- Idempotency Header: Idempotency-Key: <UUID-v4> on all POST requests
- Rate Limit: 120 requests/minute per API key (subject to endpoint-specific limits)
- Revenue Share: Partner platform keeps 100% of its own native site ad revenue + earns standard 80% (or negotiated application-specific percentage) of net Google AdSense revenue generated on MemeFlow Smart Links (/m/{slug} -> /m/{slug}/view).
- Browser-Local Ephemeral Delivery: POST /api/v1/posts/temporary (session-scoped browser-local delivery, zero MemeFlow Storage bloat, automatic cleanup on leave).
- Permanent Multi-File Posts: POST /api/v1/posts (supports articles, news, 48kHz/24-bit studio audio WAV/MP3, video, images, PDFs, ZIP archives).
- Partner Content Ingestion: POST /api/v1/partner/content (tracks partner_content_id and content_version).
- Webhooks: Verify x-memeflow-signature using HMAC-SHA256 with MEMEFLOW_WEBHOOK_SECRET.
- Machine-readable specs: https://creator-connect-earn.lovable.app/llms-full.txt and https://creator-connect-earn.lovable.app/openapi.json

03. Integration Code Examples

Zero-dependency implementations for TypeScript/Node.js, Python, cURL, and Webhook verification.

TYPESCRIPT INTEGRATION

// Zero-Dependency TypeScript / Node.js MemeFlow Partner Integration
export async function createMonetizedPartnerLink(params: {
  partnerContentId: string;
  title: string;
  caption?: string;
  actionType?: "view" | "download" | "listen";
  mode?: "temporary" | "permanent";
}) {
  const baseUrl = process.env.MEMEFLOW_API_BASE_URL || "https://creator-connect-earn.lovable.app";
  const apiKey = process.env.MEMEFLOW_API_KEY || "YOUR_MEMEFLOW_API_KEY";
  const endpoint =
    params.mode === "permanent" ? "/api/v1/posts" : "/api/v1/posts/temporary";

  const response = await fetch(`${baseUrl}${endpoint}`, {
    method: "POST",
    headers: {
      Authorization: `Bearer ${apiKey}`,
      "x-api-key": apiKey,
      "Content-Type": "application/json",
      "Idempotency-Key": crypto.randomUUID(),
    },
    body: JSON.stringify({
      application_id: process.env.MEMEFLOW_APPLICATION_ID || "universal",
      partner_content_id: params.partnerContentId,
      title: params.title,
      caption: params.caption || "",
      action_type: params.actionType || "download",
      storage_mode: params.mode || "temporary", // Browser-local delivery with zero MemeFlow storage bloat
      category: "Entertainment",
    }),
  });

  if (!response.ok) {
    throw new Error(`MemeFlow API Error (${response.status}): ${await response.text()}`);
  }

  // Returns { success: true, smart_link: "https://creator-connect-earn.lovable.app/m/{slug}", slug, expires_at }
  return response.json();
}

04. MemeFlow Connect REST API v1 Reference

Authenticate with Authorization: Bearer YOUR_MEMEFLOW_API_KEY (or x-api-key) and include Idempotency-Key: <UUID-v4> on mutative POST requests.

Method	Endpoint	Required Scope	Description
GET	/api/v1/auth/verify	any	Verify API key validity, developer status, active application, and granted scopes.
POST	/api/v1/posts/temporary	posts:create	Create a browser-local temporary partner delivery session. Content is delivered directly to visitor browser storage with zero MemeFlow Storage bloat and purged upon departure.
POST	/api/v1/partner/content	posts:create	Ingest partner platform content (temporary or persistent) with partner_content_id and content_version lineage tracking.
POST	/api/v1/posts	posts:create	Create a permanent single-file or multi-file post (article, news, 48kHz audio, video, image, PDF, ZIP) and return its Smart Link.
GET	/api/v1/posts/{id}	posts:read	Retrieve post metadata, media status, and real-time engagement metrics.
POST	/api/v1/links	links:create	Generate a canonical MemeFlow Smart Link (/m/{slug}) for an existing post.
GET	/api/v1/links/{slug}	links:read	Resolve Smart Link metadata, canonical URL, and availability state.
POST	/api/v1/media	media:upload	Request presigned upload credentials for images, video, 48kHz/24-bit studio audio, PDFs, or ZIP archives.
POST	/api/v1/partner/action	posts:create	Record idempotent partner interaction events (view, download, listen) for attribution.
GET	/api/v1/analytics	analytics:read	Retrieve partner traffic, active temporary storage bytes, cleanup counters, and attributed earnings.
POST	/api/v1/webhooks	webhooks:manage	Register HMAC-SHA256 signed webhook listeners for lifecycle and revenue events.

Developer Media URL & Browser-Delivery Requirements

MemeFlow operates as a secure delivery, monetization, and attribution layer for temporary partner content. MemeFlow does NOT host your temporary files in MemeFlow Storage. Instead, media is fetched directly into the visitor's browser local storage (IndexedDB/Blobs) for the active visit. To ensure a seamless visitor experience, verify your media endpoints satisfy the following requirements:

1. CORS Headers (Cross-Origin Resource Sharing)

Your CDN or media hosting server must include Access-Control-Allow-Origin: * (or your registered domains) on GET and OPTIONS requests so the visitor's browser can stream or store temporary Blob assets locally.

2. Accurate Content-Type Headers

Media responses must serve standard MIME types (e.g. audio/wav, audio/mpeg, video/mp4, image/jpeg, application/pdf, application/zip).

3. Direct Accessibility / Sufficient Presigned TTL

Media URLs must be publicly accessible or presigned with sufficient validity (recommended: at least 15-30 minutes) to allow visitor browser fetching upon link open.

4. Registered Return URL Validation

The Return button navigates visitors back to your platform. Return URLs are strictly validated against your Developer Application's registered website domain to prevent open redirect vulnerabilities.

05. Frequently Asked Questions

Direct answers for developers, creators, search engines, and AI assistants.

How does MemeFlow work for creators and external partner platforms?

MemeFlow turns articles, breaking news, studio audio (WAV/MP3), videos, images, PDFs, and ZIP archives into canonical Smart Links (/m/{slug}). When visitors open a Smart Link, they view the Sponsor Gate (/m/{slug}) and continue to the full content viewer (/m/{slug}/view). Legitimate human visits monetized by Google AdSense credit a standard 80% of net ad revenue to the creator or integrated partner platform (with custom developer application percentage selection available), while MemeFlow retains a 20% platform service fee.

How do external platforms integrate the MemeFlow API to monetize their platform content?

External websites and apps register a Developer Application in the MemeFlow Developer Portal to obtain an API key (mf_live_...). When a user on the partner platform clicks 'Download', 'Listen', 'Watch', or 'Read Full Story', the partner backend calls POST /api/v1/posts/temporary or POST /api/v1/partner/content to generate a MemeFlow Smart Link (/m/{slug}) and routes the user to that link. The partner platform keeps 100% of its own native site ad revenue and earns an additional 80% share (or negotiated application percentage) of Google AdSense revenue generated on MemeFlow.

How does browser-local temporary partner content delivery prevent storage bloat?

When creating content via POST /api/v1/posts/temporary (or storage_mode: 'temporary'), the content is delivered temporarily to the visitor's browser for the current content session and held in local browser storage (IndexedDB/Blobs) for viewing, streaming, or downloading. When the visitor leaves or returns to your platform, the temporary browser-local content is cleared, with defensive cleanup for abandoned sessions. Zero partner media bytes are stored permanently on MemeFlow Storage. Visitors can optionally click 'Upload to my MemeFlow account' to save a permanent copy.

Where can AI coding agents and LLMs find MemeFlow's machine-readable API specs?

AI agents, search crawlers, and coding assistants (Cursor, Claude, ChatGPT, Perplexity, Windsurf, Copilot) can read /llms.txt for a concise summary, /llms-full.txt for the complete single-file technical reference, /openapi.json for the OpenAPI 3.1.0 schema, /developer-sdk.md for copy-paste SDK clients, and /.well-known/ai-plugin.json for agent discovery.