AllyOtter Lite
Free tools that get a digital product ready for affiliate networks (WarriorPlus, JVZoo, Digistore24, Whop, ClickBank, Gumroad and more: 15 networks) from Claude Code, Codex, Claude Desktop or any MCP client.
pick_networks: which networks fit your product (kind, price, one-time or recurring), ranked with reasons.network_requirements: everything one network needs: seller setup (and which steps only you, the account owner, can do), product fields, the sales-page rules reviewers enforce, affiliate page, delivery (IPN/webhook), reviewer access, approval, affiliate approval, marketplace visibility switches, refunds, known rejection reasons, dated sources.readiness_audit: reads your public sales page and flags what reviewers reject: no price, refund or contact, missing results disclaimer, income promises, fake scarcity, and each network's own rules (JVZoo's off-page links, the WarriorPlus buy button and disclaimer, Digistore24 and ClickBank checkout links). For WarriorPlus it also reads what its compliance guidelines ask: your own privacy policy, an earnings disclaimer, no fake discounts or "Step 3: profit" steps, refund wording that covers upsells, no MLM copy or exit pops that drop affiliate links, PLR labelled.submission_checklist: a field-by-field checklist for one network, prefilled from your product facts. For WarriorPlus and JVZoo it follows the network's form in order as we filled it for our own products, with each field's limit and what we learned entering it, plus what happens after you submit and the launch calendars to use.track_submission/list_submissions: where each submission stands, with the next action (on these networks "approved" is not "live"). Saved on your computer only, in~/.allyotter/submissions.json.allyotter_full_kit: what the paid kit adds.
No sign-in, no browser, no API keys. It never submits or sends anything.
Install
Claude Code:
claude mcp add allyotter-lite -- uvx allyotter-lite
Codex (~/.codex/config.toml):
[mcp_servers.allyotter-lite]
command = "uvx"
args = ["allyotter-lite"]
Claude Desktop and other MCP clients: run uvx allyotter-lite as a stdio server.
Why this exists
Our AI (Claude Code and Codex) prepared our own product, ThreadFox, for WarriorPlus, JVZoo, Digistore24 and Whop, fixed what each reviewer asked for, and submitted it. WarriorPlus approved it on 2026-09-26 and that evening WarriorPlus's own marketplace traffic sold the first copy: $49, with no ad spend. One sale; our result, not a promise of yours. Every first-hand entry in this knowledge base comes from that run; the rest come from each network's own published pages, with the date we read them. Networks change their rules, so re-check the cited source before you act.
The paid kit
The AllyOtter kit ($49 once) has your AI write each network's own sales-page version and your JV page, prepare every submission as a copy-paste pack (each field in the form's order, sized to its limit), set up Whop through its official API, hook up delivery with the verification code we run in production, track approvals and invite affiliates, personally and commission-only. Networks forbid bots on their dashboards, so you paste and click. https://allyotter.com
Made by AMF Indiana, the team behind ThreadFox. Not affiliated with any network named here. MIT licence.
Support: support@allyotter.com · https://allyotter.com/help
Changes
- 0.2.0 (2026-10-05): WarriorPlus compliance checks in
readiness_audit(privacy policy, earnings disclaimer, crossed-out or "regular" prices, money-steps, MLM wording, refund scope for upsells, exit pops, PLR, WarriorPlus's button image); field-by-field WarriorPlus and JVZoo forms insubmission_checklist; dated lessons from our October 3-5 submissions; launch calendars. Nothing here promises an approval.
Metadata
Release files for allyotter-lite 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| allyotter_lite-0.2.0.tar.gz | 117.6 kB | Without provenance | Details for allyotter_lite-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| allyotter_lite-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for allyotter_lite-0.2.0-py3-none-any.whl |
Total release size: 233.6 kB
Release files / allyotter_lite-0.2.0.tar.gz
| Download URL | allyotter_lite-0.2.0.tar.gz |
|---|---|
| Size | 117.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
93366a7ee6fdae6e8075874a3201b022b7855325c74fcdee8163d57414512bf1
|
|
BLAKE2b-256 checksum How to use checksums |
7a043fd746e98b60633ec32991d9848a3e580516b4c497cf28114fa7a1f08b4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / allyotter_lite-0.2.0-py3-none-any.whl
| Download URL | allyotter_lite-0.2.0-py3-none-any.whl |
|---|---|
| Size | 116.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5887d1ae063c184668232111b40d3ae902d7dd647ab0ffd087f2a02f6822b307
|
|
BLAKE2b-256 checksum How to use checksums |
0da6b940749aaa775f475f3b7fdbb71c96effc1343d91f541ff186d0637a4600
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for allyotter-lite 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.