{
  "schema_version": "civicdataforge.buyer-outcomes.v1",
  "updated_at": "2026-08-22",
  "provider": "CivicDataForge",
  "position": "One submitted identifier becomes a source-bound answer with explicit scope and limits.",
  "shared_delivery": {
    "entry_pattern": "Start with one identifier, inspect the result and source evidence, then expand only if it fits the workflow.",
    "evidence_fields": [
      "official source identity",
      "query or run identity",
      "fetch time",
      "record fingerprint where supported",
      "coverage or source-reliability state",
      "responsible result semantics"
    ],
    "monitoring": "Accepted evidence can enter recurring comparison where the selected product supports complete-scope monitoring. Limited or failed pulls do not establish disappearance.",
    "privacy_posture": "The routes are for evidence and operational research, not contact-list or personal-lead harvesting.",
    "responsible_use": "Research and compliance support only. Do not use a result as the sole basis for an adverse or regulated eligibility decision; verify consequential facts with the issuing authority."
  },
  "routes": [
    {
      "id": "us-property-evidence",
      "market_entry": "United States",
      "buyer": "Property operations, insurance-review, PMS, analytics, and compliance-support teams",
      "job": "Determine what the supported official permit, license, or violation source publishes for a property and retain the source trail.",
      "minimum_input": "One property address plus the supported city or jurisdiction",
      "first_output": "EVIDENCE_FOUND, REVIEW_REQUIRED, or NO_PUBLISHED_MATCH (not found in the checked published source) with source, complete-scope status, observation time, match basis, fingerprints where present, and a decision receipt",
      "proof_available": [
        "source URL and jurisdiction",
        "retrieval time",
        "stable record evidence fields",
        "public sample and tested example",
        "complete-scope change monitoring for supported evidence records"
      ],
      "current_coverage": "30 supported U.S. STR jurisdictions, Florida DBPR lodging records across seven districts, and supported municipal violation sources",
      "start_url": "https://apify.com/civicdataforge/str-permit-registry?utm_source=civicdataforge&utm_medium=buyer_outcome&utm_campaign=address_evidence_20260822&utm_content=us_property",
      "evaluation_url": "https://civicdataforge.pages.dev/str-permit-sample",
      "paid_proof_url": "https://civicdataforge.pages.dev/permit-audit",
      "boundary": "A no-match means not found in the checked published source and scope. It does not prove illegality, nonexistence, or the absence of another authority's record."
    },
    {
      "id": "india-supplier-evidence",
      "market_entry": "India",
      "buyer": "Procurement, supplier onboarding, counterparty research, KYB-support, and data teams",
      "job": "Check whether an Indian company-master record matches the submitted CIN and preserve a source-bound company snapshot.",
      "minimum_input": "One exact Corporate Identity Number (CIN), or a registered name for bounded research",
      "first_output": "Official MCA company-master fields from the pinned OGD resource, a record fingerprint, source reliability, and optional exact-CIN GLEIF corroboration",
      "proof_available": [
        "pinned official resource identity",
        "query and record fingerprints",
        "source URL and retrieval time",
        "explicit rate-limit and partial-source failure states",
        "optional exact-CIN GLEIF corroboration"
      ],
      "current_coverage": "Company-master research fields published by the current pinned MCA Open Government Data resource",
      "start_url": "https://apify.com/civicdataforge/india-company-registry?utm_source=civicdataforge&utm_medium=buyer_outcome&utm_campaign=one_identifier_20260822&utm_content=india_supplier",
      "evaluation_url": "https://civicdataforge.pages.dev/india-company-data",
      "boundary": "Company-master evidence does not replace current regulator confirmation, consent-based document retrieval, sanctions screening, beneficial-ownership work, or a complete KYC decision."
    },
    {
      "id": "china-developer-route",
      "market_entry": "China-facing",
      "buyer": "Chinese-speaking developers, AI-agent builders, sourcing teams, and cross-border operators",
      "job": "Add source-bound U.S. property or India company evidence without maintaining each government-source adapter.",
      "minimum_input": "One target record type and jurisdiction, plus one sample property address or company CIN",
      "first_output": "A direct Actor, REST, or MCP integration route with the supported source and authority boundary stated before expansion",
      "proof_available": [
        "Simplified Chinese technical entry",
        "machine-readable product catalog",
        "Apify REST execution routes",
        "focused MCP tool entry points",
        "the same source and evidence boundaries as the underlying product"
      ],
      "current_coverage": "Chinese-language access to the existing U.S. and India evidence products; no claimed China-native company-registry product",
      "start_url": "https://civicdataforge.pages.dev/zh-cn?utm_source=civicdataforge&utm_medium=buyer_outcome&utm_campaign=one_identifier_20260822&utm_content=china_developer",
      "evaluation_url": "https://civicdataforge.pages.dev/zh-cn-developer.json",
      "boundary": "This is a China-facing distribution and integration route. It is not a claim of bulk access to, or resale rights for, a Chinese government registry."
    }
  ],
  "machine_catalog": "https://civicdataforge.pages.dev/api-catalog.json",
  "source_health": "https://civicdataforge.pages.dev/source-health.json",
  "support": "civicdataforgehq@gmail.com"
}