Get Started

Introduction

Flick is an AI human-assistant agent that inspects every transaction before it is signed, audits the contracts it touches, and watches your exposure — funded per call through the x402 protocol.

On this page

Non-custodial and local-first. Flick never takes custody of your funds, and your aggregate financial graph never leaves your device.

The cost of an irreversible signature

Self-custodial finance is built on the principle that a signature is final. When a user signs a malicious approval or a drainer transaction, there is no chargeback, no fraud department, and no settlement window. The analysis that would have prevented the loss completes in milliseconds — it just isn't in the default path, because accounts, API keys, and subscriptions don't match a risk that arrives unpredictably and at machine speed.

Flick closes that gap. It sits in front of every signature, runs the analysis automatically, and pays for the intelligence it consumes one HTTP request at a time.

How Flick works

A Flick instance holds no custody and operates over three functions — Guard intercepts every signature in path, Audit answers on demand, and Watch continuously re-evaluates standing exposure.

Figure 1. Guard sits in path of every signature; Audit answers on demand; Watch runs continuously out of band.

Get started

Connect your wallet

Install the Flick agent and let it guard every signature locally — non-custodial by design.

Read the whitepaper

Understand the per-call economics and local-first privacy model behind the agent.

What can Flick do?

Guard

Simulate every transaction before signing and return an allow / warn / block verdict with a plain-language reason.

Audit

Assess any contract, token, or protocol on demand and pay only for the analysis you actually request.

Watch

Continuously re-evaluate open approvals and standing exposure, and escalate before value can move.

System architecture

A Flick instance is composed of a local core — policy, monitored addresses, the budget accumulator, encrypted history — and a set of priced remote intelligence sources reached only through the x402 payment interface. The local core never delegates custody and never exports the aggregate financial graph.

Figure 2. Every external call is metered per request via x402. The signature is gated on the returned verdict and the budget accumulator.

Payment flow (x402)

The agent holds a bounded balance b in a stablecoin on an Ethereum Layer 2 and a user-configured budget B with cumulative spend s. Each unit of intelligence is purchased through the same five-step loop.

Figure 3. The x402 settlement loop. Spend is bounded by construction; no trust is extended between agent and provider.

Use Flick from another agent

The same paid endpoint Flick uses to buy intelligence lets other autonomous agents buy a verdict from it. Submit a candidate transaction, settle the 402 Payment Requiredchallenge in stablecoins on an Ethereum Layer 2, and receive an allow / warn / block verdict before you sign.

npx -y @flick/agent@latest init --wallet

Settlement is per-call and final. No account is created, no API key is held, and no relationship persists beyond the single request.

Only the resources below are official. Do not trust any other address, contract, or download claiming to be Flick.