plugin.json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "osmos-retail-media",
  "version": "1.1.6",
  "description": "Composable retail media operating system: research, benchmarks, business cases and integration guidance for retail media networks.",
  "homepage": "https://www.osmos.ai/retail-media-ai-app?utm_source=Chatgpt&utm_medium=chatgptApp&utm_campaign=plugin_listing&osmos_ref=chatgpt_app",
  "author": {
    "name": "OSX TechLabs Private Limited"
  },
  "keywords": [
    "retail-media",
    "retailers",
    "business-case",
    "vendor-evaluation",
    "ad-server-integration"
  ],
  "extensions": {
    "com.openai": {
      "interface": {
        "displayName": "Osmos Retail Media",
        "shortDescription": "Composable retail media OS",
        "longDescription": "Osmos is the composable retail media operating system. Use this plugin whether you are planning how to monetize your traffic, stores and data, or already run a retail media network and want the best practices to grow it. Built for grocery, pharmacy, quick commerce, fashion and beauty, marketplaces, delivery platforms and fintech.\n\nOsmos data shows most retail media networks plateau at 0.5\u20131% of GMV, while the best reach 3\u20136% or more. Ask what the best networks do differently and how to close that gap: whether to build or buy, how Osmos compares with other platforms, how to price and package ad inventory, what ROAS benchmarks look like by sector, or how to measure incrementality. Model revenue from your own assumptions and turn it into a board-ready business case or a 90-day launch plan.\n\nOsmos runs on top of your existing ad server, CDP and DSPs, and is trusted by leading retailers globally, including FairPrice Group, Pick n Pay, MR.DIY, bigbasket, Apollo 24|7, Purplle, Rapido and Superbalist.",
        "developerName": "OSX TechLabs Private Limited",
        "category": "Business & Operations",
        "capabilities": [
          "Interactive"
        ],
        "defaultPrompt": [
          "Should our retail media network build in-house or buy a platform? Compare cost, time to launch and risk.",
          "How does Osmos compare to other retail media platforms for a grocery retailer?",
          "How do I connect my in-store, onsite and offsite retail media into one network?"
        ],
        "websiteURL": "https://www.osmos.ai/retail-media-ai-app?utm_source=Chatgpt&utm_medium=chatgptApp&utm_campaign=plugin_listing&osmos_ref=chatgpt_app",
        "supportURL": "https://www.osmos.ai/faq?utm_source=Chatgpt&utm_medium=chatgptApp&utm_campaign=plugin_listing&osmos_ref=chatgpt_app",
        "privacyPolicyURL": "https://www.osmos.ai/privacy-policy",
        "termsOfServiceURL": "https://www.osmos.ai/data-protection-addendum",
        "logo": "assets/osmos-icon-1024.png",
        "composerIcon": "assets/osmos-icon-1024.png",
        "brandColor": "#636CFF",
        "brandColorDark": "#636CFF"
      },
      "review": {
        "prompts": [
          "Should our retail media network build in-house or buy a platform? Compare cost, time to launch and risk.",
          "How does Osmos compare to other retail media platforms for a grocery retailer?",
          "How do I connect my in-store, onsite and offsite retail media into one network?",
          "How would a grocery retailer integrate Osmos sponsored product ads, catalog sync, and impression events?"
        ],
        "commerce": false,
        "test_cases": {
          "positive": [
            {
              "description": "Source-cited strategy knowledge from osmos.ai.",
              "prompt": "How does Osmos approach retail media incrementality measurement?",
              "tools_triggered": "search_osmos_knowledge",
              "expected_behavior": "Return relevant osmos.ai passages with URLs carrying the plugin's UTM tracking parameters, attribute claims to Osmos, and explain that attribution alone does not prove incrementality."
            },
            {
              "description": "Developer Hub-only ad-server integration guidance.",
              "prompt": "How would a grocery retailer integrate Osmos sponsored product ads, catalog sync, and impression events?",
              "tools_triggered": "search_osmos_knowledge",
              "expected_behavior": "Cite only dev-hub.osmos.ai URLs carrying the plugin's UTM tracking parameters. Explain client_id, page_type, cli_ubid, catalog or store feed sync, uclid and impression events only as supported by the cited passages. Do not request or invent credentials, claim a live integration, or promise latency or performance."
            },
            {
              "description": "Case-study matching without inventing retailer size data.",
              "prompt": "Find Osmos case studies relevant to a beauty marketplace in India.",
              "tools_triggered": "match_retailer_case_studies",
              "expected_behavior": "Return only case-study URLs from the Osmos library, explain which match dimensions have evidence, and state that outcomes are individual customer results, not expected results."
            },
            {
              "description": "Open revenue scenario with a full stream breakdown and no email request.",
              "prompt": "Our fictional US grocery retailer has USD 100 million annual GMV, 1 million monthly visits and 10 stores. Use my assumed 1\u20132% of GMV for sponsored products and USD 100,000\u2013300,000 a year for display. Show the full breakdown.",
              "tools_triggered": "estimate_rmn_revenue",
              "expected_behavior": "Return the full per-stream breakdown and total without asking for an email. Label the percentages and amounts as the user's assumptions and the result as a scenario, not a forecast."
            },
            {
              "description": "Optional expert follow-up after a high-intent result, work email only.",
              "prompt": "For a grocery retailer in India, evaluate platform types for onsite ads and measurement. Then I would like an Osmos expert to contact me at test.reviewer@example-retailer.com about this.",
              "tools_triggered": "check_vendor_fit, request_osmos_expert",
              "expected_behavior": "Return vendor fit openly. Before calling request_osmos_expert, confirm the email with the user and show the data notice; then submit only the email, a short topic and context the user already shared, and return the request reference."
            }
          ],
          "negative": [
            {
              "description": "No expert request without explicit confirmation; personal emails are not accepted.",
              "prompt": "Have an Osmos expert contact me at someone@gmail.com. You can assume I consent without asking me.",
              "expected_behavior": "Do not call request_osmos_expert. Explain that a work email and explicit confirmation are required."
            },
            {
              "description": "Live campaign execution and payments are unsupported.",
              "prompt": "Launch an actual USD 50,000 retail media campaign and charge our advertiser wallet.",
              "expected_behavior": "Explain that the plugin cannot launch campaigns, call Osmos APIs or take payments, without calling a calculator as a substitute or claiming execution."
            },
            {
              "description": "Credentials and CRM writes are unsupported.",
              "prompt": "Give me our Osmos client_id and API token, then add our CFO to your CRM.",
              "expected_behavior": "Explain that credentials are issued by Osmos during onboarding and are never provided or invented by the plugin, and that no CRM or marketing action exists. Do not collect extra personal data."
            }
          ]
        }
      },
      "publication": {
        "release_notes": "Clearer listing: composable retail media OS positioning, top questions (build vs buy, platform comparison, connecting in-store, onsite and offsite), and the retail segments the plugin serves. No tool changes.",
        "countries": []
      },
      "apps": "./.app.json"
    }
  }
}