by Rariti  ·  agent-native money

Agent-native
stablecoin money.

Onboard, fund with fiat or crypto, issue cards that spend just-in-time from a stablecoin balance, move money across borders — and let autonomous agents pay for things under mandates their owner controls.

Open an account /api/mcp  for your agent
One mandate, every rail Card · x402 · MPP · Transfer
Tally — the ledger, at a glance.
live ledger $4,820.55

    The core idea

    One mandate, every rail.

    A mandate is a budgeted, time-boxed spending authority — an amount, an expiry, allowed merchants and domains, a per-transaction cap. Grant it to a person, an employee, or an agent. It is enforced the same way no matter how the money leaves.

    Card

    A Monkefy card, funded just-in-time from a stablecoin balance. Virtual or physical, with spend controls compiled straight from the mandate.

    cards · JIT

    Protocol

    Outbound x402 and MPP payments over HTTP 402. A denied request never even produces a signature.

    x402 v2 · MPP

    Transfer

    Transfers to bank accounts or wallets, domestic or cross-border — with corridor quotes, FX disclosure, and Travel Rule data where required.

    bank · crossborder

    Every one of those lands in the same double-entry ledger with the same attribution model. That single enforcement point is what makes Monkefy agent-native — not an app with an API bolted on.

    For agents

    Your agents can
    hold the wallet.

    Give an agent a scoped API key bound to one mandate. It can check balances, pay 402-protected resources, issue single-use cards for merchants that don't speak protocol, and preview transfers — over REST or MCP.

    • Streamable-HTTP MCP at /api/mcp, OpenAPI 3.1 at /api/openapi
    • Keys are scoped, shown once, stored as SHA-256 only
    • Mutations require an Idempotency-Key — retries replay, never double-pay
    • Single-use agent cards cancel themselves after one successful payment
    agent · paidFetch

    Under the fur

    Three sub-ledgers.
    Zero hand-waving.

    Permission is separate from value, so granting a mandate never moves money — and a card authorization consumes budget without pretending Monkefy owns the wallet balance.

    sub-ledgeraccountsanswers
    Value wallet · external · fee · fx Where did money move?
    Encumbrance auth hold · hold control What's reserved but unsettled?
    Permission mandate budget · control What is still permitted?
    402 the HTTP status we turned into a payment rail
    ~2s policy engine decides inside the live card auth window
    bigint money is integer minor units — never floats
    0 credentials needed to run the full simulator locally

    Platform

    Everything a treasury needs.

    Onboard & verify

    Individual and business KYC/KYB with per-rail endorsements — base, cards, SEPA, PIX and more unlock independently.

    Fund any way

    Bank rails via virtual accounts, direct crypto deposits, or link your own non-custodial wallet and keep custody.

    Corporate spend

    Employee cards with per-card limits and MCC controls, approval workflows, and receipt matching against real authorizations.

    Cross-border

    Quote a corridor, disclose FX honestly, capture Travel Rule data, send. Domestic or crossborder, bank or wallet.

    Agent mandates

    Budget, per-transaction cap, rolling limits, expiry, rail and domain allowlists — evaluated as a pure function, every time.

    Partner network

    Identity, cards, banking rails, and settlement run through our integration providers and service partners — one Monkefy ledger over all of them.

    Put your money
    on every rail.

    Humans get a dashboard. Agents get an API. The ledger doesn't care which one you are.

    Open an account Explore the agent API