Match tracker
HANDI STOP #135
tx-tabc · 2902 S RICHEY ST STE A, Houston, TX, 77017
Joined with 2 other record(s) — by name-contained.
1. Record ready
What does the record carry?
has name, street with a house number, zip, city + state, pin (lat/lng)
✓ Name: HANDI STOP #135✓ Street with a house number: 2902 S RICHEY ST STE A✓ ZIP: 77017✓ City + state: Houston, TX✓ Pin (lat/lng): 29.67596, -95.23267✗ Phone
2. Address joined
Is anyone else at this street + ZIP?
4 found (4 from another source); joined
| Record | Distance | What the rule says | What the master did |
|---|---|---|---|
| ab-inbev HANDI STOP 2902 S RICHEY ST STE A, HOUSTON, TX, 77017 | 58 m | address+name rule: passes (name similarity 1.00) | joined (name-contained) |
| vtinfo HANDI STOP 2902 S RICHEY ST STE A, HOUSTON, TX, 77017 | 67 m | address+name rule: passes (name similarity 1.00) | joined (name-contained) |
| overture Shell 2902 South Richey Street, Houston, TX, 77017 | 75 m | address+name rule: does not pass (name similarity 0.07) | not joined |
| shell Shell 2902 S RICHEY ST, HOUSTON, TX, 77017 | 104 m | address+name rule: does not pass (name similarity 0.07) | not joined |
3. City key joined
Anyone at this street in this city (no ZIP needed)?
4 found (4 from another source); joined
| Record | Distance | What the rule says | What the master did |
|---|---|---|---|
| ab-inbev HANDI STOP 2902 S RICHEY ST STE A, HOUSTON, TX, 77017 | 58 m | address+name rule: passes (name similarity 1.00) | joined (name-contained) |
| vtinfo HANDI STOP 2902 S RICHEY ST STE A, HOUSTON, TX, 77017 | 67 m | address+name rule: passes (name similarity 1.00) | joined (name-contained) |
| overture Shell 2902 South Richey Street, Houston, TX, 77017 | 75 m | address+name rule: does not pass (name similarity 0.07) | not joined |
| shell Shell 2902 S RICHEY ST, HOUSTON, TX, 77017 | 104 m | address+name rule: does not pass (name similarity 0.07) | not joined |
4. Street spelling found, not joined
Same house number, street written differently?
2 found (2 from another source); none joined by this step
| Record | Distance | What the rule says | What the master did |
|---|---|---|---|
| overture Burger King 2902 Richey St, Houston, TX, 77017 | 73 m | street-variant rule: does not pass | not joined |
| ubereats Burger King 2902 Richey Street, Houston, TX, 77017 | 134 m | street-variant rule: does not pass | not joined |
5. Nearby pins found, not joined
Anyone within 100 m?
4 within 100 m — distance alone never merges; these are questions for Claude
Pins are often geocoded from the address itself, so two pins agree whenever the addresses do — they cannot confirm a match, and never merge on their own.
| Record | Distance | What the rule says | What the master did |
|---|---|---|---|
| ab-inbev HANDI STOP 2902 S RICHEY ST STE A, HOUSTON, TX, 77017 | 58 m | stratum addr-agree | joined (name-contained) |
| vtinfo HANDI STOP 2902 S RICHEY ST STE A, HOUSTON, TX, 77017 | 67 m | stratum addr-agree | joined (name-contained) |
| overture Burger King 2902 Richey St, Houston, TX, 77017 | 73 m | stratum same-address | not joined |
| overture Shell 2902 South Richey Street, Houston, TX, 77017 | 75 m | stratum same-address | not joined |
6. Claude judge nothing found
What did Claude's judge say?
no judgement on these pairs
Haiku screens every candidate pair; only Opus judge
claude-opus-5-5:v12:low can merge, at confidence ≥ 0.8, with a numbered street on both sides.7. Web agent nothing found
What did the web agent find?
not asked
8. Person nothing found
What did a person answer?
no answers yet
9. Result joined
Where did it end up?
one outlet with 2 other record(s)
Outlet O0df8c8d12c61: 3 record(s) from ab-inbev, tx-tabc, vtinfo.
| Record | Distance | What the rule says | What the master did |
|---|---|---|---|
| ab-inbev HANDI STOP 2902 S RICHEY ST STE A, HOUSTON, TX, 77017 | 58 m | address+name rule: passes (name similarity 1.00) | joined (name-contained) |
| vtinfo HANDI STOP 2902 S RICHEY ST STE A, HOUSTON, TX, 77017 | 67 m | address+name rule: passes (name similarity 1.00) | joined (name-contained) |
Read-only. Every candidate is scored by the same code the master build uses, and "what the master did" is what the last build stored. Each search shows at most 40 records.