MRX Learning Center

Martin CAD Property Search: Lease Fields Are Search Inputs, Not Ownership Proof

Use Martin CAD lease and property-search fields to reproduce a retrieval route, then stop before treating the interface as ownership or title proof.

Martin CAD Property Search: Lease Fields Are Search Inputs, Not Ownership Proof

Direct answer for mineral owners

Martin CAD’s public property-search interface exposes Lease Number, Lease Name, Abstract, Agent, Property ID, Geo ID, and related filters and result columns. Those labels can help a researcher reproduce where a search was made and which public field was used. They do not prove mineral ownership, title, agency, lease validity, decimal interest, appraisal accuracy, tax liability, sale value, production, royalties, or a transaction result.

Key takeaways for mineral owners

  • Martin CAD currently offers Mineral as a Property Type and Mineral Property as a results filter.
  • Lease Number and Lease Name appear as advanced search inputs and result-surface columns.
  • The visible-column selector says Owner Address while the empty table header says Address; preserve the exact surface instead of silently normalizing the labels.
  • No owner, property, account, agent, or lease search was performed for this guide, and no record was reproduced.
  • A search field or hit is a retrieval lead, not proof of ownership, title, lease validity, value, tax, production, royalties, or a transaction outcome.
Martin CAD mineral lease search fields

Retrieval, not proof. This page inventories field labels on current official Martin CAD public search surfaces without performing a search or reproducing any owner, agent, address, property, account, or lease record. An interface label or search hit can establish where a researcher looked. It does not independently establish ownership, title, agency, authority, lease validity, decimal interest, appraisal accuracy, tax liability, mineral-rights sale value, production, royalties, or a transaction result. MRX provides educational information and resources only and does not buy mineral rights.

The direct answer is visible on the Martin CAD public property-search home page. The advanced property form currently includes Property ID, Geo ID, Legal, Abstract, Subdivision, Lease Number, Lease Name, Protest Status, and Agent. Its Property Type selector includes Mineral.

The separate Search Results page offers Mineral Property as a filter and exposes lease, account, owner, address, legal, acreage, market-value, tax-due, and action labels in the visible-column selector and empty result table. No query was submitted for this article. The observed table body was empty, so this guide does not claim that any person, property, lease, account, value, or tax entry appears in the system.

Direct answer: use a field to reproduce a route

The lease fields are useful for source control, not adjudication. A researcher can record that a term was entered in the Lease Name field, that a number was entered in the Lease Number field, or that Mineral Property was selected. That creates a reproducible retrieval note.

It does not answer whether the term is unique, current, correctly entered, connected to the intended tract, or legally sufficient. It also does not show what instrument created an interest, whether an assignment changed it, how a decimal was calculated, or whether a listed label has the same meaning outside this interface.

Interface surfaceExact observed labelSafe evidence useUnsupported conversion
Property TypeMineralRecord the category selected for a searchTreat the category as proof of title or a legal property classification
Advanced searchLease NumberReproduce the field and input type usedTreat a matching number as proof that a lease is valid, current, complete, or controlling
Advanced searchLease NameReproduce a name-based search routeTreat a name match as a unique property, owner, operator, or lease identity
Advanced searchAbstractPreserve one land-description search inputInfer a tract, acreage, title chain, or ownership share
Advanced searchAgentRecord that the interface exposes an Agent fieldInfer present agency, authority, scope, representation, or consent
Results filterMineral PropertyRecord the displayed filter choiceAssume every returned row is a mineral-rights ownership record
Results columnsMarket Value and Base Tax DueRecord which table labels were availableConvert an appraisal-system label into a sale price, offer, tax bill, or payment obligation

This boundary is the article’s information gain. A generic county-value page would blur search labels, appraisal data, title evidence, and transaction value. This guide keeps them in separate source lanes.

Preserve exact interface labels

The home-page advanced form and the no-query results page expose different parts of the retrieval system. On the home page, the observed property-search labels include:

  • Property ID and Geo ID;
  • Legal, Abstract, and Subdivision;
  • Lease Number and Lease Name;
  • Protest Status; and
  • Agent.

The results page offers a Mineral Property filter. Its visible-column selector includes Parcel ID, Sequence, Account, Owner ID, Property Type, Owner Name, Owner Address, Property Address, Legal, Abstract, Subdivision, Lease Number, Lease Name, Agent, Market Value, Base Tax Due, and Acres.

