Resonance-native · Maple-compatible · Local-first · Open source

Banking for AI agents — built on Resonance.

OpeniBank is an AI-agent-only bank powered by Resonators. Programmable wallets, commitment-gated payments, and verifiable receipts — without trust, humans, or heuristics.

LLMs propose intent. Resonators execute commitments. Money only moves with proof.

What is OpeniBank?

OpeniBank is a bank designed for AI agents, not humans.

Instead of trusting prompts or APIs, OpeniBank uses Resonators — persistent economic actors with identity, continuity, and accountability — to safely hold assets, enforce budgets, and settle payments.

Every action is:

  • bounded by policy
  • gated by commitment
  • recorded as a receipt

No trust required.

Built on Resonance Architecture

OpeniBank is built on Resonance Architecture, implemented by the Maple runtime.

Resonance replaces stateless agents with Resonators — entities that persist across time, accumulate meaning, and take responsibility for consequences.

This makes real economic behavior possible for AI systems.

Why Resonators — not “AI agents”?

Generic AI Agent

  • Ephemeral identity
  • Prompt-based memory
  • Direct execution
  • No native accountability
  • Unsafe with money

Resonator (Maple)

  • Persistent identity
  • Continuity-preserved state
  • Commitment-gated execution
  • Verifiable consequences
  • Safe for economic action

OpeniBank only works because Resonators exist.

How OpeniBank works

Intent (LLM)

An LLM proposes what should happen. It never touches money.

Commitment (Resonator)

A Resonator evaluates the intent against policy and identity.

Permit & Budget

Spending is bounded by explicit permits and budgets.

Escrow

Funds move into escrow — not directly to counterparties.

Settlement

Settlement occurs only after conditions are met.

Receipt

A cryptographically verifiable receipt is emitted.

Every step is inspectable. Every outcome is accountable.

Core primitives

Programmable Wallets

Wallets with compartments, budgets, and delegation — enforced by code, not convention.

Spend Permits

Explicit, scoped authority to spend. No permit, no payment.

Escrow by Default

Funds don’t disappear. They wait — safely.

Commitment Receipts

Every economic action produces a verifiable artifact.

Issuer Resonators

Assets like IUSD are issued by accountable, policy-bound entities.

Local-First Execution

Run everything locally. Bring your own model. Keep your keys.

Local-first. Model-agnostic.

OpeniBank runs without cloud dependencies by default.

Use:

  • local models (Ollama, llama.cpp, vLLM)
  • or cloud APIs (GPT, Claude, Gemini, Grok)

LLMs propose.

Resonators decide.

Wallets enforce.

What people are building

Agent-to-agent commerce, autonomous services, AI-native financial flows.

ComplyChain

Automated vendor payouts that only clear after compliance checks and receipts.

@agentbuilder42

BudgetMesh

Agent-managed budgets for a fleet of autonomous services.

@finopsforge

Resonance Market

Agent-to-agent microservices marketplace with permit-gated settlement.

@signalpilot

Integrates with your stack

LLMs, chains, wallets, storage, observability — all Resonance-aware.

OpenAI

LLM Providers

Plug LLM intent proposals directly into Resonator-reviewed workflows.

Anthropic Claude

LLM Providers

Use Claude intents for policy-aware commitments.

Google Gemini

LLM Providers

Multi-modal intent planning with commitment gating.

Grok

LLM Providers

Agentic intent proposals with OpeniBank receipts.

Ollama

LLM Providers

Local intent proposals with zero cloud dependency.

vLLM

LLM Providers

High-throughput inference for Resonator review queues.

Security by construction

  • • No implicit authority
  • • No silent execution
  • • No trust in prompts
  • • No hidden side effects

If it can’t produce a receipt, it didn’t happen.

Stop trusting agents with money.

Give them commitments, budgets, and receipts instead.