Developer documentation

MonetizeGroup developer resources & API documentation

Build automated media-buying workflows, connect autonomous agents via Model Context Protocol (MCP), or integrate Facebook group listings programmatically with the Monetize Group Marketplace REST API.

Download OpenAPI 3.1 Spec MCP Agent Setup Agent Instructions

OpenAPI 3.1 specification

Strict machine-readable JSON schema defining all request payloads, parameters, responses, and security schemes.

Inspect openapi.json→

Model Context Protocol (MCP)

Native tools for Claude Desktop, Cursor, and agent frameworks to discover groups and book placements autonomously.

Configure MCP server→

Accept: text/markdown

Full compliance with acceptmarkdown.com. Pass the header to receive lightweight token-efficient markdown representations.

Content negotiation guide→

MonetizeGroup authentication and API keys

All API requests must be authenticated using either a session cookie (`better-auth.session_token`), a Bearer token in the `Authorization` header, or an `X-API-Key` header issued to programmatic accounts.

HTTP Request Header Example

GET /api/groups?niche=Tech HTTP/1.1

Host: monetizegrouphq.com

Authorization: Bearer <YOUR_API_TOKEN>

Accept: application/json

MonetizeGroup marketplace REST API

Core endpoints for browsing verified Facebook groups, managing orders, configuring 24-hour pinned posts, and tracking fulfillment proof URLs.

GET/api/groups

?niche=Tech&owner_id=usr-123

Filter verified Facebook groups by member size, category niche, and base sponsorship rates.

POST/api/groups

{ name, url, niche, member_count, base_price }

Submit a new Facebook group for automated description token scanning and marketplace indexing.

GET/api/orders

?role=buyer

Query campaign orders where the user is either merchant (buyer) or group administrator (seller).

POST/api/orders

{ group_id, total_price, post_copy, is_pinned, is_tagged }

Book a sponsored post placement with escrow balance deduction and 48-hour delivery protection.

GET/api/orders/{id}

path: id (e.g. ord-88319)

Audit campaign delivery progress, verify live Facebook permalink proof, and check payout release status.

MonetizeGroup Model Context Protocol (MCP) server

Connect Claude, Cursor, or autonomous AI agents directly to the Monetize Group Marketplace using the official MCP server. This allows agents to discover communities and book placements autonomously within safety limits.

claude_desktop_config.json / cursor_settings.jsonNode / npx

{
  "mcpServers": {
    "monetizegroup": {
      "command": "npx",
      "args": [
        "-y",
        "@monetizegrouphq/mcp-server"
      ],
      "env": {
        "MONETIZEGROUP_API_KEY": "your_api_key_here"
      }
    }
  }
}

list_groups

Search verified Facebook groups by member size, price, and category.

book_sponsorship

Place campaign orders with copy, UTM link, and add-on pin/tag flags.

get_order_status

Check real-time delivery status and verified Facebook post permalink.

Markdown content negotiation (acceptmarkdown.com)

Monetize Group fully implements the RFC-compliant HTTP content negotiation standard defined by acceptmarkdown.com. Autonomous agents can consume any page on our apex domain as clean Markdown.

# Curl example requesting Markdown

curl -H "Accept: text/markdown" https://monetizegrouphq.com/

# Server Response Headers:

HTTP/1.1 200 OK

Content-Type: text/markdown; charset=utf-8

Vary: Accept, Accept-Encoding

When requesting nonexistent paths with `Accept: text/markdown`, the server returns HTTP 404 with a recovery Markdown body containing direct pointers to `/sitemap.xml`, `/llms.txt`, and this developer portal.