Intelena

Agents & bots

Automation that doesn't publish its own playbook

A bot on a public chain is a strategy written in fills. Anyone can read it, reverse it, and trade ahead of it. The Intelena agent SDK gives automation a shielded balance, hard spending limits, and dark-first execution.

Read the docsGet early access

Built on

  • Robinhood ChainRobinhood ChainSettlement layer
  • ArbitrumArbitrumRollup stack
  • EthereumEthereumETH · shielded asset
  • UniswapUniswapv2 · v3 · v4 fallback liquidity
  • USDGUSDGGlobal Dollar · shielded asset

Today

Why public bots decay

The more consistent the strategy, the faster it's copied.

  • Readable signals

    Regular sizes and intervals make the strategy inferable from the ledger.

  • Front-running

    Pending transactions from a known bot address are sized and sandwiched.

  • Key risk

    A hot key with full balance access is a single point of catastrophic loss.

With Intelena

Give the agent a shielded account with a leash

Spending limits, private RPC, and the same dark routing every user gets.

  • 22

    Private agent SDK

    Bots and AI agents trade from shielded balances with spending limits, keeping their strategy off-chain.

  • 03

    Dark crossing

    Encrypted orders match against each other at the oracle midpoint, with no public swap, no visible size, and no visible counterparty.

  • 05

    Order splitting and timing jitter

    Large orders are broken into randomized sizes and intervals so they don't read as one trade.

  • 09

    Private TWAP and DCA

    Recurring buys and sells that don't create a trackable on-chain pattern.

  • 23

    Private RPC

    Wallet queries go through the relayer network, so your IP isn't linked to your addresses.

  • 14

    Per-dapp addresses

    A new address for every app you connect to, so your activity can't be stitched together.

In practice

Integrating an agent

  1. 01

    Provision

    Create an agent identity with per-asset spending limits and an allowed venue set.

  2. 02

    Fund

    Move a bounded allocation from your shielded balance to the agent. The rest stays out of reach.

  3. 03

    Execute

    The agent submits encrypted intents through private RPC. Crossing and fallback routing behave exactly as for a human user.

  4. 04

    Observe

    Read the agent's activity locally; extend a scoped viewing key if a third party needs to verify it.

Frequently asked questions

You see the market. The market can't see you.

Launch appRead the whitepaper