$SECTORAL - 0x6effbf4438140222b8a6e7bd0dc3245206946fce

Private banking
for people and
the agents they run.

Transfers are encrypted before they ever leave your account, then settle in 100ms blocks. Each agent gets an account of its own, pays over x402 natively, and can never go a cent past the limits you define.

01To settle a block
120ms
02Fees on transfers while in beta
$0.00
03Amounts visible on-chain in plaintext
0
04Agents covering their own payments
24/7
ConsoleInside the app
Built on / works with

Wired into the infrastructure agents already use

Robinhood ChainChainlinkUSDGSafeUniswapMorphoFoundryx402
01Agents with wallets

Software now has
its own bank accounts.

  • 01Non-custodial
  • 02Confidential
  • 03Checked on Robinhood Chain

Right now, AI agents are earning, spending and settling with one another at every hour of the day. Sectoral gives them a private place to do it. It is a non-custodial neobank where people and agents move money confidentially, with each settlement checked on Robinhood Chain.

02What you get

All the tools of a private bank.
None of the prying.

People and their agents share a single protocol. The chain itself enforces each feature listed here, rather than a promise written in a policy.

Module0105
Accounts

A single account. People and agents alike.

Accounts for people and accounts for AI agents sit next to each other on the same protocol. They are non-custodial, shielded with ZK, and governed by spending policies on-chain rather than rules on a server. Your funds take orders from you, not from a database.

Specification04 items
  • 1.1Accounts for people
  • 1.2Accounts for agents
  • 1.3Multi-signature vaults
  • 1.4Handles ending in .sectoral
More on accounts
Fig. 01Accounts
Accounts
AliceMain
@alice.sectoral
Confidential2-of-3 Safe multisig
Balance
•••••USDG
Only your view key can reveal this
Latest activity
  • vendor.sectoral
    Settled · 2h ago
    •••••
  • payroll.sectoral
    Settled · 1d ago
    •••••
  • Alice to Datafetch
    Settled · 3d ago
    •••••
Shared protocol
Datafetch
datafetch.sectoral
Confidentialbelongs to @alice.sectoral
Spending rules
Request ceiling$5.00
Per-day cap$50.00
Approved domains2
Where it's enforcedOn-chain
Today · parent budget
$12.40 of $50.00back to zero at 00:00 UTC

The protocol reverts any attempt to overspend. There is no custodian and no way to override it.

Module0205
Privacy

Private from the start. Open to audit on your terms.

ElGamal encryption covers every amount, and ZK range proofs show it is correct. No observer can read it, yet anyone can verify it. Whenever you decide to share, a view key exposes only what you pick and nothing beyond that.

Specification04 items
  • 2.1Encrypted amounts
  • 2.2State kept shielded
  • 2.3Range proofs in ZK
  • 2.4Read access via view keys
More on privacy
Fig. 02Privacy
Transfer
alice.sectoralvendor.sectoral Complete
Visible on-chain
Sender
0x7fA2...e91cstealth
Recipient
0x3bD8...a04fstealth
Amount
Memo
ElGamal ciphertext
0x8f3a2c1d 9e4b7f6a 0c5d8e2f
0x1a4b7c9d 3e6f2a1b 8c5d0e4f
0x6b2e9f1a 7c43d8e5 b0f4a29c
Range proof (ZK)
Valid
Visible to you
Via view key
Amount
$1,240.50USDG
Fromalice.sectoral
Tovendor.sectoral
Fee$0.02
MemoInvoice #2210
Sent atApr 26 · 14:32:08
Settled atApr 26 · 14:32:09

Your client does the decrypting, so the plaintext never reaches the chain.

Module0305
Agents

Agents that cover their own costs.

An agent account handles x402 payment requests by itself, without anyone stepping in. Because spending policies live on-chain, no agent can exceed its mandate, and MPP routing breaks each payment apart to keep it private.

Specification05 items
  • 3.1The x402 protocol
  • 3.2Spend policies
  • 3.3SDK for agents
  • 3.4Routing with MPP
  • 3.5Nested agent hierarchies
More on agents
Fig. 03Agents
datafetch.sectoral
Live · x402 payment trace
session 0x4c19...ab27
GET api.marketfeed.io/v1/market-data
server replied402 Payment Required
x402 price · 0.25 USDG each request
CHECKING POLICY · spend policy v3
request ceiling · 0.25 <= 5.00
api.marketfeed.io is on the allowlist
spent today · 12.40 / 50.00
encrypted transfer sent · observers cannot see the amount
final · 100ms · 1 block
GET again, now with X-Payment header
server replied · 4.1 KB body200 OK
Spent
0.25 USDG
Remaining budget
$37.35
The chain enforces the policy, and each request covers its own cost.
Module0405
Protocol

Each payment takes a private path.

Multi-Path Payments break a transfer into pieces sent along parallel routes, so nobody watching can see all of it. Settlement is still atomic. Stealth addresses keep receipts from being linked together. Anyone trying to surveil it comes away with nothing.

