✦
Vertical parity contract. Every vertical API has the same four endpoints and the same referrer_tag experiment pattern. Only the pocket field schema and revenue model differ. If you know one vertical, you know them all.
Verticals
Choose a vertical to get started
💳
Personal Loans
/v1/personal-loans/
stable
Debt consolidation, home improvement, major purchases. High-intent users with strong match signal. Revenue confirms T+14 to T+45 after a funded loan.
CPL · confirmed token: nw_pl_ 14 pocket fields
View API docs →
🏦
Banking
/v1/banking/
beta
High yield savings accounts, CDs, checking. CPC model — revenue fires on click with no confirmation lag. Pacing is the key constraint: partner budgets exhaust monthly.
CPC · same-day token: nw_bk_ pacing-aware
View API docs →
💰
Credit Cards
/v1/credit-cards/
planned
Rewards, cash back, travel, and balance transfer. CPA revenue model. Pocket fields: spending categories, credit score, annual fee tolerance.
CPA token: nw_cc_ docs coming soon
Not yet available →
🏠
Mortgage
/v1/mortgage/
planned
Purchase and refinance. Longer confirmation lag (T+30 to T+90). Pocket fields: property value, down payment, loan type, credit profile.
CPL · confirmed token: nw_mo_ docs coming soon
Not yet available →
📊
Find a Financial Advisor
/v1/find-advisor/
planned
Advisor matching by AUM, specialty, location. CPL model. Lower volume than financial product verticals but higher per-session revenue.
CPL token: nw_fa_ docs coming soon
Not yet available →
ℹ
Cross-vertical experiment? Use a shared referrer_tag base with a vertical suffix — my_experiment_pl, my_experiment_bk. Note that rev_per_session is not directly comparable across CPC and CPL verticals.