Public-record data · scoped access

What is in the directory.

Public data can be incomplete or out of date.

Public-record data · scoped access

What the records can support

The dataset is a directory of public business facts, not a complete market census or a quality ranking. Check important facts against primary sources before using them.

01

Internal research

Filter by available location and service fields. Treat industry and tool fields as website mentions.

02

Workflow enrichment

Add source-backed directory fields to an internal review process, with your own deduplication and checks.

03

Market exploration

Study patterns in the directory while treating missing records, missing fields, and stale facts as known limits.

Public-record data · scoped access

Fields in the directory

Fields come from public sources or information submitted for review. Availability varies by record.

Agency recordPublic name, canonical slug, website, and phone when available
LocationReported city, state, country, coordinates, and remote-capable field when available
ServicesNormalized directory tags; unclaimed profiles show only services supported by specific public text or manual review
IndustriesKeyword matches from public agency websites; a mention is not verified client experience
ToolsKeyword matches from public agency websites; a mention is not verified implementation experience
Business detailsReported team size and founding year when available
Public rating fieldsListed Google review count and average rating when available
Ownership statusWhether we reviewed that someone can represent the agency; not a quality endorsement
Placement statusWhether a record has a paid, labeled placement; separate from ownership review

Available formats, refresh timing, field coverage, and license terms are confirmed for each request. We do not license contact emails for unclaimed agencies.

Found an incorrect record? Report the data issue. Represent the agency? Submit an ownership claim. Corrections and ownership requests are reviewed separately from paid data access.

Methodology

How a record becomes public

The process reduces obvious duplicates and records provenance, but it does not turn public business listings into a fully verified company master.

OriginsMost current records began with a dated Google Places snapshot and public website extraction. A reviewed owner can replace selected fields. Claiming does not turn unchanged public fields into owner statements.
Identity and duplicatesSource collection deduplicates Google Place IDs. Transformation then keeps one record per canonical slug, favoring the row with more review data. Branches and records that share a website can remain, so buyers should still check company identity.
Buyer discoverySearch and category pages require at least one listed AI service. Each displayed service must come from owner input, a manual category review, or specific public evidence. A business name or a generic word such as “automation” is not enough. Other published profiles remain available for correction or ownership claims but do not appear in default discovery.
Missing or conflicting fieldsMissing team size, tool mentions, pricing, and other evidence stays unpublished rather than being inferred. Reviewed owner-submitted fields can override the public snapshot; reported conflicts are held for human review.
FreshnessProfiles show a stored “Last checked” date when one exists. There is no universal refresh promise: public-source review updates are run manually, reviewed in a pull request, and appear only after the changed dataset is deployed.

A Google rating is an external public signal, not a Rolodex review or proof of AI delivery. Individual review excerpts are withheld on unclaimed records because business identity mismatches can occur in source data.

Public-record data · scoped access

Data access options

Tell us which fields, format, refresh schedule, and permitted use you need. We will confirm coverage, limits, and commercial terms before you commit.

Snapshot

One-time snapshot

A dated export of the available directory fields for an agreed use.

  • Available format confirmed before delivery
  • License scope stated in writing
  • Coverage and extraction date included
Ask about a snapshot

API

Integration access

Discuss query needs, permitted uses, data freshness, and technical limits before integration.

  • Requested filters reviewed for availability
  • Ownership status explained separately
  • Rate and access limits agreed in advance
Discuss an integration

Ask for a sample to inspect the schema and available coverage. Sample size and fields depend on the request and license terms.

Ask for a sample