More on protocol
Fig. 04Protocol
Router (MPP)
Sender
alice.sectoral
$4.00
only you can see this
everyone else sees
01 Stealth addr
0x7f3a...c19b
used once, then discarded
02 Stealth addr
0x2e8d...41f6
used once, then discarded
03 Stealth addr
0x9c04...b7e2
used once, then discarded
Recipient
vendor.sectoral
Complete
whole amount in a single balance
no link between routes
Settles atomically
0x9e2d6b0a4f81c53e7a9d2f60...
unlinkable · 1 block · 3 routes
Module0505
Transparency

Share what you choose. Prove everything.

The chain proves that each transaction happened, while the amounts remain encrypted. A view key gives an auditor read-only access, the public sees nothing, and custody stays with you the whole time.

Specification03 items
  • 5.1Receipts recorded on-chain
  • 5.2Disclosure you control
  • 5.3Exports for audits
More on transparency
Fig. 05Transparency
Disclosures
Granting a view key
Can be revoked
Auditorauditor.sectoral
CoversTransfers in Q1 2026
PermissionView only
EndsApr 30 2026
Send view key

Lets the holder decrypt only the transfers in scope. You can pull access at any time.

Your auditor sees precisely what you share. To everyone else it stays ciphertext.

Checks
4 / 4
Proof of existence recorded on-chain
all 142 of 142 transfers anchored
Every ZK range proof checks out
checked with nothing decrypted
Only the auditor sees decrypted amounts
client side, with a scoped view key
Nothing made public
no change to chain state
audit-export-q1.csv38 KB Signature ok
03Getting started

Three steps take you from a new account to your first confidential payment.

Sequence3 stages
  1. Stage 01T-2

    Create your account

    All it takes is an email and a passkey. We verify your identity a single time, your keys are made on your device, and your balances never leave it unencrypted.

    DurationDone in less than two minutes
  2. Stage 02T-1

    Add USDG

    Move in Global Dollar on Robinhood Chain, or top up straight from a wallet. A small ETH reserve pays gas on its own, so fees never need your attention.

    CreditCredited in the next block
  3. Stage 03T-0

    Pay in private. Hand work to agents.

    Send an encrypted amount to any @handle, or create an agent account with a spend policy and let it cover its own costs over x402.

    SettlementSettles in 100ms
04Developers

Build private banking before the day is out.

One lightweight, typed SDK wraps the REST API. A single client covers accounts, encrypted transfers, agent accounts with spend policies, and webhooks.

  • 01
    Typed end to end, idempotent out of the box
    Each create call includes an idempotency key, which makes retries safe even when a process restarts.
  • 02
    Webhooks worth relying on
    Settlements, policy hits and agent actions each arrive as signed events that a single helper verifies.
  • 03
    Separate test and live keys, with no mode flag
    The key prefix tells the client which environment to use, so there is no setting to get wrong.
quickstart.ts
import { Sectoral } from "@sectoral/sdk";

const bank = new Sectoral({ apiKey: process.env.SECTORAL_API_KEY });

// On-chain, the amount stays encrypted. You get confirmation
// that it settled, never the figure itself in plaintext.
const transfer = await bank.transfers.create({
  to: "@vendor",
  amount: "125.00",
  asset: "USDG",
  memo: "Invoice #4471",
});

// Spin up an agent with a separate account and a strict budget.
const agent = await bank.agents.create({
  handle: "datafetch",
  policy: { dailyLimit: "50.00", maxPerRequest: "5.00" },
});

console.log(transfer.status, agent.address);
npm i @sectoral/sdk
05FAQ

Plain answers to common questions.

Still curious? Read the complete FAQ.

Does Sectoral make me anonymous?

No, by design. We verify who you are when the account is opened, and your address is visible on-chain. The part we keep hidden is how much moves through the account. Think confidentiality, not anonymity.

Will I need to know how blockchains work?

Not at all. Signing up takes an email and a passkey, much like turning on Face ID in any other app. Key management, encryption and settlement all happen automatically in the background.

What is an agent account, exactly?

Each agent receives a dedicated smart account on Robinhood Chain plus an Agent ID that sits under your parent account. Everything it does is bound by a spend policy you write, covering daily limits, approved recipients, time windows and, if you want one, a threshold above which a human must approve.

Could an agent overspend what I allowed?

It can't. The spend policy is checked before anything gets signed, rather than audited afterwards. A transaction that breaks the policy is never built in the first place.

How do I show a payment to an auditor?

Hand them a view key. It opens read-only access to the specific transfers you choose and nothing more, and you can withdraw it whenever you like. You keep custody throughout.

How much does it cost?

While we are in beta, it's free. The only charge is Robinhood Chain gas, usually a fraction of a cent, and your ETH reserve pays it for you automatically.

Banking, rebuilt

Where agents
keep their money.

Get set up in a few minutes. It costs nothing in beta, and your very first transfer is already private.

Sectoral payment card