MagicMarker

magicmarker.dev — v0

MagicMarker

The framework to build markers, make them move, make them do things.

Every developer gets ONE marker, free-forever. A marker is a custom-built agent that uses marks — tools and skills — to build out your request as intent on a canvas. It runs on a provider-specific API key you bring: Claude, OpenAI, and more.

ink = the tokens used by your API key — counted, never billed

Marks

Tools and skills the marker uses to build out your request. The marker decides which marks to reach for.

Canvas

Intent is built on a canvas. Markers output canvas nodes — you can see what they're making and arrange it.

Your key

BYOK. A provider-specific API key — yours. The platform never bills tokens. It only counts them.

the biggest feature — why MagicMarker exists

Give your marker away. At your own expense.

You finish a milestone on a client's project. You give the client access to your marker — the one that built their project — for a set period of time. The marker goes through the designs with them and iterates on what's new, or what they don't like.

The catch

Free tier has one marker spot. If it's filled and you give your marker away — you don't have it anymore. They do.

The rules

You set the rules so the marker doesn't go building large fixes without you helping it move correctly. A revisionary period: a set amount of revisions it's allowed — about 25 on free (being tuned), more on paid tiers.

The hand-off

Send it filled — loaded with the project's context, the marker that built it — or with little ink, near-fresh. Your choice either way.

provider-native

The provider maintains their own marker.

Anthropic can come on the platform, verify they are Anthropic, and own the Claude Marker. Others hook their API key up to it. Through the MagicMarker dashboard, the provider maintains that marker's capabilities — prompts, marks, output behavior — build it, test it, ship it their way.

Why the seat is theirs

Staying current on every provider's way of doing things is too much for one person. So the platform doesn't maintain every provider's marker — the provider maintains their own marker, on this platform.

the marketplace — working name: the storeroom

Markers are like apps. You connect an API key to them.

Buy markers. Demos show what a marker can do — how it outputs canvas nodes, how it designs stuff. Developers build markers and sell them to other developers.

70 / 30the creator keeps 70 of every marker sale — the platform takes 30

One-time license

Unlimited usage — you just need an API key. Buy a marker once, run it as much as you want.

Capabilities only

A marker sale never includes the API key. You purchase the marker, then key in your own.

Creators keep them current

Updates are the creator's call — free or paid. A popular marker does well for the person who built it.

the first marker

Memory Marker — “The Interpreter”

The first marker in MagicMarker stands between you and your model. It catches your input first — before the model ever sees it. It reads what's there: is there memory relevant to this? What is it, where is it, where is it going? If memory needs adding, it enriches your text before forwarding it — so your model still has what it needs to have.

Train it by use

Tell it what you normally like. Give it a normal prompt and it catches them, and sees what's going on. You control your prompts by catching them.

A little tiny model

Right there on the app. Small, local — it does the catching and the checking.

Engine your way

Runs as an API — or locally, on your machine. The relay can sit on a server that catches traffic before the model machine.

integration

Put the marker on your machines.

Browser, app, canvas — build with the framework to make it move around on your screen. And it travels: this marker knows how to get around on machines as long as it knows how to speak that code — as long as people allow it to integrate.

Into someone else's system

A TMS, for example? That's your dev work: ask them about enterprise integration, see what code they're using, and integrate where you're allowed.

pricing

Free-forever at the core.

Every tier runs on your own API key. Mark executions are the hosted-compute meter. Client spots are time-boxed access for a client's marker.

Free Forever

$0

the one marker, free-forever

  • 1 Marker Spot
  • 1,000/day Mark Executions
  • 12hr Client Spots
  • Community Support

Lite

$4

everything in Free

  • 2 Marker Spots
  • 3,000/day Mark Executions
  • 24hr Client Spots
  • Limited Support

Solo

$17

everything in Lite

  • 5 Marker Spots
  • 10,000/day Mark Executions
  • 72hr Client Spots
  • Expedited Support

Agency

$100–$300

everything in Solo

  • 25–75 Marker Spots
  • 100k–500k/day Mark Executions
  • 7–30 day Client Spots
  • Priority Support

Enterprise

$$$$

everything in Agency

  • 100+ Marker Spots
  • 1M+/day Mark Executions
  • 30d+ Client Spots
  • First-in-Line Support

MarkerPassseason pass

$20

per season

  • 5 Marker Spots
  • 20 Marker Skinshow your marker looks — yes, you pay to make it look unique; skins live in the marketplace
  • 3 Featured Markersper-season usage, unless purchased with a 30% off coupon
  • Beta Marker Accessproviders control how long their markers stay in beta
  • Unlimited Marker Relay Executionsmarkers talking to each other, like a team

Prices are as specced. Billing cadence for the monthly tiers is still being pinned — MarkerPass is explicitly per season.