Skip to content
Hightop docs header art
Hightop
API and Integrations

Build on Hightop#

If you already run agents in your own stack, Hightop gives them a bounded way to handle money. Your agent logic stays where it is. Hightop provides the funded account, API, controls, wallet execution, monitoring, and revocation path.

What You Keep#

You keep:

  • agent logic
  • prompts, tools, memory, and schedulers
  • orchestration framework
  • product-specific business rules
  • customer-facing application code

Your system decides what should happen. Hightop decides whether the requested money movement is allowed inside the configured lane and executes it when it is.

What Hightop Takes Over#

Hightop takes over:

  • agent credentials
  • wallet and account infrastructure
  • policy enforcement
  • idempotency and operation tracking
  • approved payment paths
  • earn, borrow, conversion, and withdrawal execution
  • webhook and MCP delivery surfaces
  • human monitoring and revocation in the app

Agents get execution rights, not custody.

Integration Shape#

text
example
your agent runtime
  -> https://api.hightop.com
  -> Hightop Agent API
  -> control layer
  -> smart contract wallet
  -> payment rails and onchain protocols

Typical rollout:

  1. Fund one Hightop account.
  2. Create one Hightop agent in the app.
  3. Configure a narrow lane: permissions, limits, assets, recipients, protocols, and expiry.
  4. Generate the agent API key.
  5. Store the key in your backend secret manager.
  6. Start with reads and simulation.
  7. Add one operation-backed workflow.
  8. Poll operations or subscribe to webhooks.
  9. Expand only after the first lane is stable.

Good First Lanes#

Vendor Payments#

Let an agent pay a small set of approved vendors in USDC with tight transaction and period limits.

Conversion#

Let an agent quote and execute conversions within a limited asset set.

Earn#

Let an agent move idle cash into approved Earn opportunities and withdraw when needed.

Withdrawal#

Let an agent withdraw to prepared destinations only after the destination is visible and allowed.

MCP#

Let an MCP client call the same Agent API surface through tool calls and receive operation notifications.

Start Narrow#

Start with:

  • one account
  • one agent
  • one job
  • one payment or capital-management path
  • one asset, often USDC
  • short expiry
  • tight per-transaction and period limits
  • webhooks or operation polling

That gives you a small blast radius and clear operational evidence before you widen the lane.

Builder Entry Points#

Previous

MCP

Next

x402 Payments