For builders
Bring your app. Keep ownership. Get paid.
WeaselDen carries the marketing, the billing, the brand, and the front door. You keep building and keep ownership. We agree on integration, pricing, and payout terms with each builder before their app is listed. External partner payouts have not begun.
The deal
Terms agreed with you, before you’re listed.
We agree on integration, pricing, and payout terms with each builder before their app is listed. Nothing is decided for you after the fact.
Your app
Stays yours
You own it. The den gets a license to host, display, and promote it while it lives here. Ownership never moves.
Your terms
Agreed first
Integration, pricing, and payout terms are agreed with you before your app is listed. No form letter, no fine print sprung on you later.
Your earnings
Per your terms
Earn under the payout terms agreed for your app. Every use is metered from day one, and your statements show the calls behind every line.
Payouts follow eligible customer activity under the terms agreed for your app: not a price per call, and not a promise of traffic. External partner payouts have not begun.
How you get paid
Usage in. Statement out. Paid under your terms.
No sliders, no projections. This is the path one use of your app takes, from a chat to your statement.
A person uses your app
Inside ChatGPT, Claude, Grok, or Muse, or on your own site through the den.
The den meters the call
Tool name, hashed session, timing, outcome. Appended per call, never edited.
Your statement builds
Every line traces back to the calls behind it. You can re-derive it yourself.
You get paid
Under the payout terms agreed for your app, once external payouts begin.
External partner payouts have not begun.
submit_receiptAdd a receipt imageloggedconfirm_receiptConfirm a receiptloggedtrack_itemsWatch item pricesloggedcheck_price_dropsCheck price dropsloggedlist_receiptsList your receiptslogged
Real tool names from the den connector. No amounts: yours depend on your terms.
Illustrative only. Actual payouts depend on the terms agreed for your app and eligible customer activity.
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.
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. Not on MCP yet? Bring the app anyway. The integration path is part of what we agree on during review.
What connecting looks like for a subscriber
{ "mcpServers": { "weaselden": { "url": "https://mcp.weaselden.ai/mcp", "transport": "streamable-http" } }}List your app
One form. One review.
Tell us about the app you already built: the idea, a link, a demo, the vision. The technical details are a second step we send during review.
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.
Do I need an MCP server to apply?
No. Bring the app you already built. If it has an MCP server or an API, tell us. If not, the integration path is one of the things we agree on with you during review.
Is the deal the same for everyone?
No. Integration, pricing, and payout terms are agreed with each builder before their app is listed, because a free utility and a paid organizer do not want the same terms. What never changes: you keep ownership, a human reviews every listing, and you get paid when your app is used.
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 app onboarded now is one a future competitor has to poach.