Listing and Review

Nothing on a connector's marketplace page is typed by hand: the card, the detail page, the in-app directory, GET /connectors and the MCP catalogue all read the manifest's listing block. What a connector cannot say about itself, the registry stamps.

The listing block

Every field of the block is specified on listing in the manifest reference; this page is about what to put in it and how it is reviewed.

"listing": {
    "category": "messaging",
    "tagline": "Sell access to channels and groups, granted and removed automatically.",
    "overview": "Connect a bot you created with @BotFather and Subscriby runs your membership…",
    "screenshots": [],
    "links": {
        "documentation": "https://docs.subscriby.net/guide/connectors/telegram",
        "support": "mailto:[email protected]",
        "privacy": "https://telegram.org/privacy",
        "terms": "https://telegram.org/tos",
        "homepage": "https://telegram.org"
    },
    "added_at": "2025-04-21",
    "changelog_url": "https://www.subscriby.net/blog",
    "sign_in_required": false,
    "marketing": {
        "audience": "Telegram communities",
        "place": "channel",
        "places": "channels, groups and supergroups",
        "installation": "bot",
        "identity": "Telegram account",
        "native_payment": "Telegram Stars"
    }
}

• category shelves the connector: messaging, community, payments or productivity.
• tagline is the one line under the name, 80 characters at most; the card shows it whole.
• overview is the Overview tab, Markdown. Say what the connector does for a creator and for a member; the capability section under it is generated from the manifest, so do not repeat the feature list.
• links appear under More info. documentation should be your own guide for creators; privacy and terms are the platform's policies, and the marketing site's legal pages link the available connector's privacy for members' reference.
• added_at drives the New chip for sixty days; changelog_url is where you announce releases; sign_in_required tells creators whether they must sign in to the platform to install (an OAuth connector says true).

The marketing words

The public site, the home page, the twelve vertical pages, the twelve comparison pages and the legal pages, never spells a platform. Its copy carries tokens that are filled from the connectors available on that installation of Subscriby, so a sentence written once names Telegram today and whichever connector is available tomorrow. Your marketing block supplies the words:

The connector's name fills :platform, and every available connector together fills :platforms. A sentence built on a word your block does not supply is dropped rather than rendered half-empty: a comparison row about native payments disappears when no available connector declares one. Write the words in lower case except the platform's own proper nouns, and as they would read mid-sentence ("your :place", "a :platform :installation").

What Subscriby stamps

These are never in the manifest, so a package cannot claim them:

Review checklist

Before a package is installed on Subscriby it is read against this list. Each item is something the conformance kit cannot judge alone.

1. The kit is green, including manifest.file_is_the_source and migrations.own_tables_only.
2. Nothing from the application's namespace is imported; the connector talks to the core through Subscriby\Connector\Core\* and the SDK's value objects only.
3. Credentials never reach a log, an exception message or a view. Tokens live in the core's encrypted CredentialBag; your own tables hold them only when the platform's client forces it.
4. Every slot contribution has a placeholder that mirrors its loaded layout, and every string it shows comes from the package's lang/*.json in all ten locales Subscriby ships (English, Spanish, French, German, Italian, Portuguese, Turkish, Hindi, Bengali, Sinhala).
5. The listing tells the truth: the tagline and overview describe what the bound ports do, privacy and terms are the platform's, and documentation resolves.
6. The platform's terms allow it. A connector that automates something the platform forbids is not installed, however well it works.
7. Idempotency and pacing are respected: repeated grants and revokes are safe, pacing matches the platform's published limits, and the classifier maps the platform's rate-limit response to RateLimited with its retry-after.
8. Native payments are official-only. A community package that declares native_payments is refused at boot.

Submitting

Marketplace submission and per-connector pricing are not open yet. To get a package reviewed today, use Request a connector on the marketplace or write to [email protected] with the repository URL and the kit's report; Subscriby installs reviewed connectors itself.