# Medina County TX Liens: UCC, Tax, Mechanics & Judgments (`lienintel/medina-county-tx-lien-filings`) Actor

Search Medina County, Texas recorded liens, judgments, tax liens and UCC filings by party or document number. Get grantors, grantees, debtors, secured parties, dates, legal descriptions, amounts and county document numbers in clean JSON. $0.015 per record.

- **URL**: https://apify.com/lienintel/medina-county-tx-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

[![Medina County TX Liens: UCC, Tax, Mechanics & Judgments](https://scrapers.lat/banners/medina-county-tx-lien-filings.png)](https://console.apify.com/actors/Q8pfrv1Aely1f0BF0/input)

## Medina County TX Liens: UCC, Tax, Mechanics & Judgments

Search **Medina County, Texas** recorded liens, UCC filings, tax liens, abstracts of judgment, mechanics liens and lis pendens by party name or exact document number. Get clean, flat records with the debtor, secured party or claimant, both published party sides, recording dates, legal descriptions, amounts and the county document number.

This is a dedicated single-county index.

Here is one real record from this actor. `source_page` is left out of this example and included in your dataset.

```json
{
  "record_id": "2026010891",
  "document_number": "2026010891",
  "instrument_number": "2026010891",
  "doc_type": "FINANCING STATEMENT 1",
  "doc_type_code": "FS1",
  "doc_type_family": "ucc",
  "lien_category_label": "UCC financing statement",
  "doc_group": "FS",
  "is_release": false,
  "recorded_date": "2026-10-23",
  "recorded_time": "1:27 PM",
  "instrument_date": "2026-10-23",
  "book": null,
  "volume": null,
  "page": null,
  "book_volume_page": null,
  "page_count": 3,
  "grantor_name": "RAMIREZ ALYSSA",
  "grantor_names": "RAMIREZ ALYSSA",
  "grantor_count": 1,
  "grantee_name": "ISPC",
  "grantee_names": "ISPC",
  "grantee_count": 1,
  "debtor_name": "RAMIREZ ALYSSA",
  "debtor_names": "RAMIREZ ALYSSA",
  "debtor_count": 1,
  "secured_party_name": "ISPC",
  "secured_party_names": "ISPC",
  "secured_party_count": 1,
  "party_direction": "grantor_debtor",
  "direction_source": "code_map",
  "property_address": null,
  "legal_description": "Subdivision- Name: REDBIRD RANCH PHASE 2 Lot: 41 Block: 99 Unit: 3M-4",
  "municipality": null,
  "subdivision": "REDBIRD RANCH PHASE 2",
  "lot": "41",
  "block": "99",
  "unit": "3M-4",
  "parcel_numbers": null,
  "amount": null,
  "amount_text": null,
  "amount_source": null,
  "consideration": null,
  "filer_name": null,
  "filer_address": null,
  "parties_truncated": false,
  "county": "Medina",
  "state": "TX",
  "source": "Medina County Clerk, Texas - Real Property Records",
  "source_url": "https://www.medinacountytexas.org/page/County.Clerk",
  "search_role": "new_filings",
  "search_term": null,
  "search_terms": "families=ucc,tax_lien,judgment,mechanics,lien,lis_pendens; role=any; 2026-10-01..2026-10-31",
  "observed_at": "2026-10-31T07:24:04.372Z",
  "confidence": 1
}
```

**[Input](https://apify.com/lienintel/medina-county-tx-lien-filings/input-schema) | [Output](https://apify.com/lienintel/medina-county-tx-lien-filings/output-schema) | [Pricing](https://apify.com/lienintel/medina-county-tx-lien-filings/pricing)**

![Coverage](https://img.shields.io/badge/Coverage-Medina%20County%2C%20Texas-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

- **One row per recorded instrument**, deduplicated by the Medina County Clerk document number.
- **UCC financing statements** (`FS1`) and **UCC financial statement 3** (`FS3`) with debtor and secured-party names.
- **Federal tax liens** (`FTL`) and **Texas state tax liens** (`STL`), plus their **releases** (`RFTL`, `RSTL`) when releases are enabled.
- **Abstracts of judgment** (`AJ`) and **releases of judgment** (`RELJGMT`).
- **HOA, assessment and other statutory liens** (`LIEN`).
- **Mechanics liens** (`ML`).
- **Lis pendens** (`LP`).
- Every published **grantor and grantee**, normalized **debtor** and **secured party / claimant** roles, and a direction source so you can see how the roles were mapped.
- Recording date, instrument date, book/volume/page, page count, legal description, subdivision, lot, block, unit, parcel or reference numbers, amount and amount source.
- Filer name and return address when the Clerk publishes them.

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

| Field | Type | Description |
|---|---|---|
| `record_id` | string | County document number used as the unique record key |
| `document_number` | string | Medina County Clerk document number |
| `instrument_number` | string | Instrument number assigned by the Clerk |
| `doc_type` | string | County document type description, for example FEDERAL TAX LIEN or MECHANICS LIEN |
| `doc_type_code` | string | County document type code, for example FTL, STL, FS1, LIEN, ML or LP |
| `doc_type_family` | string | Normalized family: ucc, tax_lien, judgment, mechanics, lien, lis_pendens, release or other |
| `lien_category_label` | string | Human-readable family label |
| `doc_group` | string | County document group code |
| `is_release` | boolean | True for a release of a federal tax lien, state tax lien or judgment |
| `recorded_date` | string | Recording date in YYYY-MM-DD format |
| `recorded_time` | string | Recording time as published, when available |
| `instrument_date` | string | Instrument or judgment date in YYYY-MM-DD format |
| `book` | string | Book number, when the Clerk publishes book/page |
| `volume` | string | Volume number, when the Clerk publishes book/page |
| `page` | string | Page number, when the Clerk publishes book/page |
| `book_volume_page` | string | Raw volume/book/page string |
| `page_count` | integer | Number of pages in the recorded document |
| `grantor_name` | string | Primary grantor exactly as the Clerk indexed it |
| `grantor_names` | string | All grantors, joined with semicolons |
| `grantor_count` | integer | Number of grantor names |
| `grantee_name` | string | Primary grantee exactly as the Clerk indexed it |
| `grantee_names` | string | All grantees, joined with semicolons |
| `grantee_count` | integer | Number of grantee names |
| `debtor_name` | string | Primary debtor name when the document direction identifies a debtor |
| `debtor_names` | string | All debtor names, joined with semicolons |
| `debtor_count` | integer | Number of debtor names |
| `secured_party_name` | string | Primary secured party, claimant or lienholder when identifiable |
| `secured_party_names` | string | All secured party or claimant names, joined with semicolons |
| `secured_party_count` | integer | Number of secured party or claimant names |
| `party_direction` | string | grantor_debtor, grantee_debtor or mixed |
| `direction_source` | string | code_map, financial_heuristic, claimant_heuristic or mixed |
| `property_address` | string | Property addresses on the filing, joined with semicolons |
| `legal_description` | string | Legal descriptions, joined with a pipe |
| `municipality` | string | Municipality or city from the legal description |
| `subdivision` | string | Subdivision or condominium name |
| `lot` | string | Lot or unit number, or a low-high range |
| `block` | string | Block number |
| `unit` | string | Unit or part from the legal description |
| `parcel_numbers` | string | Parcel or reference numbers from the legal description |
| `amount` | string | Lien, judgment or tax amount when the Clerk publishes one |
| `amount_text` | string | Raw amount text from the consideration or legal description |
| `amount_source` | string | consideration or legal_description |
| `consideration` | string | Consideration amount when the Clerk publishes one |
| `filer_name` | string | Filer or return-address name |
| `filer_address` | string | Filer or return address, flattened to one string |
| `parties_truncated` | boolean | True when the Clerk truncates a long party list |
| `county` | string | County; always Medina |
| `state` | string | US state; always TX |
| `source` | string | Public source name |
| `source_page` | string | Public search page |
| `source_url` | string | Official county Clerk page |
| `search_role` | string | How the record matched: party, document_number or new_filings |
| `search_term` | string | Party name or document number that matched this record |
| `search_terms` | string | Filters used for the run |
| `observed_at` | string | Timestamp when the record was observed |
| `confidence` | integer | Record confidence, 1.0 when debtor and secured party are identified, 0.7 for mixed rows |
| `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 |
|---|---|---|---|---|
| `partyNames` | array | no | (none) | Names to search, up to 20. Partial names are supported, for example SMITH, FROST BANK or INTERNAL REVENUE SERVICE. Each name is searched on both the grantor and grantee side and results are deduplicated. |
| `partyRole` | string | no | `"any"` | Match the name as grantor, grantee, or either side. For most liens the grantor is the claimant or secured party and the grantee is the debtor; UCC initial filings reverse that direction. Values: `any`, `grantor`, `grantee`. |
| `documentNumbers` | array | no | (none) | Optional Medina County Clerk document or instrument numbers, up to 20. Use this to verify a known filing. |
| `docTypeFamilies` | array | no | (none) | Recorded families to include. Leave empty for all lien families. Allowed values: ucc, tax_lien, judgment, mechanics, lien, lis_pendens, release. |
| `includeReleases` | boolean | no | `false` | When enabled, also return recorded releases of federal tax liens, state tax liens and judgments. Releases are marked is_release=true. |
| `dateFrom` | string | no | (none) | Earliest recorded date in YYYY-MM-DD format. Leave empty for the last 30 days when no search term is given, or the last 10 years when searching by name or document number. |
| `dateTo` | string | no | (none) | Latest recorded date in YYYY-MM-DD format. Leave empty for today. |
| `maxRecords` | integer | no | `25` | Maximum number of unique recorded records to return and charge. Free Apify users receive up to 10 results per run. |

A working example to paste into the Input tab:

```json
{
  "maxRecords": 2,
  "partyRole": "any",
  "includeReleases": false
}
```

### Use cases

- Check financing statements west of San Antonio in Medina County, with grantor and grantee side labels.
- **MCA, equipment-finance and working-capital funders** monitoring new UCC filings and the incumbent secured party.
- **Commercial lenders and credit teams** checking lien priority and recent county-level activity.
- **Collections, recovery and judgment-enforcement teams** finding abstracts of judgment and releases.
- **Contractors, suppliers and construction-credit teams** tracking mechanics liens.

### Coverage and freshness

**Party direction**

The Clerk does not use one party order for every instrument. The actor maps the published order per document type:

- **UCC initial filings (`FS1`)** put the debtor on the grantor side and the secured party on the grantee side.
- **Federal and state tax liens** put the agency on the grantor side and the debtor on the grantee side. Their releases keep that order.
- **Abstracts of judgment and judgment releases** put the judgment creditor on the grantor side and the debtor on the grantee side.
- **HOA and other statutory liens** put the claimant on the grantor side and the debtor on the grantee side.
- **Lis pendens** put the plaintiff or claimant on the grantor side and the owner or defendant on the grantee side.
- **FS3 filings and mechanics liens** are indexed in either order. FS3 rows use a conservative secured-party name test; mechanics rows use a contractor/supplier claimant test. When the direction is ambiguous, the row is marked `mixed` and both published party lists are still returned.

`direction_source` is `code_map`, `financial_heuristic`, `claimant_heuristic` or `mixed`.

- **Source:** Medina County Clerk real-property index, published through the County's public search.
- **Jurisdiction:** Medina County, Texas only.
- **Volume verified for 2025-01-01 through 2026-10-31:** 23,378 recorded instruments, including 431 `FS1`, 331 `FS3`, 78 `FTL`, 72 `STL`, 325 `LIEN`, 49 `ML`, 239 `AJ`, 141 `LP`, 46 `RFTL`, 47 `RSTL` and 13 `RELJGMT`.
- **Recent volume:** 1,802 instruments in September, October 2026 and 764 in October 2026.
- **Latest recording observed on 2026-10-23**, about eight days behind the 2026-10-31 run date. The default 30-day browse still returns current records.
- The County publishes records as they are indexed. A newly recorded instrument can take a short time to appear, and OCR-indexed party names can be incomplete on the day of recording. Re-run a party search before relying on a name that was recorded today.
- Document images and certified copies are not downloaded. The actor returns the public index data 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 "Medina County Texas lien", "Medina County recorder" and "Medina County 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 and `regdata/us-county-recorded-documents` lists county clerk records in TX, OH and MI. 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:

- [Bexar County TX Liens: UCC, Tax, Mechanics & Judgments](https://apify.com/lienintel/bexar-county-tx-lien-filings): county recorded liens and UCC filings in Texas
- [Harris County TX UCC & Lien Filings: Debtors, Lenders](https://apify.com/lienintel/harris-county-tx-ucc-lien-filings): county recorded liens and UCC filings in Texas
- [Johnson County TX UCC & Lien Filings: Debtors, Lenders](https://apify.com/lienintel/johnson-county-tx-ucc-lien-filings): county recorded liens and UCC filings in Texas
- [Alaska Recorder UCC & Lien Filings: Debtors & Lenders](https://apify.com/lienintel/alaska-recorder-ucc-lien-filings): county recorded liens and UCC filings in Alaska

### FAQ

**Does this cover all of Medina County?**

It covers the Medina County Clerk real-property index for the document families listed above. It does not cover statewide UCC filings, district-court cases or documents recorded in another county.

**Can I search a name on only one side?**

Yes. Set `partyRole` to `grantor` or `grantee`. The default is `any`, which searches both sides.

**Can I verify one document?**

Yes. Put the Clerk's document number in `documentNumbers`. Exact lookups return the matching record and are charged per returned record.

**Why are some rows marked `mixed`?**

FS3 and mechanics-lien filings are indexed in either party order, and some rows do not publish enough information to identify the debtor and claimant reliably. Those rows keep the raw grantor and grantee lists and are marked `mixed` instead of guessing.

**Are releases included by default?**

No. Set `includeReleases` to `true`, or select the `release` family explicitly.

**Is this a title search?**

No. It is a public-record research tool. It does not certify title, ownership, lien priority or the legal effect of any instrument.

**Is this a consumer credit report?**

No. It returns public recorded documents for research and workflow automation. It is not a consumer report under the FCRA and must not be used to decide credit, employment, housing or insurance eligibility.

### Run it through the Apify API

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

```bash
curl -X POST "https://api.apify.com/v2/acts/lienintel~medina-county-tx-lien-filings/run-sync-get-dataset-items?token=<TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"maxRecords": 2, "partyRole": "any", "includeReleases": false}'
```

With the Apify CLI:

```bash
apify call lienintel/medina-county-tx-lien-filings --input '{"maxRecords": 2, "partyRole": "any", "includeReleases": false}'
```

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

## `partyNames` (type: `array`):

Names to search, up to 20. Partial names are supported, for example SMITH, FROST BANK or INTERNAL REVENUE SERVICE. Each name is searched on both the grantor and grantee side and results are deduplicated.

## `partyRole` (type: `string`):

Match the name as grantor, grantee, or either side. For most liens the grantor is the claimant or secured party and the grantee is the debtor; UCC initial filings reverse that direction.

## `documentNumbers` (type: `array`):

Optional Medina County Clerk document or instrument numbers, up to 20. Use this to verify a known filing.

## `docTypeFamilies` (type: `array`):

Recorded families to include. Leave empty for all lien families. Allowed values: ucc, tax_lien, judgment, mechanics, lien, lis_pendens, release.

## `includeReleases` (type: `boolean`):

When enabled, also return recorded releases of federal tax liens, state tax liens and judgments. Releases are marked is_release=true.

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

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

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

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

## `maxRecords` (type: `integer`):

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

## Actor input object example

```json
{
  "partyRole": "any",
  "includeReleases": false,
  "maxRecords": 25
}
```

# Actor output Schema

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

One row per recorded Medina County lien, judgment, tax lien or UCC filing with parties, dates, document numbers, legal descriptions, amounts and county document type codes.

# 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/medina-county-tx-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/medina-county-tx-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/medina-county-tx-lien-filings --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,lienintel/medina-county-tx-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/Q8pfrv1Aely1f0BF0/builds/nlc6y85NcltqlltYY/openapi.json