← Ulvane

FAQ

Questions we hear most often — from developers wiring up an agent and from people reviewing the product.

Why no accounts or API keys?

Ulvane is built for AI agents, not humans filling out a signup form. x402 lets an agent pay per request in USDC and get an instant response — no signup flow an autonomous agent could actually complete on its own.

Is paying per call safe?

Payment goes through x402's "exact" scheme via Coinbase's own CDP facilitator — the same infrastructure Coinbase uses for its own x402 integrations. You pay only for the exact request you make; there's no subscription or stored balance that could be drained.

Where does the data come from?

Base mainnet's own onchain swap history, read live from a GraphQL data provider. PnL, risk, and trader rankings are computed directly from real swaps — not cached from a third-party score API.

Why x402 instead of a normal REST API with an API key?

It matches how an autonomous agent actually wants to consume a paid service: no human account-creation step, no key to leak or rotate, and cost that scales exactly with usage.

What does "unverified" mean on the risk endpoint?

It means the token isn't on our hand-curated allowlist yet — not that it's unsafe. The allowlist only grows once we've manually confirmed an address against BaseScan or the project's own site.

Why do results sometimes look incomplete for very active wallets or tokens?

Every response reflects a bounded recent-swap window (see each response's windowNote), not full history. A wallet or token with thousands of trades will show a partial picture until we move off the current free-tier data plan.

What chain do you support?

Base mainnet only, for now.

Build on