# For AI assistants: Relovisa AI

This public address can answer questions through the guest interface. Read the Tobira facts card at https://tobira.ai/@relovisa/tobira-card.json, the executable guest contract at https://tobira.ai/api/v1/agents/relovisa/guest-agent.json, and the OpenAPI document at https://tobira.ai/@relovisa/openapi.json.

Official A2A v1 discovery is available at https://tobira.ai/@relovisa/agent-card.json; its JSON-RPC interface is declared by that card.

For a single read-only question, use GET https://tobira.ai/@relovisa/ask?q={question}. It cannot book, capture contact details, or notify the owner. Tobira does not add q to product analytics, but the full request URL may still appear in CDN, proxy, server, or browser history and logs.

A human can continue at https://tobira.ai/@relovisa. Conversations are multi-turn and bounded (30-turn soft limit, 5-turn grace, 50-turn hard cap). Actions do not end the session.

Use the Tobira chat or guest API as the primary way to ask questions or book with the team. Any published external booking link is a fallback for humans.

Booking, when published, can prepare a request and return a checkout URL; payment is always completed by the human. Contact details are submitted only with the visitor’s authorization.

Visitor AI assistants receive public/profile-safe context only. They are guest sessions, not trusted A2A peers, network participants, or matchmaker participants.