Platform · Routing
Model Routing & Spend
How PURE routes work across model tiers, meters AI usage per principal, and routes inbound leads to nurture plans. Live config from pure_routing_rules + pure_rate_limits. Snapshot: 2026-06-26.
Model tiers
| Tier | Used for | Model class |
|---|---|---|
| Light | Drafting, intake refine, classification, in-page assists | Haiku class |
| Standard | Summaries, routing decisions, everyday agent work | Sonnet class |
| Heavy | Deep build, review, and reasoning-critical lanes | Opus class |
Tiers are chosen per task by pure_routing_rules (model routing) so light work never pays for a heavy model. Every call is metered in audit_log.
AI rate & spend caps (per principal)
Calls-per-minute rate & a daily spend ceiling
“Spent today” is the running tally against each principal’s ceiling.
| Principal | Calls / min | Daily $ cap | Spent today |
|---|---|---|---|
| mike (superadmin) | 600 | $500 | $0.10 |
| lane-a (Design) | 200 | $50 | $0.00 |
| lane-b (Platform) | 200 | $50 | $0.00 |
| verifier | 120 | $10 | $0.00 |
| client | 60 | $5 | $0.00 |
Every MCP call is metered in audit_log; the health-scan cron escalates anomalies. Enabling caps = enforce pure_rate_limits in the MCP guard.
Lead routing plans
First matching rule wins
Inbound leads match the first rule (by intent · source · type) and enter that nurture plan. Higher intent routes faster.
| # | Plan | Intent | Match | Action |
|---|---|---|---|---|
| 1 | #21 High Intent Seller | high | seller | Drive to a listing appointment |
| 2 | #29 High Intent Buyer | high | buyer | Fast cadence + auto saved-search |
| 3 | #28 Specific Home Interest | any | Open House · buyer | Property-match follow-up |
| 4 | #30 Re-Engaged Buyer | any | Saved Search Alert · past-client | Warm-back sequence |
| 5 | #26 New Lead Audit | mid | any | Verify + route before nurture |
| 6 | #NUR Long-Term Nurture | low | any | Slow drip until intent rises |
Rules live in pure_routing_rules (ordered); two auto-create a saved search on match. Edit order/intent there to re-tune routing.
Built by Code from live config — this page reflects the tables as configured; no figures invented.