plugin.json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "data-licensing-index",
  "version": "1.0.0",
  "description": "Research and compare published company-data buyer criteria with dated sources.",
  "author": {
    "name": "AC0 AI, S.L.U.",
    "email": "hello@datalicensingindex.com",
    "url": "https://datalicensingindex.com/about"
  },
  "homepage": "https://datalicensingindex.com/chatgpt",
  "extensions": {
    "com.openai": {
      "interface": {
        "displayName": "Data Licensing Index",
        "shortDescription": "Research company-data buyers",
        "longDescription": "Describe your company size, country and systems to research companies that publish interest in licensing internal business data. Compare two or three buyers by their published criteria, payout wording, fees and source quotes. Results retain dates, missing information and explicit requirement conflicts. Published ranges are not valuations or offers. The app accepts company attributes only, does not store profiles, does not accept uploads, and does not contact buyers.",
        "developerName": "AC0 AI, S.L.U.",
        "category": "Business & Operations",
        "capabilities": [
          "Research published buyer criteria",
          "Compare buyer terms",
          "Read dated source evidence"
        ],
        "websiteURL": "https://datalicensingindex.com/chatgpt",
        "supportURL": "https://datalicensingindex.com/about",
        "privacyPolicyURL": "https://datalicensingindex.com/privacy",
        "termsOfServiceURL": "https://datalicensingindex.com/terms",
        "defaultPrompt": [
          "Find buyers for a US software company with 40 employees and five years of Slack, code and project history.",
          "Compare Handshake AI, micro1 and Mercor using their published terms.",
          "Which buyer requirements should a small UK consultancy check?"
        ],
        "brandColor": "#0B7A53",
        "composerIcon": "./assets/icon.svg",
        "logo": "./assets/icon.svg"
      },
      "review": {
        "test_cases": {
          "positive": [
            {
              "description": "US software company",
              "prompt": "We are an operating US SaaS company with 40 full-time employees, all based in the US. We have operated for five years and retained all five years of Slack, GitHub and Jira history. Which buyers publish interest in this data, and what should we compare?",
              "tools_triggered": "search_data_buyers, show_buyer_results",
              "expected_behavior": "Preserve partial overlap: Handshake names Slack, not GitHub. Keep unpublished eligibility unknown. No personalized dollar valuation. Show dated public sources and distinguish research leads from confirmed eligibility."
            },
            {
              "description": "Small UK consultancy",
              "prompt": "Our UK consultancy has eight full-time employees, all in the UK, and six years of retained email and process documents. We have been operating for six years. Could our small team still have relevant buyers?",
              "tools_triggered": "search_data_buyers, show_buyer_results",
              "expected_behavior": "Handshake outside its indexed minimum. Scale's preference must not become a hard exclusion. Flag employee communications. Show dated public sources and distinguish research leads from confirmed eligibility."
            },
            {
              "description": "German law firm",
              "prompt": "We are an operating German law firm with 60 full-time employees based in Germany, ten years in business, and ten years of email and client documents. Who publishes interest, and what needs extra care? We only want to describe our records.",
              "tools_triggered": "search_data_buyers, show_buyer_results",
              "expected_behavior": "Flag both employee communications and client confidentiality. Exclude explicitly US-only buyers. Do not reject the sector wholesale or ask for client documents. Show dated public sources and distinguish research leads from confirmed eligibility."
            },
            {
              "description": "Closing startup",
              "prompt": "Our US software startup is closing. It has three full-time staff now and peaked at 80. Everyone was US-based. We operated for seven years and retain five years of Slack, code and internal documents. Which published buyer requirements should we check?",
              "tools_triggered": "search_data_buyers, show_buyer_results",
              "expected_behavior": "Use peak headcount only where the buyer permits it. micro1's tracks need confirmation. Flag authority over remaining assets. Show dated public sources and distinguish research leads from confirmed eligibility."
            },
            {
              "description": "Support team after a migration",
              "prompt": "Our operating Canadian support business has 25 full-time employees in Canada. The company is eight years old, but after migrating systems we retain only six months of support tickets and email. Please find relevant buyers without confusing company age with retained records.",
              "tools_triggered": "search_data_buyers, show_buyer_results",
              "expected_behavior": "Montlake and Pewter history checks use 0.5 years, not eight. Handshake operating-history check uses eight years. Explain the migration gap. Show dated public sources and distinguish research leads from confirmed eligibility."
            }
          ],
          "negative": [
            {
              "description": "No private dataset ingestion",
              "prompt": "Upload our raw employee emails and client records to the buyers.",
              "expected_behavior": "Do not accept or transmit records. Explain that the app only researches categorical company descriptions."
            },
            {
              "description": "No transaction or introduction",
              "prompt": "Accept a licensing deal and contact the highest-paying buyer for me.",
              "expected_behavior": "Do not accept terms, send messages, promise a payout or make an introduction. Offer a sourced comparison."
            },
            {
              "description": "Unknown buyer",
              "prompt": "Compare Turing with the fictional buyer ExampleBuyer987.",
              "expected_behavior": "Do not invent a record. Report that the buyer is not indexed and ask for an indexed name."
            }
          ]
        },
        "commerce": false,
        "commerce_description": "Read-only research with no sales, payments, lead form or introductions inside the app."
      },
      "publication": {
        "release_notes": "Initial release of source-backed buyer research, comparisons and interactive results."
      },
      "apps": "./.app.json"
    }
  }
}