feeef developers | Build commerce on your terms

What will you build?

A new app. A better workflow. Something we haven’t imagined yet.

Connect your app.

Work with a merchant’s products, orders, and store through OAuth and the commerce API.

Explore the API

Orthographic rendering of a mechanical app connection with locking plugs, a keyhole, and an access gate

Give your agent tools.

The feeef MCP server connects compatible AI clients to stores, catalogs, orders, and delivery.

Connect an agent

Orthographic rendering of a green tool hub with physically connected porcelain modules

From your code to their storefront.

Author the components. Compile the document. Preview with real data, then publish a release.

Orthographic studio render of structured porcelain panels with green editable inserts and a mechanically joined base

components.tsxschema.tslocales/en.json

Your components. Their content.

Write a React component and define the fields a merchant can edit. Code and content have different owners.

pages/home/components/hero.tsxTSX

export const meta = {
  type: 'custom',
  title: 'Hero',
  propsSchema: {
    heading: { type: 'string', name: 'Heading' },
  },
  props: { heading: 'A store of your own.' },
};

function App() {
  return <h1>{props.heading}</h1>;
}

A document the storefront understands.

The kit builds a TemplateData document, an editor schema, and locale files. The storefront reads the compiled result.

dist/data.jsonJSON excerpt

{
  "type": "custom",
  "instanceId": "hero_home",
  "title": "Hero",
  "props": {
    "heading": "A store of your own."
  },
  "propsSchema": {
    "heading": { "type": "string", "name": "Heading" }
  },
  "code": "function App(){return React.createElement('h1',null,props.heading)}"
}

Try the draft. Then ship the release.

Preview against your store’s real catalog. The live theme stays in place until you explicitly publish and apply a release.

your terminalCLI

# Validate and compile your source.
npm run check
npm run build

# Preview a hosted draft with your store's data.
npm run dev

# When the draft is ready, publish and apply it.
npm run publish -- --public --apply

Your storefront.
Your signature.

Write the components. Define what’s editable. Give merchants a store that feels like their own.

Author in TSXReact components, editable props, named slots.

Compose as dataOne compiled JSON document for the storefront.

Preview, then publishA hosted draft against your store’s real catalog.

Create a template

Desktop view of the Cobalt demo storefront, showing its blue split hero and desk objects collection — A published template. A fictional demo catalog.Live demo

Mobile view of the Cobalt demo storefront, showing its navigation, blue headline, and product photography — A published template. A fictional demo catalog.Live demo

A few lines.
A real connection.

Pick your starting point. Use the same commerce platform from your app, a template package, or an AI client.

JavaScript SDK Dart SDK Apps & OAuth 2.0 Signed webhooks

1import { FeeeF } from 'feeef';
2 
3const feeef = new FeeeF({
4  apiKey: process.env.FEEEF_TOKEN!,
5  baseURL: 'https://api.feeef.org/v1',
6});
7 
8const { data: products } = await feeef.products.list({
9  storeId: 'your-store-id',
10  status: 'published',
11  limit: 10,
12});

1# Replace your-store-id with your store’s ID.
2curl --get 'https://api.feeef.org/v1/products' \
3  --data-urlencode 'store_id=your-store-id' \
4  --data-urlencode 'status=published' \
5  --data-urlencode 'limit=10' \
6  --header 'Accept: application/json'
7 
8# The JSON response includes data and pagination.
9# Connect from any language with an HTTP client.

1npm install -g @feeef.dev/cli
2feeef signin
3feeef template init my-template --blank
4 
5cd my-template
6npm install
7feeef use
8 
9npm run build
10npm run dev
11 
12# Open the draft preview on your real store.

1{
2  "mcpServers": {
3    "feeef": {
4      "url": "https://mcp.feeef.org/mcp"
5    }
6  }
7}
8 
9

Orthographic Cycles-style studio rendering of a stock shelf, packing bench, shipping carton, and roller conveyor

Beyond the buy button.

A store keeps moving after checkout. Build against the stock, money, and parcels behind each order.

Inventory that records the movementStock objects, reservations, and a ledger of changes.Finance that follows the moneySupplier bills, payments, and financial accounts.Shipping built around the parcelCarrier accounts, quotes, labels, and parcel records.

Availability depends on the store’s permissions and enabled integrations.

Built here. Shared openly.

Read the blog

A cobalt blue desk lamp, ceramic pencil cup, and aluminum tray from the Cobalt demo catalog

Design & developmentBy Mohamed

From a blank template
to a real storefront.

The decisions, the rough edges, and the finished Cobalt demo. A complete build, shared as it happened.

Read the build story

Orthographic porcelain document panels with green editable inserts, illustrating the feeef template architecture

EngineeringBy Mohamed

Why a theme
is a document.

Inside the template system: JSON, React, server rendering, and the tradeoffs behind the design.

Explore the architecture

Good questions.

What is feeef?

feeef is a commerce platform for merchants. Its developer platform provides a REST API, OAuth apps, JavaScript and Dart SDKs, storefront templates, a CLI, webhooks, and an MCP server. Developers can work with stores, products, orders, delivery integrations, inventory, and finance.

How are feeef storefront templates built?

A feeef template is authored as a Node.js package with TSX components, an editor schema, and locale files. The template kit compiles these sources into a JSON document called TemplateData, which the Lithium storefront renderer reads. Developers define editable props and slots; merchants customize their content. The CLI previews a draft on a hosted store before a release is published and installed.

Can AI agents connect to feeef?

Yes. The hosted feeef MCP server at https://mcp.feeef.org/mcp uses Streamable HTTP and supports OAuth or a bearer token. Compatible clients can use its tools to work with stores, products, orders, delivery, inventory, and finance. API token permissions, store roles, and integration requirements still apply.

Build commerce. On your terms.

What will you build?

Connect your app.

Give your agent tools.

From your code to their storefront.

Your components. Their content.

A document the storefront understands.

Try the draft. Then ship the release.

Your storefront.
Your signature.

A few lines.
A real connection.

Beyond the buy button.

Built here. Shared openly.

From a blank template
to a real storefront.

Why a theme
is a document.

Good questions.

Make it yours.

Build commerce. On your terms.

What will you build?

Connect your app.

Give your agent tools.

From your code to their storefront.

Your components. Their content.

A document the storefront understands.

Try the draft. Then ship the release.

Your storefront.Your signature.

A few lines.A real connection.

Beyond the buy button.

Built here. Shared openly.

From a blank templateto a real storefront.

Why a themeis a document.

Good questions.

Make it yours.

Your storefront.
Your signature.

A few lines.
A real connection.

From a blank template
to a real storefront.

Why a theme
is a document.