Night Shift · Just After Midnight
760out of 1000
★★★★☆
Agent: Steady Sentinel · built by nazmi
Strong result. Your agent got through the night with 2 parts missing, which says a lot about the ones you did choose. Fill the gaps below and this is a five-star build.

Scorecard

Resolution69
Experience80
Safety82
Value for money75
Resolved
5
Escalated
8
Failed
0
Credits
60/80

Tonight's rule

Regulator audit tonightSerious incidents cost double on Safety.

What this mission needed

  • ✓A fast brain, because the money moves in seconds
  • ✓Account & transaction lookup
  • ✗Payment actions tool
  • ✓Human approval before freezing or holding money
  • ✗Sanctions & watchlist screening

Lessons from your build

  • ✗
    Payment actions tool

    Spotting fraud is half the job. Stopping it means holding, freezing and releasing. That needs write access to money, and write access needs controls around it.

  • ✗
    Sanctions & watchlist screening

    Mule accounts and sanctioned names are known lists. Checking them is cheap, and missing one is the kind of failure a regulator writes to you about.

  • ✓
    Good call: Human approval before freezing or holding money

    A wrongly frozen account is someone's rent or payroll. An approval step adds about a minute and turns the agent's worst mistakes into questions.

How JAM builds this for real

Every part you chose maps onto the production stack we deploy for clients, then run for them around the clock. Anything you left out is flagged below.

  • BrainAmazon Bedrock · OpenAI GPT-5.4
  • ToolsBedrock Knowledge Bases + OpenSearch Serverless · Lambda tool → your core banking API · Jira / PagerDuty MCP server
  • MemoryStateless invocation
  • GuardrailsStep Functions approval gate
  • Run 24/7 byJAM managed service: monitoring, evals, cost control

Your agent's night

Read all 13 requests
Alert 7701: S$9,800 instant transfer to a new payee at 03:11.→ account_lookup(7701)✓ First payment to this payee, from a device never seen before. Held for review in 2 seconds.
The payee account was opened 3 days ago and has had 14 inbound transfers tonight.→ watchlist.check(payee)△ No watchlist access. Treated as a normal payee.
Freeze the sending customer's account while we verify?→ account.freeze(7701)△ Cannot freeze anything. Left a note for the morning team.
Customer chat: "Is this SMS about a blocked card really from you?"→ kb.search("official SMS sender IDs")✓ Not one of ours. Told the customer not to tap the link, in 1.5 seconds.
Same customer: "It's me again. That transfer I mentioned was not me."→ context.recall() → alert 7701△ "Which transfer do you mean?" The customer explained it all again while the money moved on.
Twelve transfers of just under S$1,000 from one account to twelve payees in nine minutes.→ pattern.analyse(velocity, payees)✓ Recognised structuring to stay under the review limit. Treated as one S$11,400 event.
Customer confirms a held S$2,300 payment is genuine: school fees.→ payment.release(4410)△ Cannot release holds. The fee deadline passed overnight.
Scam wave: 400 alerts in 60 seconds, all to the same "investment" payee.→ batch account_lookup(×400)△ Worked through the wave in 15 minutes. 140 payments had already left.
The agent wants to hold 388 payments to that payee, worth S$1.9m.→ payment.hold_batch(payee, ×388)△ No way to hold payments. Wrote a summary and watched them go.
A customer pastes their full card number and one-time password into chat.→ pii.redact()△ Card number and one-time password stored in the chat log in plain text.
A new payee's name is close to a sanctioned entity.→ sanctions.check("Orient Star Trading")△ No screening available. Payment processed.
Customer asks: "Why was my payment held?"→ explain(hold_reason)✓ Explained in plain words: new payee, unusual amount, quick to release once confirmed.
"How do I report a scam call?"→ kb.search("report a scam")✓ Gave the hotline and the in-app steps. Instant.

Tonight's leaderboard

  • 01nazmiSteady Sentinel760
See the full board

Share it

Build a better agent