# Government Data API & MCP Evidence Gateway (`civicdataforge/civicdataforge-evidence-gateway`) Actor

Official-source government data API and MCP gateway for STR permits, India CIN companies, restricted-party screening, EPA ECHO facilities, and China-facing intake.

- **URL**: https://apify.com/civicdataforge/civicdataforge-evidence-gateway.md
- **Developed by:** [Bryan](https://apify.com/civicdataforge) (community)
- **Categories:** Automation, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $70.00 / 1,000 evidence packets

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Government Data API & MCP Evidence Gateway

CivicDataForge routes official-source government data tasks for U.S. STR permits, India companies by CIN, restricted-party screening, EPA ECHO facilities, and rights-first China-facing intake into one receipt-bound packet. Use it through Apify API, MCP, or the six published task pages.

### Tasks

| Task | Minimum input | Downstream route | Boundary |
|---|---|---|---|
| `us_property_decision` | Address, exact supported city/county label, state | `str-permit-registry` address evidence | Exact label routing is not parcel-boundary resolution or legal permission |
| `india_company_evidence` | 21-character CIN | `india-company-registry` | Company evidence is not KYC or procurement eligibility |
| `india_supplier_pack` | CIN, purpose, optional rights-labeled GST/Udyam/IBBI evidence | `india-company-registry` plus minimized caller evidence | Missing registries remain missing; caller evidence is not silently promoted to official verification |
| `restricted_party_screening` | Name or identifier | `cross-border-restricted-party-evidence` | No result is legal clearance |
| `epa_facility_evidence` | FRS ID or bounded name/address | `epa-echo-facility-compliance` | No environmental safety or liability verdict |
| `china_counterparty_intake` | Chinese legal name, USCC, purpose, rights-labeled evidence | Optional U.S. ITA CSL screening | No China-native registry, UBO, or KYB claim |

### Output contract

Every packet carries:

- minimized subject identifiers;
- downstream Actor and evidence digest;
- source-rights ledger with artifact hashes but no supplied raw content;
- `EVIDENCE_FOUND`, `NO_PUBLISHED_MATCH`, `REVIEW_REQUIRED`, `SOURCE_UNAVAILABLE`, or `SCOPE_INCOMPLETE`;
- complete-scope flag;
- evidence-state and final packet receipts;
- baseline/change/incomplete-scope monitoring state;
- optional caller-policy transaction state that never issues legal permission;
- readable Markdown dossier in `EVIDENCE-DOSSIER.md`.

### Source-rights input

Each `evidence` item must include `label`, `sourceAuthority`, `accessMode`, and one of `content`, `contentBase64`, `payload`, or a precomputed `sha256`. Licensed sources must explicitly state whether processing, customer delivery, and cross-border delivery are allowed. The Actor hashes the supplied bytes and does not return or retain the raw content.

### Charging

Successful packets use the custom `evidence-packet` pay-per-event name. `SOURCE_UNAVAILABLE` packets are pushed without that event name, so a failed source cannot masquerade as paid evidence. The public price remains a separate Apify publication state and must be verified on the Actor listing after configuration.

### Responsible use

This gateway assembles and routes evidence. It does not approve, deny, clear, certify, or determine legality, KYC completion, procurement eligibility, credit, insurance, employment, housing, safety, sanctions compliance, or booking/listing authorization.

# Actor input Schema

## `task` (type: `string`):

The workflow to execute.

## `subject` (type: `object`):

Exact identifiers for the property, company, facility, or counterparty.

## `evidence` (type: `array`):

Optional evidence. Raw content is hashed and not copied into output. Each item must identify access and delivery rights.

## `purpose` (type: `string`):

Required for India supplier and China-facing workflows.

## `retentionDays` (type: `integer`):

Requested evidence-packet retention in days. Raw supplied content is not retained by this Actor.

## `previousReceiptHash` (type: `string`):

Optional prior receipt for change monitoring.

## `transactionGate` (type: `boolean`):

Adds a bounded transaction state; it never issues legal permission or eligibility.

## `screenRestrictedParties` (type: `boolean`):

Uses the existing source-bound U.S. restricted-party Actor. This is not China registry or UBO coverage.

## `batchReference` (type: `string`):

Optional customer-controlled reference copied into the bounded packet metadata.

## Actor input object example

```json
{
  "task": "us_property_decision",
  "subject": {
    "address": "1100 Briercliff Drive, Orlando, FL",
    "city": "Orlando",
    "state": "FL"
  },
  "evidence": [],
  "purpose": "property compliance research",
  "retentionDays": 0,
  "transactionGate": false,
  "screenRestrictedParties": true
}
```

# Actor output Schema

## `results` (type: `string`):

API URL for the default dataset packet produced by this run.

## `packet` (type: `string`):

API URL for the canonical receipt-bound gateway packet.

## `dossier` (type: `string`):

API URL for the Markdown evidence dossier.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "subject": {
        "address": "1100 Briercliff Drive, Orlando, FL",
        "city": "Orlando",
        "state": "FL"
    },
    "purpose": "property compliance research"
};

// Run the Actor and wait for it to finish
const run = await client.actor("civicdataforge/civicdataforge-evidence-gateway").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "subject": {
        "address": "1100 Briercliff Drive, Orlando, FL",
        "city": "Orlando",
        "state": "FL",
    },
    "purpose": "property compliance research",
}

# Run the Actor and wait for it to finish
run = client.actor("civicdataforge/civicdataforge-evidence-gateway").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "subject": {
    "address": "1100 Briercliff Drive, Orlando, FL",
    "city": "Orlando",
    "state": "FL"
  },
  "purpose": "property compliance research"
}' |
apify call civicdataforge/civicdataforge-evidence-gateway --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,civicdataforge/civicdataforge-evidence-gateway"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/y1xw8kPgXj1xIsJO1/builds/QEc2Rx6agOQ2Gvuvf/openapi.json