Developer path

One address in. One source-bound decision out.

Call the live STR Permit Registry Actor directly from any HTTP client. Address evidence mode evaluates the complete selected publisher query and returns one decision per submitted address.

Request

Use your own Apify API token in the Authorization header. The endpoint accepts one supported city and 1-25 addresses.

curl -X POST \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "outputMode": "address_evidence",
    "cities": ["orlando"],
    "addresses": [
      "1100 Briercliff Drive, Orlando, FL"
    ]
  }' \
  "https://api.apify.com/v2/actors/civicdataforge~str-permit-registry/run-sync-get-dataset-items"

Decision contract

EVIDENCE_FOUND: exact normalized address evidence exists in the selected published source.
NO_PUBLISHED_MATCH: no exact match was found in the complete selected publisher query.
REVIEW_REQUIRED: the input is invalid or a similar candidate needs human review.

Every row carries scope_completeness, observed_at, source_url, match detail, and a decision_receipt_hash.

Evidence boundary: NO_PUBLISHED_MATCH does not prove illegality, ineligibility, or absence from every government system. If the official source cannot be evaluated completely, the run fails instead of manufacturing a negative result.

Choose the commercial path

Use the live Actor for machine self-service. Choose the $4.99 Permit Evidence Audit for guided intake and a private, automatically prepared evidence bundle for up to 25 addresses in one supported jurisdiction. Choose $19.99/month for weekly checks, change history and private dashboard alerts on the same bounded portfolio. Ambiguous matches remain review candidates; neither option is a legal determination.

Open the live Actor

Receipt-bound evidence in your automation

Use the Evidence Gateway when your workflow needs a combined, source-bound evidence packet. Your existing HTTP client can use your own Apify credential, kept in its secret store. Review the Actor tariff and set an explicit run-cost ceiling before starting. Start once and retain the run ID; retries should read that run, not buy a replacement.

The Gateway's authoritative result is GATEWAY-PACKET in the run's default key-value store, not the STR dataset described above. Check the Gateway Actor identity, stored INPUT, and packet receipt bindings before accepting the result. Preserve its source dates, completeness and decision state.

With a CivicDataForge first-party key, use our MCP endpoint. Recover a pending call by repeating the original tools/call body and Idempotency-Key. The service reads the bound run and does not start another one. A lost start with no confirmed run ID requires reconciliation; UNRESOLVED is not delivery. First-party keys do not grant Apify account or storage access. See the agent catalog for supported tasks and routes.