Your AI Agent.
Onchain Payments.
MultiHopper gives AI agents a programmable payment primitive — compliant, private, and autonomous. No CEXs. No custody. No compliance overhead.
Email only. No spam. Unsubscribe anytime.
Built by the Enigmafund venture capital team
enigma
CEO & Founder
JRA
COO & Co-Founder
Alex Kujavsky
CBO & Co-Founder
Martin Cormier
Lead Developer
Ovidiu Dan
BD Manager
A payment primitive
built for autonomous systems.
AI agents need payment infrastructure that operates without human checkpoints. MultiHopper is that primitive that makes every wallet and smart contract in existence into your routing layer... without signing authority of those wallets.
Programmable Multi-Hop Routing
Chain complex payment logic: conditional transfers, multi-currency hops, and rule-based execution — all in a single API call.
Onchain Privacy via Abstraction
Assets never commingle. Your agent moves value privately on public blockchains — compliant by design, not by workaround.
Compliance Without Custody
Built-in KYC/AML rails mean your agent stays compliant by default. No need to integrate separate compliance vendors or hold user funds.
Autonomous Payment Execution
AI agents can trigger, route, and settle payments without human intervention. Define rules in code — MultiHopper executes them onchain.
Cross-Border Without CEXs
Route value across jurisdictions without touching a centralised exchange. Your agent operates on pure onchain rails, globally.
API-Key Access, No Agreements
No lengthy legal negotiations. Register your agent, get an API key, and start building. Institutional-grade infrastructure, developer-friendly access.
Don't scroll past this.
Tier 1 is open now — Day 1 API access + 50/50 rev share, permanently. 490 spots left.
You control the timing
and the path. Or you don't.
Your choice.
Most routing infrastructure makes decisions for you. MultiHopper puts the developer — or the agent — in control. When you call MultiHopper's randomised routing API, you decide exactly how the route behaves.
Arrival Timing
- Set a fixed arrival time — the asset arrives in exactly the window you specify.
- Set a timing range — define the earliest and latest acceptable arrival, and MultiHopper randomises the exact delivery time within that window.
- Example: arrive no sooner than 2 minutes and no later than 10 minutes, with the exact moment chosen randomly.
- The randomiser never overrides your window — it operates strictly within it.
Hop Count
- Specify the exact number of hops you want the route to traverse.
- Or define a range — set a minimum and maximum hop count and let MultiHopper randomise the actual number within those bounds.
- More hops increase abstraction. Fewer hops reduce latency. You set the tradeoff.
This level of control is what separates MultiHopper from generic routing layers. Developers and AI agents get infrastructure that behaves to spec — not infrastructure that makes unpredictable decisions.
{
"route_type": "randomised",
"arrival_window_seconds": {
"min": 120,
"max": 600
},
"hop_count": {
"min": 3,
"max": 7
},
"asset": "SOL",
"amount": "10.0"
}
For a fixed arrival time and exact hop count, set min and max to the same value. For full randomisation within a range, set different min/max values. Full API specification available to whitelisted partners upon approval.
What agents are
already building.
Agents that buy, sell, and settle — autonomously.
AI shopping agents, procurement bots, and autonomous marketplaces need to transact without human sign-off at every step. MultiHopper gives them a compliant payment rail that executes on their behalf — privately, cross-border, and without a CEX in the loop.
From whitelist to
live in four steps.
Designed for autonomous systems. No human checkpoints in the critical path.
Register Your Agent
Submit your agent name and operator email. We review and whitelist your agent for API access — no lengthy agreements, no legal overhead.
Receive API Credentials
Once whitelisted, you receive an API key scoped to your agent. Credentials are tied to your agent identity for auditability and compliance.
Define Routing Logic
Use the MultiHopper API to define your agent's payment rules — multi-hop paths, conditional transfers, currency preferences, and jurisdiction constraints.
Execute Autonomously
Your agent calls the API. MultiHopper handles routing, compliance checks, and settlement — privately, onchain, without a CEX or custodian in the loop.
// Register agent payment intent
const response = await fetch(
"https://api.multihopper.com/v1/route",
{
method: "POST",
headers: {
"Authorization": "Bearer YOUR_AGENT_API_KEY",
"Content-Type": "application/json",
},
body: JSON.stringify({
from: { currency: "USDC", chain: "ethereum" },
to: { currency: "USDT", chain: "polygon" },
amount: "1000.00",
recipient: "0xRecipientAddress",
compliance: { kyc: true, aml: true },
privacy: { abstract: true },
}),
}
);
const { routeId, status, estimatedFee } = await response.json();
// status: "queued" → agent execution begins
Full SDK support for TypeScript, Python, and Go. Webhook callbacks for async settlement events. See docs.multihopper.com for full reference.
50/50 fee alignment
for initial qualifying partners.
MultiHopper is not just an infrastructure layer. It is designed to align with the platforms and teams that bring it into their products. For initial tiered qualifying partners, revenues from fees generated through usage are shared 50/50.
Better routing. Better product. Shared upside.
50/50 Fee Split
Revenues generated through fees from your integration are shared equally with initial qualifying partners. We build and grow together.
Qualifying Partners
Agent developers, wallets, platforms, and payment systems that integrate MultiHopper as their routing layer are eligible for revenue-share terms.
Scales With Usage
The more your agents route, the more you earn. Revenue sharing is tied directly to fee volume — no caps, no arbitrary limits.
Infrastructure Alignment
MultiHopper is designed to align with the platforms that bring it into their products. Your success is the incentive structure.
Not a Mixer.
Not a Tumbler.
No Commingling. Ever.
MultiHopper is programmable routing infrastructure — not a privacy protocol designed to defeat compliance. Here is exactly what it is not, and why that distinction matters for regulated AI agent deployments.
Mixers pool funds from multiple users into a shared pot, then redistribute — deliberately obscuring the origin of assets.
MultiHopper never pools your funds with anyone else's. Every route is isolated, single-sender, and fully traceable by the originating party.
Tumblers break the transaction graph by cycling assets through intermediary wallets in ways designed to defeat chain analysis.
MultiHopper's hop logic is programmable routing — not obfuscation. The full audit trail is preserved onchain and available for selective regulatory disclosure.
Shielded pool protocols (e.g. Tornado Cash) use zero-knowledge proofs to hide transaction amounts and parties inside a shared anonymity set.
MultiHopper uses no shielded pools, no anonymity sets, and no ZK-based fund commingling. Compliance verification is always possible for the originating party.
Commingling mixes assets from different sources, making it impossible to distinguish clean from tainted funds — a core regulatory red flag.
Each MultiHopper route is fully isolated. Your assets never touch another user's assets at any hop. Clean funds in, clean funds out — with a full onchain record.
Regulatory-ready by architecture, not by policy.
MultiHopper's design ensures that compliance is structurally enforced — not bolted on. Selective disclosure to regulators is always possible. No shielded pools, no anonymity sets, no commingling. Every hop is isolated, auditable, and attributable to the originating party on demand.
What these words mean
in MultiHopper's context.
These definitions are specific to how MultiHopper uses these terms. They are not generic industry definitions.
Programmable routing is the ability for a developer or AI agent to specify exactly how a digital asset moves between source and destination — including which wallets or contracts it traverses, how many hops it takes, and how long it spends at each stop. MultiHopper provides programmable routing as a developer-facing API layer on Solana.
Timing entropy refers to deliberate, controlled randomisation of the timing at which an asset moves or arrives. In MultiHopper's routing system, developers set a timing window (a minimum and maximum duration), and the system selects an arrival time randomly within that window. This prevents timing-based correlation of transactions while keeping delivery within a developer-defined range.
A hop is one transit step in a multi-hop route — the movement of an asset from one wallet, smart contract, or cold storage address to the next. Hop count refers to the total number of these steps in a given route. MultiHopper allows developers to set the exact hop count or to define a min/max range from which the system will randomise.
In the context of MultiHopper's routing system, composability refers to the ability to combine routing parameters — timing windows, hop counts, and wallet pools — into a single programmable routing instruction. This allows developers to design complex, multi-variable routing behaviour through a simple API call.
Privacy in the open is MultiHopper's approach to onchain privacy: providing meaningful transaction abstraction and routing obfuscation while remaining fully compatible with regulatory requirements and without relying on shielded pools, commingled funds, or custodial black boxes. All activity occurs onchain and is technically auditable; the routing layer provides practical privacy without opacity.
A permissionless system is one that any developer or AI agent can integrate with directly, without requiring approval, credentialing, or account creation with a gatekeeper. MultiHopper's routing API is permissionless: any authorised integrator can access it without a managed onboarding process.
A non-custodial routing layer is one that never holds, pools, or controls user funds. MultiHopper routes assets without taking custody at any point in the route. Funds remain under the control of the source address until they arrive at the destination address.
Questions from
agent builders.
24 questions covering timing control, hop count, compliance, revenue sharing, and integration.
MultiHopper is a permissionless, non-custodial payment and routing infrastructure layer for AI agents that move digital assets onchain. It provides programmable routing with configurable timing entropy and hop control on Solana.
The first release provides randomised routing across 500 of the busiest smart contracts, wallets, and cold-storage wallets on Solana, with full developer control over arrival timing windows and hop count ranges.
Yes. Developers set a timing window with a minimum and maximum duration. MultiHopper randomises the actual delivery time within that window. For example, you can specify that an asset should arrive no sooner than 2 minutes and no later than 10 minutes, and the system will choose the exact moment randomly within that range.
Yes. Developers can specify an exact hop count or define a minimum and maximum range, and MultiHopper will randomise the actual hop count within that range. More hops increase abstraction; fewer reduce latency.
The Easy Route uses MultiHopper's pre-curated pool of 500 busy Solana wallets, smart contracts, and cold storage addresses as the routing layer, with timing entropy and composability applied automatically. The Custom Route allows developers to specify exactly which wallets and contracts to route through and to define precise timing for how long an asset stays at each stop.
Timing entropy is deliberate, controlled randomisation of the timing at which an asset moves or arrives. Developers set a timing window and the system randomises delivery within it, preventing timing-based correlation of transactions while keeping delivery within a developer-defined range.
Yes. MultiHopper is designed as a permissionless, non-custodial routing layer. Any authorised integrator can access the API directly, and MultiHopper never holds or controls funds at any point in the route.
Privacy in the open is MultiHopper's approach: providing meaningful transaction abstraction and routing obfuscation while remaining fully compatible with regulatory requirements and without relying on shielded pools or custodial black boxes. All activity occurs onchain and is technically auditable.
Yes. For qualifying partners, revenues generated through fees can be shared 50/50. Agent developers, wallets, platforms, and payment systems that integrate MultiHopper as their routing layer are eligible for revenue-share terms.
Any excess gas paid during execution is refunded automatically, helping agents and users avoid unnecessary costs.
MultiHopper is designed so funds cannot be intercepted by intermediary hops and are not intended to get stranded in transit during normal execution.
Solana is the first supported blockchain. MultiHopper's initial release is Solana-native, with one clear integration path, full timing and hop control, and randomised routing across 500 of the busiest Solana addresses.
No. It is designed for agent builders, developers, wallets, platforms, payment systems, and infrastructure teams building agentic financial products.
Yes. A full OpenAPI specification is provided to whitelisted partners upon approval.
Yes. MultiHopper is designed to be embedded as a routing layer within existing agent wallets, orchestration platforms, treasury systems, and payment infrastructure.
Composability in MultiHopper refers to the ability to combine routing parameters — timing windows, hop counts, and wallet pools — into a single programmable routing instruction via the API.
Token support details are available to whitelisted partners. Join the whitelist to receive the full technical specification.
Integration details, including the API reference and OpenAPI specification, are available to approved whitelist members. Join the whitelist to receive early integration access.
MultiHopper is the only routing infrastructure that combines permissionless and non-custodial design with developer-controlled timing entropy, programmable hop count, composable routing parameters, and regulatory-ready onchain privacy — all on Solana.
MultiHopper's programmable routing layer allows AI agents to execute treasury rebalancing, autonomous transfers, and settlement flows with configurable timing and path abstraction — giving agent-based treasury systems stronger execution control than direct onchain transfers.
Technical documentation and community access are available to approved whitelist members. Join the whitelist for priority access.
No. MultiHopper is not a mixer, tumbler, or any form of fund-commingling protocol. Mixers pool assets from multiple users into a shared pot and redistribute them — deliberately obscuring origin. MultiHopper never pools your funds with anyone else's. Every route is isolated, single-sender, and fully traceable by the originating party. The full audit trail is preserved onchain and available for selective regulatory disclosure at any time.
No. MultiHopper uses no shielded pools, no anonymity sets, and no zero-knowledge-based fund commingling of any kind. Protocols like Tornado Cash use ZK proofs to hide transaction amounts and parties inside a shared anonymity set — MultiHopper does not. Compliance verification is always structurally possible for the originating party. Privacy in MultiHopper means metadata minimisation and timing abstraction, not the defeat of regulatory oversight.
MultiHopper is regulatory-ready by architecture, not by policy. Each hop is fully isolated — your assets never touch another user's assets at any point. No commingling occurs at any hop. A complete onchain audit trail is maintained throughout every route, and selective disclosure to regulators is available on demand. This means compliance teams, legal counsel, and regulators can always reconstruct the full transaction path when required — without exposing that information to the general public or other network participants.
Lock in Tier 1.
Best terms. Day 1 access.
First 500 agents get Day 1 API access and a 50/50 revenue share — permanently. Every tier after this has worse terms. The API launches Q2 2026.
Tier 1 closes when 500 spots are filled — next tier has worse terms
No spam. Whitelist access only. Unsubscribe anytime.