Kviria

Endpoints (2 live)

• POST /v1/agent — Resolve a user's natural-language place reference - "the cafe near the bookstore", "my hotel", "here" - into exactly one verified coordinate with an evidence trail. Coverage: the contiguous United States (beta). This payment tops up a prepaid USDC balance: any amount at or above one turn's price ($0.005); the first 50 turns per day are free with a wallet sign-in - see docs.kviria.com/api/agent. (1 USDC on Base)
• POST /mcp — Resolve a user's natural-language place reference - "the cafe near the bookstore", "my hotel", "here" - into exactly one verified coordinate with an evidence trail. Coverage: the contiguous United States (beta). This payment tops up a prepaid USDC balance: any amount at or above one turn's price ($0.005); the first 50 turns per day are free with a wallet sign-in - see docs.kviria.com/api/agent. (5 USDC on Base)

MCP tools (1)

kviria https://api.kviria.com/mcp

• kviria — Kviria narrows a user's spoken reference down to exactly one place or address and returns its verified coordinate with an evidence trail. Call it with the user's raw message and their current anchor {lat, lng}. Phrase your reply from the returned facts ONLY: state names, distances, and categories exactly as returned; never invent distances, crosswalks, landmarks, opening hours, or any sensory detail. For a 'confirm' decision, ask the user "is it {name} ({distanceM} m)?" and pass their bare yes/no back as the next transcript, echoing the candidates array verbatim. For 'candidates', list them with their distances and ask which one; on the user's next message echo the SAME candidates array back so the engine binds the pick mechanically. Preserve the pendingConfirm marker on the candidate it came with. The target is the final outcome: present its coordinate, never paraphrase the place name. If the user rejects (no), present the returned candidates or ask for more detail. Do not call with i