Pay for a service.
Route payments between agent workflows and service providers without exposing a simple, direct transfer pattern.
Explore oobe and EarnFi ↗FOR AUTONOMOUS SYSTEMSAgents act.
Agents act.
MultiHopper routes.
Give your agent control over how assets move. Programmable hops, configurable timing and compliance screening become part of the workflow.
A PAYMENT PRIMITIVE
From a decision to a routed transfer.
An agent can request a paid service, fund a task or move treasury assets. MultiHopper supplies the programmable routing step.
Move around a strategy.
Compose asset movement with swaps, staking and treasury operations while keeping routing parameters under programmatic control.
Execute recurring intent.
Trigger transfers from your application’s rules, then follow their status through the documented lifecycle.
Integration guide ↗CONTROL THE PARAMETERSYour timing.
Your timing.
Your hop count.
Define the delivery window and the number of routing steps that suit your workflow. Balance abstraction with execution time, then inspect the quote before authorizing the transfer.
The agent supplies the intent. Your signing and authorization policy stays part of your integration.
Understand route configuration ↗MACHINE DISCOVERY
Make the integration discoverable.
Use the published specifications and agent-facing documentation to connect your tooling.
API specification.
Inspect the machine-readable definition of the API.
Open the specification ↗Server card.
Discover the documentation MCP at dev-docs.multihopper.com/mcp. Its two read-only tools, search_multi_hopper and query_docs_filesystem_multi_hopper, search and retrieve documentation.
Open the server card ↗llms.txt.
Give your agent a concise entry point to MultiHopper documentation.
Read llms.txt ↗START BUILDING
An integration with clear steps.
Get environment-specific credentials
Start with devnet keys from the developer dashboard.
Use the API for transfers, MCP for docs
Use the authenticated REST API for transfer execution and your own wallet-signing policy. The documentation MCP helps agents read the guides; it does not execute transfers.
Set routing and authorization rules
Configure transfer parameters, wallet signing and how your agent responds to failures.
Monitor the transfer
Consume transfer status and lifecycle events so your application knows what happened.
ROUTING, EXPLAINED
Privacy with isolated transfers.
Every route is separate. MultiHopper combines onchain abstraction with compliance screening, without commingling user funds.
What does the agent control?
The integration defines the asset, recipient and supported routing parameters, including hop count and arrival timing. Your application controls its own authorization policy.
Does using MultiHopper remove compliance obligations?
MultiHopper provides integrated screening and routing infrastructure. The application still needs policies appropriate to its own users, activities and jurisdictions.
How do oobe and EarnFi use the routing layer?
The use cases on our homepage distinguish agent-to-agent services from agent-funded work. Both use programmable movement as a component of a wider workflow.
Where do I get API access?
Open the developer access section for devnet and production dashboards.
Is partner revenue sharing available?
Qualifying integration partners can participate in 50/50 fee revenue sharing. Contact the team to discuss current terms.
Give your agents a routing primitive.
Build autonomous asset movement on infrastructure designed to be programmed.