Future: synthetic address seeding pipeline (E2E)

[BleedingDev]

Goal

Build our own address dataset over time by generating/scraping realistic addresses via E2E flows, searching for them, and persisting results.

Who Uses This

• Product/engineering: build a high-coverage address DB without manual imports.
• Operators: reduce long-term dependency and cost.

What “Done” Means (Business)

• We can run a repeatable job that:
  • generates or scrapes address candidates
  • calls our /suggest
  • stores results into our DB for later reuse/analysis
• We can measure coverage improvements over time.

Constraints

• Must be safe/legal/ethical (no uncontrolled scraping).

Out of Scope

• Full-scale data pipeline and ML ranking.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• Own address DB + cache improvements (reduce provider dependency) #2

Related Issues

• Analytics + monitoring + dashboard (suggested/accepted, cache, providers) #3
• SDK: Core JS + React/Vue/Svelte + Web Component #1
• Providers: add HERE + Radar (MVP capacity & benchmarking) #7
• Self-hosting: Bun + Docker Alpine #6

👤 Suggested Assignees

• BleedingDev

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!