The empty table header uses a similar list, but it displays Address where the visible-column selector displays Owner Address. It also includes Action. Preserve that interface difference exactly. Do not silently rewrite both labels as the same field without a data dictionary or issuer statement.

The ordered field manifest used for this review has SHA-256 73edc6bb38fd5d2aa0baef265052162954e712742c0e993a4613c1cc837e4b7c. It records the observed labels, the retrieval date, and the facts that no search was performed and no record was reproduced. That hash helps later reviewers detect whether the bounded field inventory changed. It does not validate the interface, its underlying data, or any result.

Move through an evidence ladder

A defensible workflow has four separate stages:

  1. Search field. Record the exact URL, date, search mode, field label, filter, and query term used.
  2. Search hit. Preserve the displayed row labels and any system-provided identifier without treating the hit as a legal conclusion.
  3. Official record retrieval. Obtain the source document or dataset that the question actually requires and preserve its issuer, URL, date, bytes, and file hash.
  4. Independent verification. When ownership, title, authority, tax, or legal effect matters, reconcile the record with the relevant chain and obtain qualified interpretation.

Each stage answers a different question. Skipping from stage one or two to stage four creates an unsupported inference.

For example, a Lease Name match may help locate a record. It does not show that the displayed name is unique, that the lease remains in force, that every amendment or assignment is present, or that a person owns a specific decimal. A Lease Number match may narrow a search. It does not prove what numbering system controls or whether another issuer uses the same identifier.

Do not treat the Agent field as proof of agency

The current public form includes an Agent selector. That is an INTERFACE-OBSERVATION, not a relationship finding. This guide does not reproduce the selector’s option values because the article’s job is field semantics, not a directory of people or organizations.

The field’s presence does not establish:

  • who appointed a listed party;
  • whether an appointment remains current;
  • the property or account covered;
  • the scope or duration of authority;
  • whether a person may sign, negotiate, receive notice, or make a transaction decision; or
  • whether the displayed label reflects a current legal relationship.

If authority matters, identify the source document that creates or records it and verify that source on its own terms. Do not infer authority from the interface label alone.

Keep search results separate from data downloads

The Martin CAD Data and Records page separately routes readers to annual reports, reappraisal plans, mass appraisal reports, and year-specific roll downloads, including mineral archives. Those links form a different source lane from the public search interface.

A search hit and a downloaded archive should not be merged by assumption. Preserve the search URL and field route, then preserve the dataset URL, label, retrieval date, byte count, archive members, and hashes separately. If labels conflict, record the conflict instead of choosing the more convenient label.

The Martin CAD 2026 mineral archive guide owns one such label conflict between a publisher link and an internal PDF label. This article does not reopen that archive question. It owns only the search-input and no-query result-surface boundary.

Appraisal context is not title or sale value

The Texas Comptroller Valuing Property page supplies current general context about appraisal districts, taxable property, market value, and mass appraisal. That context explains why an appraisal system can expose property, value, and tax-related fields.

It does not make a search result a title record or a mineral-rights sale estimate. An appraisal-system Market Value label and a negotiated sale value answer different questions and can use different evidence, dates, assumptions, and legal interests. A Base Tax Due label is also not a complete tax conclusion for a reader or transaction.

The Texas Comptroller county directory can route current local appraisal or property-tax questions to the applicable office. It does not verify a Martin record, determine ownership, interpret agency, confirm lease validity, calculate a decimal, state tax liability, or determine a mineral-rights sale value.

Separate provenance from validity

Claim IDEvidence labelSource roleSupported observation
C280-01INTERFACE-OBSERVATIONMartin CAD home searchAdvanced property-search and Mineral property-type labels observed on the current public form.
C280-02INTERFACE-OBSERVATIONMartin CAD Search ResultsMineral Property filter, visible-column labels, empty table headers, and no-query state.
C280-03LABEL-BOUNDARYSearch Results selector and headerOwner Address and Address are separate visible labels.
C280-04NON-VALIDATINGEmpty result-table bodyNo record was returned or reviewed; the field inventory does not validate underlying data.
C280-05ROUTING-ONLYMartin CAD Data and RecordsRoute to separately published reports, plans, and roll downloads.
C280-06CONTEXT-ONLYTexas Comptroller Valuing PropertyGeneral appraisal-district and mass-appraisal context.
C280-07ROUTING-ONLYTexas Comptroller county directoryRoute a current local appraisal or property-tax question.
C280-08PRIVACY-BOUNDARYArticle research procedureNo owner, property, account, agent, or lease search was performed and no record was reproduced.

