Security on Vectr
Vectr handles wallets, API keys, trading and AI agents — so the rules are simple: you confirm before anything signs, keys are scoped, and every contract is on the explorer. The controls below are served live from the API's platform descriptor.
Custody
- Your own wallet
- Connect any EVM wallet and sign everything yourself — Vectr never sees a key.
- Vectr wallet (X login)
- Logging in with X creates a custodial wallet. Private keys are stored encrypted (AES-256-GCM).
- Key export
- Private-key export is disabled until it can be gated behind re-authentication. Need out? Contact support rather than waiting on a raw key over HTTP.
- Creator fees
- Curve fees accrue in the FeeCollector contract and are claimed by the token's fee recipient — the only balance that contract ever holds.
Transaction controls
- Confirmation first
- Nothing signs without your confirmation. The AI never writes raw calldata — it builds typed intents the backend validates on its own.
- Selector + target whitelist
- Before signing, the wallet service checks the calldata selector against a per-action whitelist and the target against known platform contracts.
- Spending limits
- Optional daily and per-transaction USD limits, enforced server-side before anything is signed.
- Pause switch
- One switch halts all signing for the wallet.
- Recipient allowlist
- Restrict outgoing transfers to addresses you approve, with a cooldown before new recipients activate.
- Contract-call guard
- A switch to block arbitrary contract calls entirely, limiting the wallet to known Vectr actions.
- Anomaly detection
- Transfers well above a wallet's rolling average get flagged before they sign.
API keys
- Scoped keys
- Keys can be read only, read write, ip allowlist, recipient allowlist — and shown in full only once at creation.
- Read-only can't broadcast
- A read-only key is rejected at the signing layer — it can read data and prepare work but never submit a transaction.
- Read-write keys can move funds
- A read-write key can broadcast through /wallet/sign-and-submit — treat it like a password and prefer read-only keys for data access.
- Instant revocation
- Revoke any key from your profile and it stops working immediately.
Contracts & source
- Not upgradeable
- Tokens and curves are EIP-1167 clones of fixed implementations — there is no proxy admin key that can rewrite them.
- Locked liquidity
- Graduation mints a full-range Uniswap V3 position into VectrLPLocker — it can never be withdrawn.
- Platform fees never pool
- The platform's 0.67% share is pushed to platform wallets in the same transaction; the FeeCollector only ever holds unclaimed creator fees.
- Fee cap on-chain
- No fee rate can be set above 5.00% — a bound enforced by the contract, bounding what even a compromised owner key could charge.
- Open source
- The contracts, CLI, MCP server and skills are public in the Vectr git.
Your controls, in the product
Spending limits, recipient allowlists, contract-call blocking and the pause switch live in your profile security tab. API keys are created and revoked there too, and every transaction still waits for a confirmation in the Terminal.
A note on claims
This page describes what the code does — rendered from the platform descriptor on GET /config and the contracts on robin.etherscan.io. On-chain trading carries smart-contract, liquidity and automation risk — transactions are irreversible. If you find a vulnerability, report it through the source repo or the contact in /.well-known/security.txt.