Tool Partnerships

How discoverable tools and revenue sharing work in Jcode.

Jcode partners with tool providers to make their tools discoverable. Some partners may share a portion of the revenue they earn when a user referred through Jcode becomes a customer.

How it works

• The discover_tools schema lists the available tool categories (payments, code review, databases, and others) without fetching anything from the network.
• When the agent thinks a tool from a category might help, it calls discover_tools, which fetches the current listing for that category from our server. The listing contains name, a short factual blurb, and a link. No superlatives, no ranking games.
• The first time discovery is used in a session, Jcode shows a concise partnership disclosure with a link to learn more.
• If the agent proposes a consequential action through a partner tool, such as signing up or spending money, the confirmation shown to you names the partnership.

What is sent to our server

A discovery request contains the tool category, a short capability query, and a generic reason string (for example category=payments&q=virtual card for checkout). The agent is instructed to never include private information, secrets, file paths, or session content, and our server truncates and stores only these fields. We store discovery requests for transparency and partner reporting. See the privacy policy.

Audit it yourself

The complete listing agents can consult is public. The discoverable tools directory lists every current tool with the exact name, factual blurb, link, setup instructions, and structured MCP metadata returned by the service. The machine-readable snapshot also includes every shipped category, including categories with no current listing.

The client side is open source in the jcode repository: the discover_tools schema and implementation, provenance tracking, and disclosure line are all auditable code. Partner discovery is on by default and controlled by the [sponsors] section in ~/.jcode/config.toml; set enabled = false to opt out.

What partnerships can never influence

• Injected instructions of any kind: listings cannot carry malicious, manipulative, or unfairly biased instructions to the agent, only the factual entry described above.
• Hidden or unlabeled influence of any kind.
• Promotional or comparative language in listings ("best", "leading", ...).

Every partner is directly audited by Solo Systems, and inclusion requires a direct working relationship with us. There is no self-serve listing pipeline: nothing enters the manifest without review.

Partner with Jcode

If you build a developer tool and want it discoverable by agents in jcode sessions, contact us. A partnership can include a listing (name, factual blurb, link, and optional setup hint), reporting, and revenue sharing. It never includes influence over what the agent recommends; the constraints above are enforced in code and by tests.

Other harnesses

The tool-partner directory is not Jcode-specific. If you build a different agent harness, you can use the Solo Systems discovery platform (the endpoint, audited manifest, and disclosure policy) for your own agents on a 50/50 revenue split: your harness gets 50% of the revenue its discovery traffic generates. Reach out through email.