Developers
Build on REM products
Every REM product publishes its developer docs here: the HTTP API, MCP tools for AI assistants, tokens and scopes, webhooks and working examples.
Developer docs by product
Each set opens on the product’s own website.
REM AI
One AI model, remai, for your apps, agents and team.
REM Auth
One REM account for every REM app.
REM Blogs
The content hub for every REM product.
REM CloudHub
Publish, run and schedule your apps, with an AI gateway built in.
REM Genie
One chat that gets things done in every app on REM Platforms.
The developer docs for REM Genie are being published. Until then, open REM Genie or write to us.
REM Payments
Plans, checkout, subscriptions and invoices for every REM app.
REM Vibe Coder
Describe an app; get a tested, running app.
The developer docs for REM Vibe Coder are being published. Until then, open REM Vibe Coder or write to us.
Showing REM Blogs content in a REM app
An app shows its blog, docs, legal pages, forms and newsletter from REM Blogs with two values, both server side only.
# the app's server environment (never in the browser)
REM_CONTENT_URL=https://blogs.remplatforms.com
REM_CONTENT_TOKEN=rct_... # issued once in REM Blogs > Products > Link the App// lib/content.ts (Next.js, @rem/content-react)
import { createContentClient } from '@rem/content-react';
export const content = createContentClient(); // reads REM_CONTENT_URL + REM_CONTENT_TOKEN
// app/blog/page.tsx
const page = await content.posts({ page: 1 });
return <BlogIndex page={page} basePath="/blog" />;- Python apps use the stdlib-only rem_content package with the same two values.
- Public API lives under /api/public/<product>/: posts, topics, authors, docs sets and pages, legal pages with versions, docs search, sitemaps, RSS and Atom, robots.txt and llms.txt. Responses carry an ETag and a short shared cache.
- Drafts are visible only with ?preview=1 and a token holding content:preview; previews are never cached.
Publish webhook
When something is published, REM Blogs calls each product's webhook so it can drop its cached copy. Every call is signed:
X-REM-Content-Signature: t=<unix seconds>,v1=<hex>
v1 = HMAC-SHA256(key = sha256hex(serviceToken), message = t + "." + rawBody)The key is the SHA-256 of the app's own service token, so the token is the only secret the app keeps. While a product has two active tokens (during a rotation) both signatures are sent and either one passes. verifyWebhook in the SDK checks it for you.
MCP tools for writers
Writers can draft from an AI assistant through the REM Blogs MCP server, with an API token from Admin › Account › API tokens. The tools are house_format, search_posts, read_post, list_products, create_post, update_post and upload_image. They can draft, edit and upload images you supply; they cannot publish or delete, every write is audited, and generating images with AI is refused.
Missing an endpoint or an example?
Tell us what you are building and which product it is for.
Questions? Write to support@remplatforms.com.