Skip to main content
Docs · Integrate

A focused surface.
Synchronous where
it matters.

One endpoint to send activity, one endpoint to read the financial state. Light context returns in-line right away; the fuller state and its readiness gates typically update within minutes, and your product fetches them once they are ready.

Talk to our team See the flow
01The flow

Activity in.
Understanding out.

Your product already has the stream. Neumetria sits under it: ingest, interpret, keep the financial state current, expose gates. Your policy still decides what happens next.

POST /v1/transactions
Stream activity in. Minimal payload: amount, merchant hint, timestamp, direction. Your existing open-banking or ledger feed is enough to start.
→ synchronous response
Light context returns in-line so the request path stays fast. Designed for a sync-slice latency budget under 200ms at p99 (environment-dependent).
· async processing
The fuller financial state and readiness gates typically update in the background within minutes as new activity lands. One engine covering earn, spend, save, borrow, invest, and hold signals as data allows.
GET /v1/actors/{id}/understanding
Read the current financial state on demand. Versioned objects, confidence, and as_of. Optional gate bundle for spend / save / invest / quiet.
02What you read

Understanding,
then gates.

The read surface is built for products and agents that need a person-shaped view before they paint a screen or plan a turn — not a dump of raw classifications.

01Understanding

A current behavioral view of the person: how they earn, spend, and hold, read in context, with confidence and as-of on each object.

02Gates

Readiness for this moment: spend, save, invest, or stay quiet. Your product decides what that means for UI, policy, or an agent turn.

03Auditability

Versioned responses you can inspect and log. Built for human review and documentation when credit or automated systems sit under oversight.

Illustrative shape only. Field names and nesting in the private preview may differ. We do not publish the full object catalogue here on purpose.

Authentication is API-key based per tenant. Actors are scoped to your tenant. We do not share behavioral views across customers.

GET /v1/actors/{id}/understanding
// illustrative
{
  "actor_id": "a_4f2a9e...",
  "as_of": "2026-07-22T09:41:00Z",
  "understanding": {
    "income_rhythm": { "shape": "biweekly", "stability": 0.91 },
    "liquidity_horizon": { "days": 11, "confidence": 0.78 },
    "behavior_drift": { "direction": "cooling", "since_days": 19 }
  },
  "gates": {
    "spend_readiness": "moderate",
    "save_readiness": "hold",
    "invest_readiness": "hold",
    "stay_quiet": false
  }
}

»» Gate names describe readiness for your product to read. They are not advice, guarantees, or instructions to the end user.

03Callers

Same API.
Three jobs.

Lenders, product surfaces, and agents all hit the same layer. What changes is what your policy does with the response.

01 · Lend

Affordability context

Read capacity alongside the credit file for creditworthiness checks. Your institution owns approve, decline, limit, and price.

Lend application →02 · Adapt

Surfaces and gates

Banks, wallets, and investment apps query the financial state and gates before painting a prompt — or choosing silence.

Adapt application →The caller · Agents

Ground the turn

Agent runtimes fetch the financial state and gates before planning language. Your product bounds what the agent may do.

Agents application →
04What integration looks like

Setup, security,
pricing, support.

Setup
Often 2–4 weeks from first call to first live financial state in a staging environment, depending on data shape and access.
Security
SOC 2 and ISO 27001 certification in progress. We process personal data under GDPR. Data residency and PII handling agreed before any integration begins. Tenant isolation is the default.
Pricing
Annual contracts, scoped to the surfaces you integrate. We size with you once we understand the deployment.
Support
We work directly with your engineering lead during integration. No procurement-scale SDK tour.
POST /v1/transactions · illustrative
// minimal ingest shape
{
  "actor_id": "a_4f2a9e...",
  "transactions": [
    {
      "amount": 52.40,
      "currency": "USD",
      "direction": "debit",
      "posted_at": "2026-07-19T10:24:00Z",
      "merchant_hint": "WHOLEFDS MKT"
    }
  ]
}
05Access

Private preview.
On purpose.

Full OpenAPI, auth recipes, webhooks, and SDK patterns live in the private preview. We share them once we have mapped fit with your product and the first surface you are integrating.

Write with your product, the caller (lend, surface, or agent), and the environment you want to start in. We will send the preview and schedule a working session with your engineering lead.

Designed to embed via API — and, where useful, into agent runtimes. Built for regulated environments. Your product keeps the duty of care.

Integrate

Ready to stream activity in?

If you are building lending, product surfaces, or financial agents on a current financial state, talk to us.

Contact sales Request API preview