Nuelink Developer Documentation

Version: 1.0 (Alpha) Base URL: https://nuelink.com/api/public/v1

Nuelink offers two ways to publish programmatically. They share the same account, the same brands, the same collections, and the same channels. The difference is who is driving.

Two surfaces, one Nuelink

REST API

HTTP endpoints for developers building integrations, automations, or custom apps.
Send a POST request, get back a post ID. Works from any language that can make HTTP calls.

Start with API Quick Start.

MCP Server

Connect Nuelink to Claude, ChatGPT, Cursor, Manus, Codex, or any other MCP-compatible AI assistant, and publish posts in natural language.

Start with MCP Quick Start.

You can use both. The MCP server is a thin wrapper around the public API, so anything one can do, the other can do.

This first release focuses on a single workflow: creating posts and uploading media. Listing, updating, and deleting existing posts will arrive in a later release.

How Nuelink is organized

Before you make your first call (or your first prompt), it helps to understand the three-level hierarchy Nuelink uses:

Account
  └── Brand (workspace, e.g. "Fernwood Botanicals")
        ├── Channels     (the connected social accounts: IG, X, TikTok, ...)
        └── Collections  (content folders grouped by theme or campaign)
              └── Posts  (social media posts)

Brand

A fully isolated workspace. Each brand has its own channels, collections, automations, and insights, so you can manage multiple companies or projects without their data mixing. Most accounts have one brand; agencies and power users typically have several.

Collection

A content folder inside a brand, typically organized by theme or campaign (e.g. “Summer Campaign”, “Product Launches”, “Customer Stories”). Each collection has a set of default channels and weekly time slots (aka Queue). When you create a post inside a collection, it publishes to the collection’s default channels.

Channel

A single connected social account, e.g. @fernwoodbotanicals on Instagram or your company LinkedIn page. Channels belong to a brand.

So creating a post is always:

Pick a brand → pick a collection inside it → POST the post to that collection.

Channels are listed as a separate endpoint so you can inspect what is connected to the brand, but you do not pass channel IDs when creating a post; the collection’s configuration determines which channels receive it.

Which surface should you use?

	REST API	MCP Server
For	Developers writing code	Anyone using an AI assistant
Interface	HTTP requests	Natural language
Best for	Custom apps, automations, integrations, scheduled jobs	Drafting, scheduling, day-to-day posting
Auth	API key in Authorization header	Same API key, via URL param or header
Workflow	Code → request → response	Prompt → assistant → tool calls

If you are building software that publishes posts (a content scheduler, a CMS integration, an automation pipeline), use the API.

If you want to publish posts from an AI assistant you are already using to draft them (Claude, ChatGPT, Cursor, etc.), use the MCP Server.

If you are not sure, start with MCP Quick Start. It is the fastest path to a working setup, and you can always layer the API on top later.

Documentation map

API

Quick Start - your first API post in 5 steps.
Authentication - bearer tokens and how to get one.
Rate Limits, Errors, Pagination
Endpoints - full reference for every endpoint.
Platform-Specific Options - Instagram collabs, YouTube playlists, and more.

MCP Server

Overview - what the MCP server does and when to use it.
Quick Start - connect Nuelink to your AI assistant quickly.
Authentication - API key in URL or header.
Available Tools - the six tools the server exposes.
Example Prompts - copy-paste prompts for common workflows.

Resources

Changelog - releases for both API and MCP.