Jump to main content
ndStill

Agents pay. You still decide

Connect the bank accounts your business already holds. Each agent gets caps, not a balance. Every transfer runs the same nine checks, and anything risky waits for a person. We never hold your money.

Create accountRead the docs
  • 01Authenticate
  • 02Go-live
  • 03Kill switch
  • 04Source account
  • 05Beneficiary
  • 06Guardrails
  • 07Anomaly
  • 08Window limits
  • 09Execute or hold

Your bank keeps the money. Your agents get caps. ndStill checks every transfer, and you approve anything out of bounds.

transfer · assembledtest mode · example
  1. Bank rail
    US · Increase
  2. Account
    ops ····4417
  3. Agent
    acme-buyer
  4. Caps
    $500 threshold
  5. Nine checks
    01–09
  6. You approve
    anything held
One example transfer assembled from its parts, in the order the checks run: the bank rail, the source account, the agent, its caps, the nine checks, and your approval for anything held. Values are test-mode examples.

What a transfer goes through

Agents can't skip a step. Here is one example, traced in test mode: it clears five checks, then the approval threshold holds it for a person.

transfer tracetest mode · example
$ POST /v1/transfers
agent:acme-buyer → Northwind Supply · $1,240.00
authagent key · scope transfers
go-liveorg KYC verified
kill switchagent active · org active
sourceops ····4417 (agent default)
beneficiaryNorthwind Supply · registered
guardrails$1,240.00 > approval threshold $500.00
statuspending_approvalwaiting for a person
An example $1,240 agent transfer passes authentication, go-live, kill switch, source account and beneficiary checks, then exceeds the $500 approval threshold and is held for a person to approve.
  1. 01
    Authenticate

    An admin key, or a key scoped to one agent.

  2. 02
    Go-live

    The org must be KYC-verified before real money moves.

  3. 03
    Kill switch

    A frozen agent, or a frozen org, stops here.

  4. 04
    Source account

    Explicit, then the agent's default, then the org's — only accounts the agent may use.

  5. 05
    Beneficiary

    Payouts on the India rail need a registered payee.

  6. 06
    Guardrailsheld here

    Hard cap, per-transfer limit, confidence floor, approval threshold.

  7. 07
    Anomaly

    Velocity and spend spikes are held automatically.

  8. 08
    Window limits

    Daily, weekly and monthly caps for each agent.

  9. 09
    Execute or hold

    Sent on your rail, or held in Approvals for a person.

Caps, not balances

Your organisation owns the bank accounts. Agents are delegates that spend from the ones you allow, up to the limits you set.

A kill switch for every agent

Freeze one agent, or every agent in the org, in one step. A frozen agent stops at the third check.

Nothing can be edited later

Every decision goes into an append-only audit log. The database itself refuses edits and deletes.

How it works

  1. 01

    Link your bank rail

    Pick the US or India rail. This lets ndStill talk to your bank; it never holds your money.

  2. 02

    Give each agent caps

    A per-transfer limit, an approval threshold, daily windows, and the accounts it may spend from. It cannot go past them.

    travel-deskpolicy · example
    per transfer
    ≤ $1,200.00
    approval over
    $800.00
    per day
    ≤ $5,000.00
    confidence floor
    0.80
    spends from
    Operating ····4417
  3. 03

    Agents pay through the API or MCP

    Each agent gets its own scoped key. It calls POST /v1/transfers, or the ndstill_transfer tool from Cursor or Claude Desktop. Test mode runs every check and moves nothing.

    POST /v1/transfers
X-API-Key: <agent key>

{
  "agent_id": "travel-desk",
  "recipient_account_id": "acct_hilton",
  "amount_in_cents": 124000,
  "llm_confidence_score": 0.91,
  "simulate": true
}
  4. 04

    You approve what the checks hold

    Anything over a threshold, unusual, or sent with low confidence waits in Approvals. Approve it and it goes out on your rail; reject it and it never moves.

What an agent can call

The MCP server gives agents in Cursor or Claude Desktop the same calls as the REST API, each one running through the same checks.

  • ndstill_create_wallet

    Add an agent as a capped delegate. It holds no money of its own.

  • ndstill_list_accounts

    List the org's bank accounts and live balances, to pick a source.

  • ndstill_get_wallet

    Look up an agent's identity, status and policy.

  • ndstill_simulate_transfer

    Run every check with no money moving, and get a trace of each gate.

  • ndstill_transfer

    Send money from an account the agent may use, within its caps.

  • ndstill_list_transfers

    List transfers, by agent or by status.

  • ndstill_issue_card

    Issue a single-use virtual card with a hard cap.

  • ndstill_approve_transferadmin

    Sign off on a held transfer, which then executes.

  • ndstill_reject_transferadmin

    Decline a held transfer. It never moves.

  • ndstill_setupadmin

    One-time bootstrap for a new org.

Put your agents on your accounts

Create accountSign in

US via Increase, sandbox today. India payouts turn on once a banking partner is live.

ndStill isn't live yet. For questions or early access, write to 10by31labs@gmail.com.