# Alaska Recorder UCC & Lien Filings: Debtors & Lenders (`lienintel/alaska-recorder-ucc-lien-filings`) Actor

Search Alaska's statewide recorder index by debtor, lender or lien claimant. Get UCC filings, liens, tax liens and mortgages from every recording district with parties, addresses, amounts, legal descriptions and document links in clean JSON.

- **URL**: https://apify.com/lienintel/alaska-recorder-ucc-lien-filings.md
- **Developed by:** [LienIntel - UCC & Secured Lending Intelligence.](https://apify.com/lienintel) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $15.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

[![Alaska Recorder UCC & Lien Filings: Debtors & Lenders](https://scrapers.lat/banners/alaska-recorder-ucc-lien-filings.png)](https://console.apify.com/actors/znaSzcElM6DHGZ9j4/input)

## Alaska Recorder UCC & Lien Filings: Debtors & Lenders

Search **Alaska's statewide recording index:** Anchorage, Fairbanks, Juneau, Palmer, Kenai, Ketchikan, Sitka, Kodiak, Valdez, Nome, Bethel and every other recording district, plus the UCC Central File, by debtor, secured party, lender or lien claimant. Get the parties, addresses, lien amount, recording date, document number, legal description and document link as flat rows.

Alaska's Recorder's Office publishes one free public index for recordings across the state. This actor turns that index into structured rows.

Here is one real record from this actor.

```json
{
  "error": null,
  "record_id": "301-2026-035976-0",
  "document_number": "2026-035976-0",
  "document_year": "2026",
  "document_serial": "035976",
  "document_suffix": "0",
  "district_code": "301",
  "district_name": "Anchorage",
  "doc_type": "CLAIM OF LIEN",
  "index_code": "LI",
  "index_name": "LIENS",
  "index_full": "LI - LIENS",
  "filing_type": "lien",
  "filing_type_label": "Liens",
  "lien_category": "lien",
  "lien_category_label": "Mechanics / general lien",
  "is_release": false,
  "recorded_date": "2026-10-07",
  "recorded_time": "08:03 AM",
  "record_status": null,
  "pages": 2,
  "amount": 703.5,
  "amount_raw": "$703.50",
  "debtor_name": "JEAN GRIFFITH KATHRYN MOLLY",
  "debtor_names": "JEAN GRIFFITH KATHRYN MOLLY; GRIFFITH KATHRYN MOLLY JEAN; KINGS KATHRYN J",
  "debtor_count": 3,
  "debtor_address": null,
  "debtor_addresses": null,
  "secured_party_name": "CHINOOK PLACE CONDOMINIUM ASSOCIATION",
  "secured_party_names": "CHINOOK PLACE CONDOMINIUM ASSOCIATION",
  "secured_party_count": 1,
  "secured_party_address": null,
  "secured_party_addresses": null,
  "grantor_name": "JEAN GRIFFITH KATHRYN MOLLY",
  "grantor_names": "JEAN GRIFFITH KATHRYN MOLLY; GRIFFITH KATHRYN MOLLY JEAN; KINGS KATHRYN J",
  "grantor_count": 3,
  "grantee_name": "CHINOOK PLACE CONDOMINIUM ASSOCIATION",
  "grantee_names": "CHINOOK PLACE CONDOMINIUM ASSOCIATION",
  "grantee_count": 1,
  "party_direction": "grantor_debtor",
  "party_count": 4,
  "legal_description": "apt/unit: 6 | plat: 79-8",
  "parcel_number": null,
  "plat": "79-8",
  "lot": null,
  "block": null,
  "tract": null,
  "unit": "6",
  "section": null,
  "township": null,
  "range": null,
  "meridian": null,
  "subdivision": null,
  "location": null,
  "associated_document": null,
  "comments": null,
  "document_url": "https://dnr.alaska.gov/ssd/recoff/search/DocDisplay?district=301&selecteddoc=20260359760",
  "image_url": "https://dnr.alaska.gov/docimages/Release_Images_2026_10/301-2026-035976-0.TIF",
  "matched_name": "CHINOOK PLACE CONDOMINIUM ASSOCIATION",
  "source": "Alaska Recorder's Office public recording index",
  "source_page": "https://dnr.alaska.gov/ssd/recoff/Search",
  "source_url": "https://dnr.alaska.gov/ssd/recoff/Search",
  "search_role": "name",
  "search_term": "CHINOOK PLACE CONDOMINIUM ASSOCIATION",
  "search_terms": "types=liens; district=ALL; 2000-01-01..2026-10-21",
  "observed_at": "2026-10-21T07:23:32.080Z",
  "state": "AK"
}
```

**[Input](https://apify.com/lienintel/alaska-recorder-ucc-lien-filings/input-schema) | [Output](https://apify.com/lienintel/alaska-recorder-ucc-lien-filings/output-schema) | [Pricing](https://apify.com/lienintel/alaska-recorder-ucc-lien-filings/pricing)**

![Coverage](https://img.shields.io/badge/Coverage-Alaska-blue)
![Output](https://img.shields.io/badge/Output-JSON%20%7C%20CSV%20%7C%20Excel-orange)
![Billing](https://img.shields.io/badge/Billing-Pay%20per%20result-brightgreen)

### Table of contents

- [What you get](#what-you-get)
- [Input and filters](#input-and-filters)
- [Use cases](#use-cases)
- [Coverage and freshness](#coverage-and-freshness)
- [Pricing](#pricing)
- [Comparison with other Apify actors](#comparison-with-other-apify-actors)
- [Related LienIntel actors](#related-lienintel-actors)
- [FAQ](#faq)
- [Run it through the Apify API](#run-it-through-the-apify-api)

### What you get

- **Debtor and secured-party parties:** every indexed party with its role and address. `debtor_name` and `secured_party_name` are derived for quick filtering, and `party_direction` tells you whether the document uses debtor/secured, grantor/grantee or assignor/assignee roles.
- **UCC filing type:** `ucc_initial`, `ucc_fixture`, `continuation`, `amendment`, `assignment`, `termination` and the other UCC index codes, alongside the recorder's own document description and code.
- **Liens and tax liens:** mechanics and general liens (`LI`), tax liens (`TL`), deeds of trust (`MX`) and mortgages (`M`), including the published lien amount and the claimant.
- **Recording district:** the district code and name, so you can separate UCC Central filings from local recordings in Anchorage, Fairbanks, Juneau and the other districts.
- **Recording date and time:** normalized to `YYYY-MM-DD` plus the published time.
- **Document number and chain:** the recorder's document number and the associated or parent document, so you can connect a continuation or termination to its initial filing.
- **Legal context:** legal description, plat, lot, block, tract, unit, section, township, range, meridian and subdivision when the recorder publishes them.
- **Release flag:** terminations, releases and satisfactions are marked so you can separate new liens from payoffs.
- **Document links:** the public detail page and, when available, the public document image.
- **Source traceability:** source, search term, matched name and observation timestamp on every row.

Each record can carry these 67 fields. A field the source does not publish for a record comes back as `null`.

| Field | Type | Description |
|---|---|---|
| `record_id` | string | Unique record key: recording district plus document number |
| `document_number` | string | Recorder document number, for example 2026-000003-0 |
| `document_year` | string | Four-digit document year |
| `document_serial` | string | Six-digit document serial number |
| `document_suffix` | string | Single-digit document suffix |
| `district_code` | string | Alaska recording district code, for example 301 or 500 (UCC Central) |
| `district_name` | string | Recording district name, for example Anchorage or UCC Central |
| `doc_type` | string | Recorder description of the instrument, for example FINANCING STATEMENT or CLAIM OF LIEN |
| `index_code` | string | Recorder index code, for example FS, CO, AM, AS, TS, LI or TL |
| `index_name` | string | Recorder index name, for example FINANCING STATEMENT or LIENS |
| `index_full` | string | Full index label as published, for example FS - FINANCING STATEMENT |
| `filing_type` | string | Normalized filing type: ucc_initial, ucc_initial_assigned, ucc_fixture, continuation, amendment, assignment, information_statement, termination, release, partial_release, termination_bankruptcy, manufactured_home, lien, filed_lien, tax_lien, deed_of_trust, mortgage, deed, miscellaneous, mining, monument_record, plat, power_of_attorney, public_recreational_easement, record_survey, transmitting_utility or void |
| `filing_type_label` | string | Human-readable filing type label |
| `lien_category` | string | Normalized category: ucc, lien, tax_lien, mortgage or other |
| `lien_category_label` | string | Human-readable category label |
| `is_release` | boolean | True for terminations, releases, partial releases and satisfactions |
| `recorded_date` | string | Recording date in YYYY-MM-DD format |
| `recorded_time` | string | Recording time as published, for example 08:14 AM |
| `record_status` | string | Recorder record status: ACTIVE, INACTIVE, LAPSED or another published status |
| `pages` | integer | Number of pages in the recorded document |
| `amount` | number | Lien or document amount as a number when the recorder publishes one |
| `amount_raw` | string | Amount as published, for example $1,483.31 |
| `debtor_name` | string | Primary debtor or grantor name |
| `debtor_names` | string | All debtor or grantor names, joined with semicolons |
| `debtor_count` | integer | Number of debtor or grantor names |
| `debtor_address` | string | Primary debtor or grantor address |
| `debtor_addresses` | string | All debtor or grantor addresses, joined with semicolons |
| `secured_party_name` | string | Primary secured party, lender or lien claimant name |
| `secured_party_names` | string | All secured party, lender or lien claimant names, joined with semicolons |
| `secured_party_count` | integer | Number of secured party, lender or lien claimant names |
| `secured_party_address` | string | Primary secured party, lender or lien claimant address |
| `secured_party_addresses` | string | All secured party, lender or lien claimant addresses, joined with semicolons |
| `grantor_name` | string | Primary grantor name when the recorder uses grantor/grantee roles |
| `grantor_names` | string | All grantor names, joined with semicolons |
| `grantor_count` | integer | Number of grantor names |
| `grantee_name` | string | Primary grantee name when the recorder uses grantor/grantee roles |
| `grantee_names` | string | All grantee names, joined with semicolons |
| `grantee_count` | integer | Number of grantee names |
| `party_direction` | string | Party convention on the document: debtor_secured, secured_party_transfer, grantor_debtor or unknown |
| `party_count` | integer | Total number of indexed parties on the document |
| `legal_description` | string | Legal description fields published by the recorder, joined with pipe separators |
| `parcel_number` | string | Parcel number when the recorder publishes one |
| `plat` | string | Plat reference when published |
| `lot` | string | Lot reference when published |
| `block` | string | Block reference when published |
| `tract` | string | Tract reference when published |
| `unit` | string | Apartment or unit reference when published |
| `section` | string | Section reference when published |
| `township` | string | Township reference when published |
| `range` | string | Range reference when published |
| `meridian` | string | Meridian reference when published |
| `subdivision` | string | Subdivision or addition reference when published |
| `location` | string | Location reference when published |
| `associated_document` | string | Associated or parent document number, for example the initial financing statement for a continuation or termination |
| `comments` | string | Recorder comments, including indexing notes |
| `document_url` | string | Public document detail page |
| `image_url` | string | Public document image URL when the recorder publishes one |
| `matched_name` | string | Exact indexed name whose document list produced this record, in name-search mode |
| `source` | string | Public source name |
| `source_page` | string | Public search page |
| `source_url` | string | Public source URL |
| `search_role` | string | How the record matched: name or browse |
| `search_term` | string | Party name that matched this record, in name-search mode |
| `search_terms` | string | Filters used for the run |
| `observed_at` | string | Timestamp when the record was observed |
| `state` | string | US state; always AK |
| `error` | string | Error message when no records were returned or the run failed; error records are not charged |

### Input and filters

All inputs are optional.

| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `searchNames` | array | no | (none) | Names to search, up to 20. Partial names are supported, for example SMITH, WELLS FARGO or CHINOOK PLACE CONDOMINIUM ASSOCIATION. Each name is searched separately and results are deduplicated. |
| `documentTypes` | array | no | `["ucc", "liens"]` | Document families to include. Allowed values: ucc, liens, tax_liens, mortgages, all. The default includes UCC filings, liens and tax liens. |
| `district` | string | no | `"ALL"` | Alaska recording district or UCC Central. Use ALL to search every district. Values: `ALL`, `500`, `301`, `401`, `101`, `311`, `302`, `303`, `102`, `103`, `314`, `318`, `201`, `402`, and more. |
| `dateFrom` | string | no | (none) | Earliest recorded date in YYYY-MM-DD format. Leave empty for the last 7 days when no search term is given, or the last 10 years when searching by name. |
| `dateTo` | string | no | (none) | Latest recorded date in YYYY-MM-DD format. Leave empty for today. |
| `maxResults` | integer | no | `25` | Maximum number of unique recorded documents to return and charge. Free Apify users receive up to 10 results per run. |

A working example to paste into the Input tab:

```json
{
  "searchNames": [
    "CHINOOK PLACE CONDOMINIUM ASSOCIATION"
  ],
  "documentTypes": [
    "liens"
  ],
  "dateFrom": "2000-01-01",
  "dateTo": "2026-10-21",
  "maxResults": 2,
  "district": "ALL"
}
```

### Use cases

- Follow liens by recording district, from Anchorage to Fairbanks, with `district_name`, or look up a claimant's filing statewide.
- **MCA and ISO brokers:** find Alaska businesses with new secured filings and identify the incumbent funder.
- **Equipment finance, factoring and commercial lenders:** monitor competitor lending and new borrower activity.
- **Credit, collections and recovery teams:** spot new secured positions and releases.
- **Construction, solar, HVAC and home-improvement finance teams:** local lien recordings show the claimant, the property and the amount.

### Coverage and freshness

- **Jurisdiction:** the State of Alaska, all recording districts plus the UCC Central File.
- Select a specific district to browse that district.
- **Records:** UCC financing statements, fixture statements, continuations, amendments, assignments, terminations, releases, mechanics and general liens, tax liens, mortgages, deeds of trust and other recorded instruments.
- The recorder posts recordings in batches, so the most recent days may not yet appear. Use the recorded-date range that fits your use case.
- **Not included:** documents the recorder does not publish party detail for, child-support lien assertions, and voided records.
- **Not included:** certified copies or the paid certified-search cart. Data comes from the free public index only.

### Pricing

This actor uses pay-per-event pricing. These are the current Apify prices, read on 2026-11-06.

| Event | Price | When it is charged |
|---|---|---|
| `result` | $0.015 | Each record delivered to your dataset |
| `apify-actor-start` | $0.003 | When a run starts, once per GB of run memory with a minimum of one |

At the default 512 MB, a run that delivers 100 records costs $1.503.

- Apify asks for a maximum spend of at least $0.018 per run on this actor.
- Accounts on the free Apify plan receive up to 10 results per run.
- If nothing matches or the source fails, you get one row with an `error` field and no `result` charge. The start event still applies to the run.
- Set a maximum cost per run and the actor stops delivering results when it reaches that limit.

### Comparison with other Apify actors

No dedicated actor for this source on the Apify Store as of November 2026. We searched the public Store on 2026-11-06 with queries including "Alaska recorder", "Alaska lien" and "Alaska ucc", and we reviewed the listings for this source and data type. Broader actors exist: `shelvick/property-deed-records` searches deed and lien records from county recorder indexes. Their listings do not name this source, so we could not confirm that they cover it. Store listings change, so run the same search before you rely on this.

### Related LienIntel actors

Other public LienIntel actors for the same buyer:

- [Allegan County MI UCC & Lien Records Search](https://apify.com/lienintel/allegan-county-mi-lien-filings): county recorded liens and UCC filings in Allegan County, Michigan
- [Allegheny County PA UCC Filings: Debtors & Secured Parties](https://apify.com/lienintel/allegheny-county-pa-ucc-filings): county recorded liens and UCC filings in Allegheny County, Pennsylvania
- [Arapahoe County CO Lien Filings: UCC, Tax & Mechanics](https://apify.com/lienintel/arapahoe-county-co-lien-filings): county recorded liens and UCC filings in Arapahoe County, Colorado
- [Baldwin County AL Liens: UCC, Tax & Judgment](https://apify.com/lienintel/baldwin-county-al-lien-filings): county recorded liens and UCC filings in Baldwin County, Alabama

### FAQ

**Is this a statewide Alaska search?**

Yes. The actor covers the UCC Central File and every Alaska recording district. Use `district` to narrow to one district, or `ALL` to search statewide.

**Does it include debtor and lender names?**

Yes. Every document returns all indexed parties, their roles and their addresses, plus derived primary debtor and secured-party names and counts.

**Can I search by lender or lien claimant?**

Yes. Enter the lender, funder or claimant name. The recorder's name index matches the start of the indexed name, so a partial name such as `WELLS FARGO` returns the exact indexed variants, and each variant is searched.

**Can I monitor new filings?**

Yes. Leave the names empty and set a date range. The actor walks the busiest recording districts and returns recent UCC, lien and tax-lien recordings.

**Are terminations and releases included?**

Yes. `is_release` is `true` for terminations, releases, partial releases and satisfactions so you can filter them in or out.

**Does it include the lien amount?**

Yes, when the recorder publishes one. `amount` is numeric and `amount_raw` preserves the published value.

**Is the data FCRA-compliant for credit decisions?**

No. This is public-record research and workflow data, not a consumer credit report.

### Run it through the Apify API

Replace `<TOKEN>` with your Apify API token.

```bash
curl -X POST "https://api.apify.com/v2/acts/lienintel~alaska-recorder-ucc-lien-filings/run-sync-get-dataset-items?token=<TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"searchNames": ["CHINOOK PLACE CONDOMINIUM ASSOCIATION"], "documentTypes": ["liens"], "dateFrom": "2000-01-01", "dateTo": "2026-10-21", "maxResults": 2, "district": "ALL"}'
```

With the Apify CLI:

```bash
apify call lienintel/alaska-recorder-ucc-lien-filings --input '{"searchNames": ["CHINOOK PLACE CONDOMINIUM ASSOCIATION"], "documentTypes": ["liens"], "dateFrom": "2000-01-01", "dateTo": "2026-10-21", "maxResults": 2, "district": "ALL"}'
```

Every run writes to a dataset that you can export as JSON, CSV or Excel from the Storage tab or through the Apify API.

***

*LienIntel is an independent data provider and is not affiliated with any government office named on this page. Records are public and are provided for research and workflow automation. This is not a certified search and not a consumer report under the FCRA.*

# Actor input Schema

## `searchNames` (type: `array`):

Names to search, up to 20. Partial names are supported, for example SMITH, WELLS FARGO or CHINOOK PLACE CONDOMINIUM ASSOCIATION. Each name is searched separately and results are deduplicated.

## `documentTypes` (type: `array`):

Document families to include. Allowed values: ucc, liens, tax_liens, mortgages, all. The default includes UCC filings, liens and tax liens.

## `district` (type: `string`):

Alaska recording district or UCC Central. Use ALL to search every district. Browse mode walks the busiest districts when ALL is selected.

## `dateFrom` (type: `string`):

Earliest recorded date in YYYY-MM-DD format. Leave empty for the last 7 days in browse mode, or the last 10 years when searching by name.

## `dateTo` (type: `string`):

Latest recorded date in YYYY-MM-DD format. Leave empty for today.

## `maxResults` (type: `integer`):

Maximum number of unique recorded documents to return and charge. Free Apify users receive up to 10 results per run.

## Actor input object example

```json
{
  "documentTypes": [
    "ucc",
    "liens"
  ],
  "district": "ALL",
  "maxResults": 25
}
```

# Actor output Schema

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

One row per recorded Alaska document with district, document number, index code, parties, addresses, amount, legal description, dates and document links.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("lienintel/alaska-recorder-ucc-lien-filings").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("lienintel/alaska-recorder-ucc-lien-filings").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 '{}' |
apify call lienintel/alaska-recorder-ucc-lien-filings --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,lienintel/alaska-recorder-ucc-lien-filings"
        }
    }
}
```

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/znaSzcElM6DHGZ9j4/builds/IP2o0lZlqSDvqqqWv/openapi.json