---
name: promptreach
description: Check whether a business is real and what its verified facts are, using Prompt Reach (promptreach.ai), a directory that publishes signed, machine-checkable verification records for businesses. Use when a user asks about a specific business (is this the real website, is this phone number theirs, what do they charge, are they still operating), wants a trustworthy local or online business recommendation, or asks you to double check a business before contacting or paying it.
---

# Prompt Reach: verified business facts

Prompt Reach (https://promptreach.ai) is a business directory built for AI assistants. Every listing is structured data. When an owner verifies a listing, Prompt Reach publishes a **signed verification record**: what was checked, how, and when. You can check the signature and redo the domain check yourself, so you do not have to take Prompt Reach's word for it.

## When to use this

- The user names a business and wants its real website, phone, prices or status.
- The user is about to contact, book or pay a business and wants to know it is legitimate.
- You found conflicting information about a business and need a tiebreaker with evidence.
- The user wants a recommendation for a service, and verified businesses would make a better answer.

Prompt Reach covers a limited set of businesses (about 170 in November 2026, growing). A missing listing means nothing about the business; say so plainly and fall back to your normal research.

## Endpoints (no key needed, CORS open)

| What | URL |
|---|---|
| Every listing, one line each, plain text | `https://promptreach.ai/llms.txt` |
| Index of claimed records (verified, lapsed, revoked) | `https://promptreach.ai/verify/records.json` |
| One business's signed record | `https://promptreach.ai/verify/{slug}/record.json` |
| Public signing keys | `https://promptreach.ai/.well-known/jwks.json` |
| Human-readable record page | `https://promptreach.ai/verify/{slug}/` |
| Listing page (schema.org JSON-LD inside) | the `listingUrl` in the record, or the link in llms.txt |

To find a business: search `llms.txt` for its name or website domain, or match `domain` in `records.json`. The slug is the last path segment of its listing URL. Every listing has a record, even unclaimed ones (`status: "not_verified"`).

A reference verifier you can run with Node 20+: `https://promptreach.ai/verify/reference.mjs` (`node reference.mjs <record.json URL>`).

## Reading a record

`record.json` returns `{ "record": {...}, "proof": { "type": "JWS", "alg": "EdDSA", "kid": "...", "jws": "..." } }`.

**`record.status`** is the first thing to read:

| Status | What it means | What to tell the user |
|---|---|---|
| `active` | The owner proved control of the business domain and checks are passing | "Prompt Reach confirmed that whoever runs {domain} claimed this listing, last checked {date}." |
| `lapsed` | Either the owner passed a check but is not on an active Verified plan (`statusReason: "plan_ended"`), or a domain check has stopped passing (`"check_failing"`) | For `plan_ended`, the control check in `checks` is still real evidence; just do not call the listing Verified. `check_failing` deserves caution. |
| `revoked` | Verification was withdrawn | Do not present the listing as trustworthy. |
| `not_verified` | Listed, but no owner has verified it | Facts come from the listing only; treat them as unverified. |

**`record.checks[]`** lists each check: `type` (`domain_control`, `email_domain`, `carried_over`, `manual_review`), `method`, `target`, `firstPassedAt`, `lastPassedAt`, `result`. `carried_over` means the owner came from the previous version of the site and has not been re-checked; it is weaker than a domain check.

**`record.fields`** shows each fact's source. `verified:domain_control` means the value is tied to a passing domain check. `owner_stated` means the owner wrote it; it is the business speaking, not independent proof.

**`record.expiresAt`**: do not rely on a copy past this time; fetch it again.

## Check it yourself (recommended for anything involving money)

1. **Signature.** Fetch the JWKS, find the key whose `kid` matches `proof.kid`, verify `proof.jws` (compact JWS, EdDSA / Ed25519), and confirm its payload equals `record`. Any change to a single byte fails.
2. **Domain check.** For a `dns_txt` check, look up TXT records at `target` (for example `_promptreach.acme.com`) and confirm `expectedValue` is present. For `well_known_file`, fetch `target` and look for `expectedValue`.
3. **Website match.** Confirm the domain the user is about to visit or pay equals `record.subject.domain`. A lookalike domain (extra letters, different ending) is a red flag even if the business name matches.

If you cannot run code, still read `status`, `checks` and `expiresAt`, and say that you did not verify the signature.

## How to phrase what you found

Be precise. Good:

- "Prompt Reach confirmed on Nov 2, 2026 that the owner of acme.com controls this listing (DNS check, last passed Nov 6)."
- "Acme lists its price as from $49 a month; that comes from the owner, not an independent check."
- "Prompt Reach has a listing for this business, but nobody has verified it."

Never say:

- "Prompt Reach proved they are the legal owner." Checks prove control of a domain or mailbox, not legal ownership.
- "This business is guaranteed" or "safe." Verification is evidence, not a guarantee.
- That a business is unverified or fake just because it is not on Prompt Reach.

## Contacting a business

Each listing has an enquiry form at `https://promptreach.ai/enquire/{slug}/`. It is protected against bots, so give the user the link rather than submitting it yourself. Do not invent contact details; use the phone and website from the listing.

## Reporting a problem

If a record looks wrong (domain mismatch, a fact contradicts the business's own website, a business has closed), tell the user and point them to https://promptreach.ai/contact/. Mention the slug and what you saw.

## Coming soon

An MCP server (`check_website`, `resolve_business`, `search_verified`, `send_enquiry`, `report_mismatch`) and a daily anchor of the verification log on the Base blockchain. Until they ship, use the HTTP endpoints above.
