Sell digital products, ship physical goods, capture leads — from one platform that also runs your site, your customers and your calendar. All of it behind an open API, so the AI you already use can work it directly.
No credit card required. Connect Stripe when you're ready to charge.
Most businesses run at least two of these. Running them in separate tools is why nobody can tell you which article sold the thing. Here they share one customer record and one checkout.
Put a price on an article, a report, a dataset, a course. Sell it outright, gate it behind a membership tier, or give the first half away and charge for the rest — the paywall cuts exactly where you put it, and the free part still gets indexed.
A real catalog: shipping addresses, inventory counts, order status, fulfilment. Buyers filter by the attributes your products actually vary by, and every order lands against the customer who placed it.
Not selling a SKU? Put a form on any page and point it at a list. It creates the contact, joins the list, logs the enquiry, and records which page produced them — so your pipeline knows where it came from without a tracking spreadsheet.
Connect your own Stripe account in a click. One-time payments, subscriptions, renewals and the customer portal are handled, and funds settle to you directly — we never hold your revenue.
The old stack was five products and a pile of integrations holding them together — which is fine when a person is the glue, and useless when you want an agent to be. Here it is one system, so what brought a customer in is attached to the order they placed.
A block editor for pages and long-form articles, a media library with responsive images, and public pages that render server-side with clean URLs and structured data so they can actually be found.
Product pages, a filterable catalog, checkout, digital delivery, order management and a customer portal — on your own account, at your own URLs.
Contacts, segmented lists, enquiry history, purchase history and internal notes. Sales opens a record and sees what the person read and what they bought, not a CSV row.
A/B test a headline, a price or a form on any block. Conversions count against the same customer records everything else uses, so a result is a revenue number rather than a click number.
There is no bundled assistant here, and no model you’re locked into. The whole platform is an open API and a command-line tool, which is what the agents you already pay for are good at driving — so they can publish the page, price the product, answer from your own documents and work the follow-up list, end to end.
# publish the launch article, written as markdown modelpad notes create --title "The 2026 Buyer's Guide" --markdown guide.md # put it on the storefront and price it modelpad products create --name "Buyer's Guide (PDF)" --set price=29.00 # find what it already knows before answering a customer modelpad notes list --query search="do you ship to the EU" # work the follow-up list — who enquired, and what did they ask modelpad contacts list --query list=pricing-enquiries modelpad contacts interactions <id>
Claude Code, Codex, Cursor, a harness you wrote yourself. Anything that can run a command works on day one, and an MCP endpoint exposes 46 tools over streamable HTTP for clients that prefer tool calls to a shell.
Nothing here is tied to one vendor. The in-app assistance runs on hosted Claude, on OpenAI, or on anything you host yourself — Ollama or any OpenAI-compatible endpoint — so your data can stay on your hardware if that matters.
One env var authenticates. JSON to stdout, human text to stderr, so piping is safe. Markdown converts both directions, so a model never learns an internal format. Updates read-then-merge, so setting one field doesn’t blank the record.
Issue a separate credential for each agent or automated run, see them all in one list, and revoke any of them independently. An autonomous run gets its own blast radius.
A real run with an off-the-shelf coding agent — no custom integration, nothing bundled from us. The kind of work that used to mean a prospecting tool, a scheduler, a website builder and an afternoon of copy-and-paste between them.
An assistant is only as useful as what it can see. Everything here is one connected graph with search built in, which is the difference between an agent that guesses and an agent that knows.
Customers, orders, products, pages and documents are linked by typed relationships — Purchased, Interested In, Lead From, Featured On. "Who bought this and what did they read first" is one question, not a data project.
Keyword matching catches the SKU and the order number. Vector similarity catches the customer who phrased it their own way. Both run together and return one result set, so an agent answering support gets the actual document.
Documents are indexed the moment they are saved, in the same write. No nightly job, and no window where your agent is answering from last week’s prices.
Point retrieval at one product line or one folder and the answers stay inside it. Your agent cites your material instead of inventing a policy you never wrote.
Set it on the thing itself, not with a plugin. Leave the top of the funnel open so it gets found, and make everything past it earn an email address or a payment. One item can offer more than one way in.
Open to everyone and indexable. Where your SEO work pays off.
Free, but you get the contact. Right for benchmarks and templates.
Pay once, keep access. Reports, datasets, training material.
Recurring access to a body of content. Predictable revenue.
The work between a good idea and a business that runs. None of it is exciting, all of it is required.
Documents and products publish as real HTML with canonical URLs, structured data and a sitemap that updates as you go — so the corpus you built for your agents is also indexable by everyone else’s.
A block editor with inline AI assistance, cloud or local models, and personas per document. Agents and people write into the same store, in the same format.
The web app is a client of it, so nothing is held back for the UI. Predictable resources, consistent pagination, JSON errors, and a reference with a runnable example on every endpoint.
Documents, relationships, contacts and orders read back out in the same shape they went in. Your graph is yours, and it leaves as cleanly as it arrived.
Create an account, put your business in it, and hand whichever AI you already use an API key. Connect Stripe whenever you’re ready to start charging.
Create Free Account