How the evaluation works

Three steps. Your files, your call, our engine.

No synthetic data, no rebuilt workflow. The sandbox runs on files you've already decided — so the comparison is against ground truth you already trust.

1 Bring your files

Recent, real, already-decided

Pick a batch of recent applications you've approved or rejected — a deliberate mix of both. GST returns, bank statements, invoices, KYC — whatever you have, ingested as-is.

A mix of good and bad files

2 Run the engine

One API call per file

Each file goes through a single authenticated call. The engine verifies entity, transaction and financial — two layers, one pass — and hands back a Risk Ready Packet in ~120 seconds.

~120s to a desk-ready packet

3 Compare to your call

The packet vs. your decision

Put each packet next to the decision your desk actually made. See what we'd have flagged, cleared, and where we'd have saved hours — measured against outcomes you already know.

Ground-truth, not a guess

The engine · what happens to each file

One API call. Watch the engine work.

This is exactly what runs inside the sandbox. Your LOS keeps running the loan — TruStackAPI runs the verification: one call, two layers, a Risk Ready Packet handed back before the file would reach a credit desk.

Scroll to follow a file through the firewall

Purpose-built verification

A layer that drops in — not a platform to build Rules for speed, governed AI for risk control ~120s from call to a desk-ready packet

Your first call

From sandbox key to first packet in minutes.

The sandbox is the production API with a scoped key. The integration you build against it is the same one you ship — nothing to redo when you go live.

Get your sandbox key

We provision a scoped sk_sandbox_… key and a VPC endpoint, with the full API reference.

POST a file to `/v1/verify`

Send an application plus its supporting documents — one authenticated request hands the whole file to the engine.

Read the Risk Ready Packet

Block for the response or take a webhook — score, severity-triaged flags, and the three-part packet come back ready for the desk.

sandbox.sh cURL

# sandbox · one file · application + documents
curl -X POST https://api.trustackapi.com/v1/verify \
  -H "Authorization: Bearer $SANDBOX_KEY" \
  -H "Content-Type: application/json" \
  -d @application.json

200 OK~118s · application/json

{
  "id": "app_4471",
  "mode": "sandbox",
  "score": "B+",
  "decision": "review",
  "flags": [
    { "severity": "P1", "label": "Hidden EMI detected" }
  ],
  "packet": { "verification_memo", "cam_bridge", "audit_log" }
}

Developer access

Sandbox keys, full API reference, payload schemas and the severity taxonomy — provisioned the day your evaluation starts.

Enter demo

What comes back

Every file returns a Risk Ready Packet.

Not a score in isolation — the full evidence-graded read your desk would open, in three parts.

Verification Memo

The risk read in one page — applicant intel, insights, signals, distilled flags.

CAM Bridge

80–90% of credit-appraisal prep already structured and ready to carry into the CAM.

Audit Log

Every check audit-trailed and regulator-exportable. RBI FREE-AI ready by design.

VM-IF-150196 · Vihaan Polymers & Engineering Plastics

TruScore

32.5/100

Requires resolution

ActiveGSTIN

AA+Buyer

38dDSO

₹9.1LGST·bank gap

2 / 5Invoices

Verification narration · 8 sections

1Entity ProfileVerified

3Buyer & CounterpartyPartial

4Transaction TrailUnverified

5Financial HealthPartial

Key verification signals

GST Return vs Bank Receipts₹9.1L gap — declared > receivedHygiene

Document AuthenticityAll 5 clean — no tampering (AI)Clear

Buyer Credit QualityAA+ · paying 7d ahead of termsStrong

One packet · three parts

Verification MemoCAM BridgeAudit Log

What's included

A full evaluation — inside your perimeter, on your terms.

Everything you need to judge the engine against your own book, with nothing leaving your cloud and no commitment on the other side.

VPC-native deployment

The engine runs inside your cloud. Borrower data, documents and outputs never leave your perimeter.

Sandbox keys & documentation

Scoped API keys, full reference, payload schemas and the severity taxonomy — provisioned day one.

Engine tuned to your segment

The product cartridge reads your loan type — checks, scoring slabs and STP thresholds tuned to what you actually write.

A working comparison, not a pitch

Run your decided files, line the packets up against your calls, and judge accuracy on outcomes you already know.

14 days · zero commitment

A fixed window with no contract attached. You shape the tunable surface; we refine the engine against your feedback.

Defensible by construction

Every check audit-trailed and regulator-exportable. RBI FREE-AI aligned, DPDP-ready — from the first sandbox call.

Rules decide, AI advises, humans judge — in the sandbox exactly as in production. Nothing you see in the evaluation changes when you go live.

Request sandbox access

See it on your files before you decide anything.

The fastest way to judge a verification engine is to point it at files you've already called — and see where it agrees, where it doesn't, and what it catches early.

Tell us a little about your book and we'll provision a sandbox inside your VPC, with keys and docs, typically within a few working days.

Venkatesh Murthy

GTM & Product · Co-Founder

Valleesh Athreya

CTO · Co-Founder

Built and operated by OneTruth Technologies Private Limited.

Now onboarding design partners · Live sandbox

What to expect

A scoped sandbox deployed inside your VPC — keys and API reference included.
Bring 20–50 recent files you've already approved or rejected.
14-day evaluation. Zero up-front commitment.