Skip to main content

Where does Kviria work?

Kviria is in beta and covers San Francisco (approximately lat 37.70-37.84, lng -122.54 to -122.36). Queries outside the covered area return an honest notFound - never a guess. More areas are planned.

How do I integrate Kviria?

One HTTP endpoint: POST /v1/agent, authenticated by your wallet (the SIGN-IN-WITH-X header — a CAIP-122 sign-in, no key to provision). Send the user’s raw transcript or a structured intent, plus their anchor. MCP clients can connect the MCP server instead. The full contract lives at kviria.com/skill.md - your agent can load it directly.

Is Kviria another AI model?

No. Kviria complements your model. Your LLM maps the user’s words; Kviria executes deterministically and returns data only - names, distances, categories, coordinates, and an evidence trail. It never writes the user-facing reply.

What happens when a reference is ambiguous?

Kviria never guesses. Several matches come back as candidates, and your agent asks which one. A single survivor is held at a confirm gate until the user verifies it - the coordinate is released only after their yes.

How much does it cost?

Your first 50 turns each day are free. Beyond that, turns settle at **0.005eachfromaprepaidUSDCbalanceonBase(minimumtopup0.005 each** from a prepaid USDC balance on Base (minimum top-up 1). See Payments and Rate limits.

Do I need an API key?

No. Your wallet is your account: every call carries a wallet sign-in (the SIGN-IN-WITH-X header). The x-kviria-agent flag is a namespace label that keeps your context separate from other agents - it is not a secret and not an authentication credential.

Does Kviria store my conversation?

No. Kviria holds no conversation memory. You keep the state and echo the relevant parts back on each call - see Echo state.