For builders

Submit a tool. Keep ownership. Be early.

WeaselDen carries the marketing, the billing, the brand, and the front door. You keep building and keep ownership. Built so builders can earn from measured eligible customer activity under transparent product-specific terms; external partner payouts have not begun.

Submit your tool

Run the numbers →

The deal

The deal, in the open.

No negotiation table, no preferred partners, no fine print pricing. One subscription price, a fixed platform share, one pool. The same deal for every weasel.

Subscriber pays

$4.99

Per month, for full den access. One plan.

Platform take

A flat fee

Fixed by design. Payment processing comes out of our side, never the pool. Pilot terms, subject to change.

Builder pool

The rest

Allocated per subscriber: each user’s builder share is split across the tools that user put to work, weighted by verified usage.

Builder earnings are shares of a fixed pool, never a price per call. The pool cannot be outspent, so the model cannot bankrupt itself paying you. Boring by design. External partner payouts have not begun.

Run the numbers

What would your tool earn?

Drag the sliders. The majority of every $4.99 subscription funds the builder pool; your payout is your verified share of usage. This is the model, not a traffic promise.

Active subscribers990

5025,000

Your share of verified usage20%

1%60%

Monthly subscription revenue

Your monthly share, at least

$0+

Over a year, at least

$0+

Floors, not promises: the math above treats the majority as exactly half, and the pilot terms published to builders allocate more. Real numbers start small and the dashboard makes the trajectory visible. External partner payouts have not begun.

Trust

The numbers are right.

The entire builder relationship rests on one sentence: the numbers are right. Everything here serves that sentence.

Every call logged

Tool, hashed session, timestamp, latency, outcome. Append-only writes, captured per invocation at the platform layer.

Statements you can re-derive

Monthly statements are computed from raw logs that are retained. Any line on your statement can be traced back to the calls behind it.

A live dashboard, not a quarterly PDF

Real-time call counts and a projected payout, visible all month. You should never have to ask how you are doing.

Disputes answered with data

The attribution methodology is published. If your numbers look wrong, the answer is a query, not a shrug.

Two tiers

The Premium Den, and Weasels in Training.

Strict gates lose talent. No gates lose the brand. The den runs a funnel instead.

Tier one

The Premium Den

The flagship. Curated, reliable, brand-bearing. This is what subscribers pay for. Tools here meet the quality bar and stay there, or they move.

Tier two

Weasels in Training

A separate beta den for tools that show promise but are not premium-ready. Real exposure, real usage, real feedback. Users opt in knowing they are testing.

Every training tool is reassessed on a 90-day cycle: graduate to premium, keep training with specific feedback, or part ways. Premium tools answer to the same numbers and can move down. The den is a meritocracy and says so out loud.

Reliability and uptimeUsage trendUser feedbackFixes shipped

Division of labor

What we carry. What you carry.

The den carries

Marketing and the brand
Billing and subscriptions
Distribution and discovery
Usage tracking and builder statements
The front door and support

You carry

Building the tool
Keeping it reliable
Shipping fixes when feedback lands
Ownership. It stays yours.

Under the hood

One MCP server. Every tool in the den.

WeaselDen is a single MCP server that exposes every den tool to the subscriber’s AI. Users connect once; your tool becomes available alongside the rest of the den, namespaced and labeled by tier.

Your tool stays your tool. You expose capabilities through a manifest: tool names, descriptions, input and output schemas. The den handles transport, authentication, session scoping, and per-invocation usage tracking at the platform layer.

The server speaks Streamable HTTP per the public MCP spec. Subscriber identity is hashed before it reaches attribution logs, and tools never see another tool’s traffic.

The den server is live. Receipt Weasel is the first tool through the pipe, and the integration sequence is deliberately small: prove the plumbing, prove the attribution, then scale the roster.

What connecting looks like for a subscriber

claude-config.json

{
  "mcpServers": {
    "weaselden": {
      "url": "https://mcp.weaselden.ai/mcp",
      "transport": "streamable-http"
    }
  }
}

Apply

Pitch your weasel.

A real application, read by a human — every answer, every time. If the tool is rough but real, say so. Training-tier weasels are welcome; junk is not.

YouYour nameEmailWhere can we see your work? (optional)Who writes the code?Just you? A partner? Contractors? AI coding tools count as tools, not people — we use them too. No wrong answer, we just want the true one.

The toolWhat’s it called?Describe what it does in 50 characters or less.0/50The hardest question on the form. Take your time.What does it do, or what will it do?Plain words, like you’d explain it to a neighbor. What goes in, what comes out, who smiles.Link to the product, if any (optional)Demo video, if you have one (optional)A two-minute Loom or YouTube link beats a page of prose.Is it an MCP server yet?All three answers are fine — the den template does the plumbing.What’s the stack? (optional)Languages, hosting, and the AI models or AI coding tools you use. That’s a normal answer here, not a confession.

ProgressHow far along are you?Are people using it? Paying? (optional)Numbers welcome, honesty required. “Three friends and my mom” is a real answer.How long have you been working on it? (optional)

CuriousWhy the den? What part of someone’s day does your tool make a little better?This is the question we read first.Any other tool ideas in your drawer? (optional)List them, even half-baked. Sometimes the second idea is the weasel we’ve been waiting for.

Forms not your thing? Email hello@weaselden.ai and answer whichever of these you like.

Builder questions

The fine print, out loud.

Who owns my tool?

You do. The den gets a license to host, display, and promote it while it lives here. Ownership never moves.

Is the den exclusive?

No lock-in by default. Your tool can live elsewhere too. Exclusivity, if ever, would be a separate conversation with separate terms.

What gets accepted?

Working tools from good-faith builders. Premium needs polish and reliability. Training needs promise and a builder who ships. Junk, scams, and abandonware get a fast no.

When do payouts start?

Not yet. External partner payouts have not begun. The den meters verified usage from day one, so when payouts start for your tool, the first statement reflects numbers that already exist.

How do I get paid?

Straight answer: the payout rails are still being built and external payouts have not begun. Method, schedule, and settlement get agreed with you under transparent, product-specific terms before your tool earns. You handle your own taxes.

Can my tool be removed?

Yes. Removal and relegation key off published KPIs: reliability, usage trend, feedback, and fixes shipped. You get the numbers, specific feedback, and a path back.

The den is taking applications.

Be early. Every tool onboarded now is one a future competitor has to poach.

Submit your tool