Provider architecture
Data Sources
No data provider is hard-coded into the valuation engine. Each source is an adapter that normalises vendor data into engine-standard shapes — that standardisation is core URLX intellectual property.
Adapter interfaces
interface TrafficDataProvider {
getTraffic(domain: string): Promise<TrafficReading | null>;
}
interface FinancialDataProvider {
getFinancials(ticker: string, domain: string): Promise<FinancialReading | null>;
}
interface SearchDataProvider {
getSearchDemand(domain: string): Promise<SearchReading | null>;
}The engine receives standardised data with its provenance attached and does not know or care where it came from.
Source registry · 7 entries
| Source | Category | Provider | License | Status |
|---|---|---|---|---|
| Public Company Filings | FINANCIAL | Regulatory filings (public record) | PUBLIC | PUBLIC |
| Exchange Listing Data | MARKET | Public exchange listing records | PUBLIC | PUBLIC |
| Traffic Intelligence Provider | TRAFFIC | Not connected | PLANNED | INACTIVE |
| Web Analytics (Owner-Granted) | TRAFFIC | Not connected | PLANNED | INACTIVE |
| Search Demand Provider | SEARCH | Not connected | PLANNED | INACTIVE |
| Revenue / Commerce Data Provider | FINANCIAL | Not connected | PLANNED | INACTIVE |
| URLX Development Dataset | DEVELOPMENT | URLX (internal) | INTERNAL | INTERNAL |
Provider policy
URLX never claims a provider relationship that does not exist. Sources marked PLANNED are architectural placeholders. All measurements currently in the engine come from the internal URLX development dataset and are illustrative.