Provenance answers where a field, hit, or file came from. Validity asks whether the underlying information is correct, current, complete, uniquely matched, and fit for a specific purpose. A public URL, response hash, exact label, and retrieval date improve provenance. They do not establish title, ownership, agency, lease validity, decimal interest, value, tax, production, royalties, or legal effect.

Build a privacy-safe retrieval log

Use this compact log without copying more personal information than the task requires:

  1. Record the official search URL and retrieval date.
  2. Record the exact search mode, field label, property-type choice, and results filter.
  3. Record whether the query was submitted and whether a result was returned.
  4. If a result is necessary, record only the minimum identifier needed to retrieve the controlling source.
  5. Keep interface labels, result labels, downloaded files, and title evidence in separate fields.
  6. Preserve any label mismatch, including Owner Address versus Address.
  7. Add an evidence label such as INTERFACE-OBSERVATION, SEARCH-HIT, OFFICIAL-RECORD, NON-VALIDATING, or UNRESOLVED.
  8. Add the forbidden conclusions: ownership, title, agency, authority, lease validity, decimal interest, appraisal accuracy, tax liability, sale value, offer, production, royalties, and transaction outcome.

This structure gives search and answer systems a direct field inventory, explicit evidence states, and a visible stopping point. It does not guarantee indexing, rankings, retrieval, traffic, leads, or citation by any search engine or language model.

Keep adjacent Martin CAD jobs separate

The Martin CAD Category G row guide owns one aggregate parcel-count and market-value row. It does not define the search interface or prove a property result.

The Martin CAD MIUP plan guide owns the plan’s interest-versus-minerals terminology boundary. It does not define a Lease Name field or validate a search hit.

The Martin CAD general reappraisal-plan guide owns the source-attributed handoff to a separate contractor plan. It does not prove agency for a displayed field value or identify a controlling record for a property.

The Glasscock CAD property-search field inventory owns a different county interface and its own result-field surface. Field names should not be assumed portable between systems.

Frequently asked questions

Does Martin CAD offer Lease Name and Lease Number search fields?

Yes. Both labels appear in the public advanced property-search form and on the no-query result surface observed on August 29, 2026.

Does a Lease Name search result prove mineral ownership?

No. A field or hit can help reproduce a retrieval route, but ownership and title require separate source records and qualified interpretation when needed.

What does the Agent field prove?

The observed interface proves only that an Agent field is present. It does not establish current agency, authority, scope, or a relationship for any person or property.

Why preserve Owner Address and Address as different labels?

The visible-column selector uses Owner Address while the table header uses Address. Preserving both prevents an unsupported assumption that the two interface labels are identical.

Can Martin CAD search fields determine mineral-rights sale value?

No. The interface labels do not supply the complete ownership, lease, production, deduction, title, market, buyer, or transaction evidence needed for a sale-value conclusion.

Frequently asked questions

Does Martin CAD offer Lease Name and Lease Number search fields?

Yes. Both labels appear in the public advanced property-search form and on the no-query result surface observed on August 29, 2026.

Does a Lease Name search result prove mineral ownership?

No. A field or hit can help reproduce a retrieval route, but ownership and title require separate source records and qualified interpretation when needed.

What does the Agent field prove?

The observed interface proves only that an Agent field is present. It does not establish current agency, authority, scope, or a relationship for any person or property.

Why preserve Owner Address and Address as different labels?

The visible-column selector uses Owner Address while the table header uses Address. Preserving both prevents an unsupported assumption that the two interface labels are identical.

Can Martin CAD search fields determine mineral-rights sale value?

No. The interface labels do not supply the complete ownership, lease, production, deduction, title, market, buyer, or transaction evidence needed for a sale-value conclusion.

Sources reviewed for this article

A practical next step

Put your mineral rights in context.

Every mineral interest, royalty history, and written offer is different. Start with a question, or share what you have for a free underwriter review.

  • Free
  • Confidential
  • No obligation to sell

Ready for a closer look?

Open the Martin CAD Mineral Archive Guide

Get a directional range with the assumptions clearly stated.

or start with a question
Not ready to share documents? Travis can help you figure out what matters first.