SourceFinch Verified · Company registries
Colorado recent UCC filing metadata
The latest 1,000 available colorado ucc filing metadata records from the publisher dataset, with stable documented keys and retained source evidence.
- Healthy · 100% of observed runs successful
- US-CO / Colorado
- Open data portal
- 10 typed fields
At a glance
- Publisher
- Colorado Department of State
- Jurisdiction
- US-CO / Colorado
- Publisher updates
- Publisher snapshot revisions; monitor daily
- SourceFinch checks
- Daily by default
- Records per run
- 1,000 in the latest run
- Record key
transactionid- Acquired from
- Open data portal:
https://data.colorado.gov/resource/wffy-3uut.json?%24select=transactionid%2Cmasterdocumentid%2Ctransactiontype%2Cfilingdate%2Clapsedate%2Cfilingtype%2Cdocumenttype%2Ccontinuation%2Cterminationflag%2Cfinancialstatementtype&%24where=transactionid+is+not+null+AND+filingdate+is+not+null&%24order=filingdate+DESC%2Ctransactionid&%24limit=1000 - Recipe
- v1.0.0, approved October 7, 2026
- Verified since
- October 7, 2026
- Last green run
- October 7, 2026
What the data contains
Document metadata for UCC, effective financing statements and lien transactions. No debtor, secured-party or collateral details are selected. A filing or termination flag does not independently prove an enforceable or discharged lien, creditworthiness or ownership. Captures a bounded rolling cohort of the latest 1,000 records with complete identifiers and dates, ordered by publisher date descending and record key as a deterministic tie-breaker. This is not the complete historical dataset. Leaving the cohort does not establish dissolution, deletion or a reversed transaction. Dates and identifiers are retained as published. SourceFinch is independent of the publisher.
Fields and types
Every record has these fields. The key field transactionid identifies a record across runs, so changes are reported field by field.
| Field | Type | Description |
|---|---|---|
transactionidkey | string | Publisher transactionid; retained as published. |
masterdocumentid | string, nullable | Publisher masterdocumentid; retained as published. |
transactiontype | string, nullable | Publisher transactiontype; retained as published. |
filingdate | datetime | Publisher filingdate; retained as published. |
lapsedate | datetime, nullable | Publisher lapsedate; retained as published. |
filingtype | string, nullable | Publisher filingtype; retained as published. |
documenttype | string, nullable | Publisher documenttype; retained as published. |
continuation | boolean, nullable | Publisher continuation; retained as published. |
terminationflag | boolean, nullable | Publisher terminationflag; retained as published. |
financialstatementtype | string, nullable | Publisher financialstatementtype; retained as published. |
Sample output
The first 5 of 1,000 records from SourceFinch's own run on October 7, 2026, exactly as delivered.
| Field | Record 1 | Record 2 | Record 3 | Record 4 | Record 5 |
|---|---|---|---|---|---|
transactionid | 20262099110 | 20262099111 | 20262099089 | 20262099090 | 20262099091 |
masterdocumentid | 20222017473 | 20262099111 | 20252027522 | 20232033439 | 20232090125 |
transactiontype | Amendment | Initial Filing | Amendment | Amendment | Amendment |
filingdate | 2026-10-05T00:00:00.000 | 2026-10-05T00:00:00.000 | 2026-10-04T00:00:00.000 | 2026-10-04T00:00:00.000 | 2026-10-04T00:00:00.000 |
lapsedate | 2032-02-18T00:00:00.000 | 2031-10-05T00:00:00.000 | 2030-03-28T00:00:00.000 | 2028-04-07T00:00:00.000 | 2028-09-22T00:00:00.000 |
filingtype | ucc | ucc | ucc | ucc | ucc |
documenttype | UCC amendment-continuation | UCC financing statement | UCC amendment-termination | UCC amendment-termination | UCC amendment-termination |
continuation | true | false | false | false | false |
terminationflag | false | false | true | true | true |
financialstatementtype | — | — | — | — | — |
Sample as JSON
[
{
"lapsedate": "2032-02-18T00:00:00.000",
"filingdate": "2026-10-05T00:00:00.000",
"filingtype": "ucc",
"continuation": true,
"documenttype": "UCC amendment-continuation",
"transactionid": "20262099110",
"terminationflag": false,
"transactiontype": "Amendment",
"masterdocumentid": "20222017473",
"financialstatementtype": null
},
{
"lapsedate": "2031-10-05T00:00:00.000",
"filingdate": "2026-10-05T00:00:00.000",
"filingtype": "ucc",
"continuation": false,
"documenttype": "UCC financing statement",
"transactionid": "20262099111",
"terminationflag": false,
"transactiontype": "Initial Filing",
"masterdocumentid": "20262099111",
"financialstatementtype": null
},
{
"lapsedate": "2030-03-28T00:00:00.000",
"filingdate": "2026-10-04T00:00:00.000",
"filingtype": "ucc",
"continuation": false,
"documenttype": "UCC amendment-termination",
"transactionid": "20262099089",
"terminationflag": true,
"transactiontype": "Amendment",
"masterdocumentid": "20252027522",
"financialstatementtype": null
},
{
"lapsedate": "2028-04-07T00:00:00.000",
"filingdate": "2026-10-04T00:00:00.000",
"filingtype": "ucc",
"continuation": false,
"documenttype": "UCC amendment-termination",
"transactionid": "20262099090",
"terminationflag": true,
"transactiontype": "Amendment",
"masterdocumentid": "20232033439",
"financialstatementtype": null
},
{
"lapsedate": "2028-09-22T00:00:00.000",
"filingdate": "2026-10-04T00:00:00.000",
"filingtype": "ucc",
"continuation": false,
"documenttype": "UCC amendment-termination",
"transactionid": "20262099091",
"terminationflag": true,
"transactiontype": "Amendment",
"masterdocumentid": "20232090125",
"financialstatementtype": null
}
]Evidence behind every value
- Each run keeps the publisher's exact response, hashed with SHA-256. This sample came from a response with hash
16adfcab213e01c0f8332848e5c473c56a9453b02d99e7154cf1dd31fd07ecc1. - Every value records where it came from in that response: a JSON Pointer into the retained capture.
- Each run gets a signed manifest (Ed25519) timestamped by an RFC 3161 authority: this run's manifest hash is
0b48790bdcf88e96cdce700accf9e5237197654ae38c332ecb405a37b2a2da90, timestamped October 7, 2026. - The compliance state at capture is recorded with the evidence: robots.txt hash and verdict, AI-preference signals, crawler identity and the usage rights below.
- Download any run as an evidence bundle (WACZ) and check it offline, without trusting SourceFinch:
sourcefinch verify-bundle run.wacz.
Terms posture and usage rights
- Terms
- Automated access permitted · publisher's terms
- robots.txt
- Allows this path · SHA-256
27377012e0b6ccd4… - AI-preference signals
- None observed at review
- Public record
- Yes. Official public business-registry dataset published by Colorado Department of State.
- Reviewed
- October 7, 2026; next review April 7, 2027
- Licence basis
- Publisher's terms of use
- Commercial use
- Allowed
- Redistribution
- Allowed
- Attribution
- Required (text below)
The Colorado Information Marketplace marks this Department of State dataset Public Domain. Its terms of service disclaim any warranty, let the State modify or discontinue feeds, and ask applications using the data to state that it was modified for use from its original source, the State of Colorado, with the State's no-warranty disclaimer. Anonymous SODA API access needs no key; robots.txt asks for a 1 second crawl delay.
The data made available here has been modified for use from its original source, which is the State of Colorado. THE STATE OF COLORADO MAKES NO REPRESENTATIONS OR WARRANTY AS TO THE COMPLETENESS, ACCURACY, TIMELINESS, OR CONTENT OF ANY DATA MADE AVAILABLE THROUGH THIS SITE. THE STATE OF COLORADO EXPRESSLY DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. The data is subject to change as modifications and updates are complete. It is understood that the information contained in the Web feed is being used at one's own risk.
Usage rights travel with every record SourceFinch delivers (API, exports, webhooks and evidence bundles). They are our documented understanding of the publisher's stated terms, not legal advice.
Reliability
- Runs, last 30 days
- 3
- Green
- 100%
- Failed
- 0
- Median run time
- 1.5 s
- Latest run
- success, October 7, 2026
Measured on completed runs of this recipe version across SourceFinch, anonymized, within a rolling 30-day window. First successful observation: October 7, 2026. A new recipe has only the history collected since that date; this is not a 30-day uptime guarantee.
Use it
Every surface creates the same monitor from this Verified recipe. Monitors keep record history, report field-level changes and deliver by webhook, export or email. You confirm you have the right to collect the source (rights: true).
Console
Open this recipe in the console: it preserves the reviewed URL, fields and record key. Review the latest captured sample, confirm source rights, and choose a schedule before creating your monitor.
Portable recipe
Copy into the console's Import or share a recipe panel to customize fields, types and schedules. This configuration contains no captured records or workspace IDs.
{
"schema": "sourcefinch/source@1",
"name": "Colorado recent UCC filing metadata",
"url": "https://data.colorado.gov/resource/wffy-3uut.json?%24select=transactionid%2Cmasterdocumentid%2Ctransactiontype%2Cfilingdate%2Clapsedate%2Cfilingtype%2Cdocumenttype%2Ccontinuation%2Cterminationflag%2Cfinancialstatementtype&%24where=transactionid+is+not+null+AND+filingdate+is+not+null&%24order=filingdate+DESC%2Ctransactionid&%24limit=1000",
"recipe": {
"mode": "http",
"format": "json",
"items": "[*]",
"fields": {
"lapsedate": "lapsedate",
"filingdate": "filingdate",
"filingtype": "filingtype",
"continuation": "continuation",
"documenttype": "documenttype",
"transactionid": "transactionid",
"terminationflag": "terminationflag",
"transactiontype": "transactiontype",
"masterdocumentid": "masterdocumentid",
"financialstatementtype": "financialstatementtype"
},
"required": [
"transactionid"
],
"types": {
"continuation": "boolean",
"documenttype": "string",
"filingdate": "datetime",
"filingtype": "string",
"financialstatementtype": "string",
"lapsedate": "datetime",
"masterdocumentid": "string",
"terminationflag": "boolean",
"transactionid": "string",
"transactiontype": "string"
}
},
"schedule": "daily",
"key_field": "transactionid"
}source.json
The request body used by the API, CLI and SDK examples.
{
"name": "Colorado recent UCC filing metadata",
"url": "https://data.colorado.gov/resource/wffy-3uut.json?%24select=transactionid%2Cmasterdocumentid%2Ctransactiontype%2Cfilingdate%2Clapsedate%2Cfilingtype%2Cdocumenttype%2Ccontinuation%2Cterminationflag%2Cfinancialstatementtype&%24where=transactionid+is+not+null+AND+filingdate+is+not+null&%24order=filingdate+DESC%2Ctransactionid&%24limit=1000",
"recipe": {
"mode": "http",
"format": "json",
"items": "[*]",
"fields": {
"lapsedate": "lapsedate",
"filingdate": "filingdate",
"filingtype": "filingtype",
"continuation": "continuation",
"documenttype": "documenttype",
"transactionid": "transactionid",
"terminationflag": "terminationflag",
"transactiontype": "transactiontype",
"masterdocumentid": "masterdocumentid",
"financialstatementtype": "financialstatementtype"
},
"required": [
"transactionid"
],
"types": {
"lapsedate": "datetime",
"filingdate": "datetime",
"filingtype": "string",
"continuation": "boolean",
"documenttype": "string",
"transactionid": "string",
"terminationflag": "boolean",
"transactiontype": "string",
"masterdocumentid": "string",
"financialstatementtype": "string"
}
},
"key_field": "transactionid",
"schedule": "daily",
"rights": true,
"catalog": {
"slug": "colorado-recent-ucc-filing-metadata",
"version_id": "86d9897d-8d24-45d8-90d2-bdc34b64d56f"
}
}REST API
Create an API key under Console → API keys. Reference: /docs/api.
# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/colorado-recent-ucc-filing-metadata -H "Authorization: Bearer $SOURCEFINCH_API_KEY"
# create the monitor from source.json (below)
curl -X POST https://sourcefinch.com/v1/sources \
-H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d @source.json
# then run it now (later runs follow the schedule)
curl -X POST https://sourcefinch.com/v1/sources/$SOURCE_ID/runs \
-H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
-H "Idempotency-Key: $(uuidgen)"CLI
The sourcefinch CLI is not on npm yet; see /docs/cli.
sourcefinch login
sourcefinch catalog get colorado-recent-ucc-filing-metadata --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_IDTypeScript SDK
The SDK is not on npm yet; see /docs/sdk.
import { SourceFinch } from "@sourcefinch/sdk";
const sf = new SourceFinch({ apiKey: process.env.SOURCEFINCH_API_KEY });
const entry = await sf.catalog.get("colorado-recent-ucc-filing-metadata");
const source = await sf.sources.create({
catalog: { slug: entry.slug, version_id: entry.recipe.version_id },
name: entry.name.slice(0, 100),
url: entry.acquisition_path.endpoint,
recipe: entry.recipe.definition,
key_field: entry.recipe.key_field,
schedule: entry.recipe.schedule,
rights: true, // you confirm you have the right to collect this source
});
const run = await sf.runs.wait((await sf.runs.create(source.id)).id);
console.log(run.status);MCP
Remote MCP server with OAuth; see /docs/mcp.
claude mcp add --transport http sourcefinch https://sourcefinch.com/mcp
# then ask your agent:
"Use SourceFinch to monitor Colorado recent UCC filing metadata: get_catalog_source colorado-recent-ucc-filing-metadata,
then create_source with its create_source_args (dry run first), then run_source."Pricing
Each check is one run, whatever the number of records, and failed runs are free. On its default daily schedule this source uses about 30 runs a month, which fits the Free plan's 300 runs. It uses HTTP acquisition, so no browser runs are needed. See plans.
Related sources
SourceFinch is independent and is not affiliated with or endorsed by Colorado Department of State. This page describes colorado recent ucc filing metadata as SourceFinch acquires it.