Relevance AI Marketplace submission guide

This guide records the submitted package and remaining review boundary. It does not convert a pending submission into a public listing or authorize acceptance of new legal terms.

Current state

The authenticated RunOnProof Builder profile shows five intended Tool listings with approval status pending and published status Unpublished. The out-of-scope Company Capability Passport submission was withdrawn on 2026-08-12 without deleting its private Tool. No public listing URL exists.

Verified platform requirements

• Only verified Relevance Builders can submit.
• Every Marketplace submission is reviewed by the Relevance team.
• Tool and Agent listings may be free or paid at the Marketplace layer.
• Tool input descriptions must explain what users and agents should provide.
• API keys or OAuth requirements must be surfaced as clone-time inputs; secrets are not copied.
• An approved update must be submitted again for review.

The RunOnProof listings are free to clone. RunOnProof execution prices in USDC are separate and must remain visible before payment.

Before publication approval

Confirm:

• current Relevance AI Marketplace eligibility and terms from official sources;
• whether five Tool listings or one consolidated Agent gives the clearest installation journey;
• review requirements, pricing, support, privacy, and data-processing obligations;
• whether legal terms require acceptance by Ricardo or the company;
• whether a public listing needs a public production call path;
• ownership of support, updates, incident response, and deprecation.

Stop for human action if login, MFA, new terms, identity documents, legal declarations, Stripe onboarding, fees, or public-publishing confirmation are required.

Submission package to prepare

• truthful title and short description;
• public case and screenshots using synthetic data;
• installation and everyday-use guide;
• exact inputs and outputs;
• current capabilities and limitations;
• security and privacy summary;
• cost/HTTP 402 explanation;
• support and troubleshooting route;
• version, repository SHA, and validation evidence;
• statement that RunOnProof is not claiming a partnership.

Pre-submission gates

• Public docs routes are live and coherent with GitHub.
• Tool and agent pass all synthetic workspace cases or the listing precisely states which tests were run.
• Current product, price, coverage, and source health are verified.
• Automatic payment remains off unless separately designed and authorized.
• No secrets or real personal data exist in examples or screenshots.
• Rollback and support ownership are active.
• Company Capability Passport submission was withdrawn while its private Tool remains available internally.
• Legal/terms acceptance is recorded by an authorized human.
• The listing does not promise unsupported capabilities.

Possible external states

Record one exact state:

• NOT_SUBMITTED
• SUBMITTED_EXTERNAL_REVIEW — current state for five listings
• CHANGES_REQUESTED
• APPROVED_NOT_LISTED
• PUBLISHED_DISCOVERABLE_CERTIFIED
• REJECTED

Never describe submission as approval or internal publication as public listing.

After review

Preserve the submitted version and evidence. Track review feedback without weakening safety. Re-run certification for every requested technical change. After approval, use a separate external Relevance account or project to find, clone and connect Company Check before asking for the one 0.04 USDC purchase approval.

The current truthful verdict is RELEVANCE_PUBLICATION_REVIEW_PENDING.