Solutions
Cash health scores for SMB accounts — built for production APIs
Ship a defensible 0–100 cash health score from bank-grade inputs — structured JSON, narrative text, and drivers for SMB lending, embedded finance, and internal portfolio tools.
Most teams already ingest transactions and balances; the hard part is turning that stream into a repeatable decision signal that credit, product, and engineering can agree on. Cashytics exposes a dedicated cashflow health score route that returns structured drivers and a plain-language narrative alongside the score, so you can render dashboards, attach JSON to LOS records, or trigger policy rules without maintaining bespoke spreadsheets per cohort.
Why a score API beats analyst-built spreadsheets
Spreadsheet models drift the moment a new analyst inherits a file. An API contract, by contrast, version-changes like any other service: you test in staging, promote to production, and keep historical JSON for audit. That matters when regulators or investors ask how a decision was made six quarters ago.
Cashytics returns the same top-level response envelope across all eight POST routes, which means your data warehouse only needs one parser for `structured` blocks even as you add endpoints for runway, distress, or AR prioritization later.
What “health” means in the structured payload
The health score route is designed to summarize liquidity pressure, volatility, and directional cash tension using the envelope you supply — including trailing balance watermarks and categorized flows. Drivers are numeric so risk teams can diff accounts, while the narrative explains the “why” in language a committee can skim.
Because outputs are deterministic from the documented envelope, you can regression-test against golden files in CI the same way you test pricing engines — a big step up from subjective color-coding in Excel.
How this fits next to forecasts, runway, and distress
High-intent buyers rarely stop at a single number. Underwriting flows often need a score for triage, a runway read for covenant proximity, and distress flags for escalation. Cashytics maps those to separate endpoints so you can cache aggressively, route traffic by SLA, and disable features per tenant without branching your ingestion pipeline.
If you are evaluating paid tiers, compare monthly quotas and overage semantics on the pricing page — paid plans meter overages so production traffic does not hard-stop when a customer spikes during close week.
Security, residency, and operational boundaries
Teams running regulated programs usually ask two questions early: who holds ledger-of-record, and what leaves the perimeter. Cashytics is built around an ephemeral scoring pass you initiate: you POST an envelope, receive JSON, and decide what to persist in your own systems.
Pair this model with your existing vaulting for API keys (server-side only), and document in your DPIA that narratives are generated from customer-supplied aggregates rather than from a hosted ledger replica.
Proof before you re-platform your data lake
Use the playground to run representative SMB profiles — seasonal retail, lumpy payroll software, services firms with AR concentration — and read how narratives change when you tweak `balances.low_30d_minor` or add optional envelope blocks from the schema reference.
When the JSON matches what your PMs and risk leads expect, move to the quickstart and wire curl against staging keys. That sequence keeps sales cycles honest: you demonstrate the contract with real output, not slideware.
Rollout checklist for engineering leads
Start with schema validation on ingress, then add retries for 429 responses on free-tier workspaces. Log `endpoint` and `account_id` on every response for traceability, and snapshot anomaly cases (negative runway artifacts, missing categories) into fixtures so model updates do not surprise downstream dashboards.
If you need webhook-based async delivery for long-running internal workflows, read the webhooks documentation — the envelope supports an optional `webhook_url` field for compatible routes.
FAQ
- Do I need separate integrations per endpoint?
- No. All eight production routes accept the same JSON envelope; you change only the URL path. That keeps mobile, web, and batch workers aligned on one contract.
- Can I try output without creating API keys?
- Yes. The playground runs the same engine with sample data and does not consume your monthly API quota for production keys.
- Where should I store responses for audits?
- In your own systems. Treat Cashytics JSON like any other vendor artifact: append-only storage in your LOS or warehouse, with access controls you already operate.