Turn complex data and repetitive work into an operating advantage.

UCCContacts structures and normalizes filing records, supports secured-party filtering, and identifies repeat filings so teams can recognize duplicate activity and evaluate records with more context. Source data still varies by jurisdiction, so YANETO does not describe any dataset as perfect or error-free.

Covered states are updated on a daily or weekly schedule, depending on source availability. Filing dates and delivery cadence help buyers evaluate how recent a record is. UCCContacts does not claim perfectly real-time coverage.

UCCContacts currently focuses on debtor and secured-party information, with officer or principal enrichment when an available match can be made. Phone numbers and email addresses are not promised, and officer matches are not available for every record.

Yes. YANETO offers a separate dataset from a government source that included 18,915 distinct cell phone numbers and 37,212 distinct email addresses in the August data. This is a source-specific offering and is not a standard phone-or-email promise for every UCCContacts record. If you only want to purchase this dataset, contact YANETO to discuss current availability, coverage, fields, and delivery options.

Officer and principal details are sourced directly from Secretary of State records or other reliable government sources. Of the debtor-to-officer matches made, more than 99% are exact matches. Fewer than 1% use a fuzzy, or likely, match, and a fuzzy match must score above 90% before it is accepted. This keeps the fuzzy-match rate very low. Enrichment is included only when an available government record can be matched with appropriate confidence, so these percentages describe the matching method—not officer coverage across every UCC filing record.

UCCContacts classifies debtors algorithmically. A classification of 0 indicates an organization, 1 indicates an individual, and NC means the debtor was not classified. NC is used because not every state provides a distinct debtor classification in its source records. This approach is highly effective, but it is not infallible, and a small number of UCC debtors may be classified incorrectly.

Raw records are only the starting point. UCCContacts is designed around usability: multi-state coverage, structured fields, repeat-filing identification, secured-party filtering, available officer enrichment, API access in CSV or JSON format, and automated Google Sheets delivery.

The product is built for MCA funders, ISOs, brokers, commercial lenders, equipment-finance companies, factoring and debt-related businesses, data platforms, and lead-generation teams that can responsibly use UCC filing signals.

UCCContacts can identify repeat-filing activity associated with a record. That signal can help a team investigate filing history, but it should not be treated as a definitive statement of a company’s current obligations or funding position.

UCCContacts customers can retrieve data through the API in CSV or JSON format, or receive automated delivery to a Google Sheet. API access supports all available current and historical data. Google Sheets delivery is limited to the current month and includes that month’s backlog plus new records as they become available.

New UCCContacts customers can begin receiving data in less than 24 hours after account signup. Delivery timing may depend on completing the required account and delivery configuration.

No. API customers can retrieve all available data, including historical data, in CSV or JSON format. Automated Google Sheets delivery covers the current calendar month only. For example, a Google Sheets customer who starts on September 7 receives the available September backlog and then receives new September data as it becomes available.

New records are available through the API immediately after they are loaded into the master system. Automated Google Sheets customers receive the newly loaded data within 15 minutes.

Watched-company and competing-lien alerts are not currently presented as a standard UCCContacts capability. YANETO can discuss the monitoring use case and integration requirements, but availability should be confirmed before it is included in a solution plan.

Yes. YANETO’s team has built a custom CRM that supported a customer sending thousands of text messages per day. That customer’s application is not resold or copied; a new system must be designed and built from scratch around your requirements. The customer is responsible for complying with all applicable texting laws, consent and opt-out requirements, do-not-contact rules, carrier policies, and platform terms. YANETO does not provide legal advice.