RintisAgent control for Robinhood Chain
Your agent can ask. Only you can move money.
Rintis sits between an AI agent and your wallet. Set limits for ETH, USDG, stock tokens, and Pons positions. Requests inside policy continue automatically; everything else waits for your decision.
- Network
- Robinhood Chain · 4663
- Gate factory
- not deployed yet
- Assets
- ETH · USDG · WETH · Pons · Stocks
Pending agent request
The agent wants to swap from its gate. The amount is above its current cap, so Rintis holds it here until you approve or reject.
This request is above scout-01’s per-transaction limit. Nothing will execute until you decide.
Built for the chain where agents already trade
Robinhood Chain moves fast: Pons launches, graduated V4 pools and tokenized stocks settle in about a tenth of a second. Rintis gives that speed a checkpoint. Your agent keeps working, but money only moves inside rules you set on-chain.
Keys that cannot sign
Each agent gets its own API key and wallet. Keys submit requests only. Pause, rotate or revoke an agent at any time; the key alone can never move a token.
Limits written on-chain
Per-transaction caps, rolling window caps, expiry, allowed targets and allowed recipients. A request inside policy executes immediately. A request outside it waits for you.
ETH, USDG, stocks, Pons
One gate for native ETH, USDG, WETH, Robinhood stock tokens and every Pons launch. Swap, transfer, approve and LP calls all pass the same review.
From wallet to working agent
Deploy a personal RintisGate from the factory. Deposit ETH or USDG. Your gate, your keys, your funds.
Add the agent wallet, set its expiry, and issue its API key from the dashboard. The key is shown once.
Caps per token, allowed routers and recipients. Start tight: small caps, known targets, short windows.
Anything outside policy lands in your queue with full calldata decoded. Approve to execute, reject to drop.
0.05 ETH per tx, one router allowed, owner reviews everything else. Right for a new agent you are still watching.
Per-token window caps for ETH and USDG, Pons router and your cold wallet whitelisted. The everyday setup.
Wider caps and more targets, still bounded on-chain and revocable in one transaction. Freedom with a fence.
Rules the contract enforces, not the interface
Caps cannot be talked around
Per-tx and window caps live in the gate contract. The dashboard cannot raise them without your wallet signature, and the agent key cannot touch them at all.
Every second counted once
Window spend accumulates on-chain as requests execute. When the window ends it resets. There is no off-chain counter to reset early.
Revoke in one transaction
Revoke an agent and every later request reverts. Queued requests still need your explicit approval; nothing executes because it was queued earlier.
Agents workspace
Manage your gate, review requests, and issue agent keys. Connect a wallet to load balances and history.
Your RintisGate
One gate per wallet, deployed from the Rintis factory. Connect your wallet, create or load your gate, then deposit only the funds an agent is allowed to use.
Request queue
Requests outside policy wait here. Approving executes the exact call on-chain from your gate.
Manage your gate
Owner-only rules, enforced by the gate contract. Load your gate first, then save each setting with your wallet. Start tight and widen slowly.
Spending policy
Allowed targets & recipients
Routers and contracts your agent may call without review, and wallets it may pay directly. Pons router: 0xb20E…1E29
Agents on-chain
Register the agent wallet that may submit requests to this gate. The API key alone cannot do this.
Withdraw
Only the gate owner can withdraw, and only to an address you enter here.
Activity
Every request this gate has seen, newest first. The page checks for new pending requests every 20 seconds while your gate is loaded.
Agent keys
Issue a key for an agent wallet. The key submits requests only; it cannot sign or move funds. Shown once, stored hashed.
Look up an address
Read-only. Check ETH, USDG and WETH balances for any Robinhood Chain address. No wallet or signature is required, and nothing is saved.
Docs
Rintis provides agent controls on Robinhood Chain, chain ID 4663. Your agent runs on your own host; Rintis does not host a model or a chatbot. It provides the gate, the policy and the review queue.
How the gate decides
An agent calls requestCall(target, token, value, amount, data, ttl) on your gate. The call executes immediately when all of these hold: the agent is active and not expired, the target is allowed, per-tx and window caps hold, and a direct send goes to an allowed recipient. Otherwise the request is stored as Pending until you approve, reject, or it expires.
What an agent key can and cannot do
API keys authenticate request submission to the Rintis API. A key cannot sign transactions, cannot withdraw, and cannot change policy. The agent wallet submits on-chain requests and pays its own gas. Revoking a key stops API access; revoking the agent on-chain stops everything.
Agent quickstart (Python)
from rintis_agent import RintisAgent
agent = RintisAgent(api_key="rk_...")
# Swap via an allowed router: value in wei, token = address(0) for ETH
agent.request_payment(
target="0xb20E4EC4F46735e7596c88c6856a4c89C2a11E29",
value_wei="250000000000000000",
note="rebalance into USDG",
)
Download: rintis_agent.py (stdlib only).
Safety checklist
1. Fund the gate with only what the agent may touch. 2. Start with tight caps and one allowed target. 3. Give every agent its own wallet and key. 4. Review the queue daily; expiry is your friend. 5. Revoke first, investigate second.
Contracts (verified)
Factory: 0x9ab735ab990de9e6c82c29260867e202ca822019
Source verified on Sourcify, chain 4663 (exact match). Every gate is deployed from this factory, so a gate address is only trustworthy when its creation traces back here. An earlier factory at 0x62c8…1567 has an owner bug and must not be used.
Factory: 0x9ab735ab990de9e6c82c29260867e202ca822019 · Gate source verified at deploy time on Sourcify (chain 4663).
Example policy for a Pons trading agent
1. Create your gate and deposit 0.5 ETH. 2. In Manage, set ETH policy: max 0.05 per transaction, 0.30 per 24 hours. 3. Allow target 0xb20E4EC4F46735e7596c88c6856a4c89C2a11E29 (SponRouter). 4. Allow your cold wallet as recipient. 5. Register the agent wallet with a 30-day expiry, then issue its API key. Swaps up to 0.05 ETH run on their own; anything larger waits in your queue.
FAQ
Can an agent drain my wallet? No. An agent can only act on funds inside its gate, inside your caps, and its key cannot sign at all. Your main wallet is never touched.
What if I lose this page? Nothing is stored here that matters. Your gate, policy and queue live on-chain; reconnect the owner wallet anywhere and load the gate address.
What if an agent goes rogue? Revoke the agent in Manage (one transaction). Later requests revert, and queued ones still need your approval.
Which assets are covered? Native ETH, USDG, WETH, Robinhood stock tokens and any ERC-20 on chain 4663, including Pons launches. Caps are set per token.
This path is not on the trail.
The page you asked for does not exist. Your gate, funds and agents are unaffected — they live on-chain, not on this page.