ServiceVerticals makes each x402 family a first-class credit vertical with its own underwriting profile: advance rate, revenue-volatility haircut, settlement horizon, minimum track record, and required attestations. profileFor() resolves a service type to its vertical; qualify() gates eligibility; sizeAdvance() fronts revenue × advance_rate × (1 − volatility); register() lets governance tune profiles. Seeded for all p1 category families (coverage-checked). 7 new tests, full suite 233 green. Completes roadmap p3–p10. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2.2 KiB
p10 — New service verticals
Open distinct credit products for compute, inference, and data markets. Each major x402 family gets its own underwriting profile — advance rate, volatility haircut, settlement horizon, track-record and attestation gates — so credit is sized on each vertical's real economics, not one-size-fits-all.
Why
p1 made every x402 service a credit input via category risk weights. But a GPU compute provider, an LLM inference seller, and a data-feed operator have very different cash-flow shapes: settlement speed, revenue volatility, and the proofs that make their revenue trustworthy all differ. p10 turns each family into a first-class credit vertical with its own product parameters.
Scope
- Per-vertical underwriting profiles. Advance rate (how much projected revenue is frontable), revenue volatility (which haircuts the advance), settlement days, minimum track record, and required attestations — seeded for every category family and tunable by governance.
- Qualification gating. A borrower qualifies in a vertical only with the required attestations and enough finalized track record.
- Advance sizing.
advance = projected_revenue × advance_rate × (1 − volatility_haircut), so riskier/more-volatile verticals advance less on the same revenue.
Deliverables (shipped)
lib/services/service_verticals.ts—ServiceVerticals:SEED_VERTICAL_PROFILES— rwa / compliance / data / api / compute / storage / inference / dispute / defi profiles (coverage-checked against the p1 families).profileFor(serviceType)/get(vertical)/isSupported()/list().qualify(serviceType, { track_record_jobs, attestations })→ eligibility + what's missing.sizeAdvance(serviceType, projectedRevenueMotes)→ volatility-haircut advance.register(profile)— governance tuning.
test/service_verticals.test.ts— family coverage, resolution, qualification gates, advance sizing + haircut, unsupported/zero handling, governance tuning, defensive copies.
Success metric
Cred402 underwrites compute, inference, and data agents on terms that reflect each vertical's economics — and new verticals can be added by registering a profile, no core redeploy.