Provider Integrations
One normalized catalog, 50 live-validated provider connections, and provider-aware signal coverage.
Catalog
50
Featured
15
Categories
9
Featured providers in the product surface
OpenRouter
Auth: API key (management key preferred)
Signals: Cost, Usage, Credits
Validation: verified
Runtime: verified-live-adapter
OpenAI
Auth: Admin API key
Signals: Cost, Usage
Validation: verified
Runtime: verified-live-adapter
AWS
Auth: Access key + secret (read-only IAM) / Role-based credentials
Signals: Cost
Validation: verified
Runtime: verified-live-adapter
Anthropic
Auth: Admin API key
Signals: Cost, Usage
Validation: verified
Runtime: verified-live-adapter
Azure OpenAI
Auth: Azure service principal / Subscription ID
Signals: Cost, Usage
Validation: verified
Runtime: verified-live-adapter
Cursor
Auth: Team Admin API key
Signals: Cost, Usage
Validation: verified
Runtime: verified-live-adapter
Featured providers in the product surface - compact
Full catalog (compact view)
How coverage actually works
Provider-aware monitoring
Signals depend on what each provider officially exposes. Cost, usage, credits, and billing detail are not invented where they do not exist.
Scheduled sync windows
Spendwall uses scheduled ingestion and daily threshold evaluation instead of claiming fake real-time parity across very different providers.
Read-only connection model
Integrations are designed for visibility and governance. Provider accounts are not used as a write-back control plane.
Need route-level detail?
Use the support pages when you want setup notes, FAQ answers, or application route references behind this catalog.