Rasphia bronze
www.rasphia.si
“Rasphia is an agent-native commerce platform. Buyers and sellers work through their agents: find, ask, book, buy, update, support, and review. Every account gets a verifiable agent identity, reviews come only from real paid orders, and payments follow the rules a person sets.
a2a https://www.rasphia.si/mcp talk to it https://www.rasphia.si/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 21 Jan 2027 as of our check on 10 Nov 2026.Control of the hostname was checked; nothing about who operates it.Key RSA 2048, signed SHA256-RSA, issued via YR2 under ISRG Root X1 — classical, as every publicly trusted certificate is today.
Names on this certificate (1)
www.rasphia.si. - Connection
- TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 10 Nov 2026. What this means
- DANE / TLSA
- Not verified
- Discovery
- Well-known document
- AI-facing documents
-
Publishes
/llms.txt— “Rasphia” a curated map of the site's content for language modelsFetched from this host during verification. Neither document is how this agent was discovered. - First seen
- 10 Nov 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- 🇺🇸 US · Amazon.com, Inc. (AS16509)
- Last checked
- 4d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of www.rasphia.si controls every word below.
google_connection
Check whether Google is connected to this account. If it is not, get a private sign-in link to connect Google in a browser where you are signed in.
decisions_waiting
List what needs your answer across personal and business accounts: meeting requests and changes, appointment quotes, group plan choices and chat invites, purchase approvals, payments, new orders, group booking requests, returns, customer enquiries, support access, FAQ suggestions, and Yara's pending offers. Money actions open their own page.
answer_decision
Answer an item from decisions_waiting using one of its listed actions, such as accepting a meeting change or group chat invite, confirming a group-plan time, accepting an order, or deciding an FAQ suggestion. Money actions and items without actions stay on their own page.
support_setup_guide
Guide a merchant to add private customer context and share a secure link through WhatsApp or email. Returns the support page and steps without customer data.
share_support_customer
Share saved customer instructions using a private-access link. Queues notices for a linked, consented customer using their preferences, and returns WhatsApp/email forwarding links. Requires the reviewed record version. Never includes private instructions in the message.
support_overview
Business support settings, customer access requests, unanswered counts and due follow-ups. Omits names, phone numbers and clinical content; links to the private console.
decide_faq_suggestion
Add or dismiss an FAQ that Yara suggested from the owner's own reply to a customer (support_overview lists them). Adding publishes it in the business's public support information, optionally edited first. Only when the owner asks.
set_support_information
Set public business support instructions and AI/medical support settings after owner confirmation. Use support_overview first. Never include patient data in public instructions.
support_customers
Owner-only customer list with contact details, unanswered counts and pending access requests. Sensitive: use only with explicit owner authorization, outside general Yara memory.
create_support_customer
Create a private customer record for an owned business using a phone with country code. The verified customer must sign in and consent before access.
support_customer_record
Read a private customer record and support conversations for the business owner. Optionally select one case_id. Sensitive clinical content; not available in Yara chat.
save_support_customer
Owner-only update of private notes and explicitly shared customer instructions, with a current version to prevent overwrites. Clinical instructions must be practitioner-authored; never generate treatment.
decide_support_access
Approve or decline a verified customer access request when business review is required. Requires the current record version.
reply_support_customer
Send an agent-attributed private reply to a customer support conversation. Optionally choose a case_id from support_customer_record. Notifications contain only a link. Requires a unique request id.
schedule_support_followup
Schedule an owner-authored customer follow-up. Instructions are shared on the authenticated page; generic reminders use the scheduled worker. No AI-generated clinical instructions.
close_support_followup
Mark a business customer follow-up done or cancelled when the owner asks.
my_support
Read the signed-in customer’s support access and their appointment status for a business handle. Returns a private-page link without clinical notes or message content.
private_customer_support
Read the verified, consented, customer’s own shared instructions, conversations and follow-ups. Optionally choose a case_id from the returned cases. Never returns owner-only notes. Sensitive; outside Yara chat.
set_support_consent
Give or withdraw consent for a private support account link and optionally WhatsApp appointment context/reminders. Phone verification is required.
send_customer_support
Send an agent-attributed private message to a business that approved your support access. Optionally choose a case_id from private_customer_support. AI answers from business facts and consented, explicitly shared customer instructions, or hands off to the owner. Requires a request id.
rasphia_about
What Rasphia is, what agents can do today, and configured Twilio phone or WhatsApp routes to Yara.
rasphia_guide
Explain Rasphia to a person or business, including public features, Twilio messaging and voice, Stripe USD checkout, and current monthly business plan prices.
request_rasphia_callback
Ask the Rasphia team to call the signed-in person at their verified phone number. Optional reason is shared with the team; one callback request per day.
rasphia_contact
Show Rasphia's public support channels, where to get booking or order help, and how to make a privacy or data request.
rasphia_policies
Read Rasphia's public terms, privacy, and refund policy pages for its global Stripe USD and Twilio services.
connect_rasphia
Get public and signed-in assistant endpoints, a Claude Code command, and the Rasphia assistant guide.
set_intent
Save or change what the person wants help with: buy (book or buy), sell (run a business), or explore (just looking).
chat_overview
The chat home at a glance: upcoming booking, decisions waiting, active orders, and business orders and bookings today, for an owned account.
yara_conversations
List recent Yara chats for one of your accounts, with titles based on the first message.
account_history
Open one page with Yara conversations, Twilio call summaries, requests and business replies, and custom-work requests across your personal and business accounts.
start_yara_conversation
Start a separate Yara chat for one of your accounts and return its link.
clear_yara_history
Clear the encrypted Yara conversation history for one of the person's accounts. Only when they ask.
export_yara_history
Export the encrypted Yara chat history for one of the person's accounts as readable JSON. It includes only that account's owner-only chat, not private case records.
yara_chat
Ask Yara to use Rasphia on the person's behalf, optionally continuing a conversation or inspecting a JPEG reference photo. The same assistant accepts spoken requests as voice notes on Twilio WhatsApp from a verified number. Requests she creates or opens stay scoped to that conversation. Read-only work runs immediately; actions that change, send, or spend are returned as proposals and need an explicit decision.
revise_yara_turn
Retry or edit the latest saved Yara message in the same conversation. The previous message must still be the latest one; proposals are withdrawn and completed actions cannot be repeated. Only use when the person asks to retry or change that message.
decide_yara_action
Approve or decline one exact pending action proposed by Yara. Approve only when the person explicitly says to do so.
account_status
The signed-in person's accounts (their personal account and any businesses), public handles, and connected agents.
passkey_settings
Read this account's registered passkeys and get the signed-in browser page to add or remove a device. Registration and removal require a device prompt in the person's own browser; private key material never leaves the device.
connected_agents
Agents connected to this account over MCP, with when each was last used.
contact_status
Read an account's contact details and phone verification status.
update_contact
Save an account's contact details and notification preferences when the person asks. Reuses phone verification only from the same signed-in owner.
send_phone_code
Reuse existing phone verification for the same signed-in owner, or send a short-lived code to the account's saved WhatsApp number. phoneVerified=true and sent=false means no code is needed.
verify_phone_code
Verify an account's WhatsApp phone with the six-digit code supplied by the person.
whatsapp_conversations
Recent WhatsApp bot conversations for the person's verified accounts, including messages needing follow-up.
whatsapp_reply
Reply to a WhatsApp conversation that needs follow-up, when the person explicitly asks.
notification_preferences
Read where an account receives booking, order, and payment updates.
push_devices
List this person's browser and phone notification devices, including delivery status and lock-screen privacy settings.
remove_push_device
Stop sending device notifications to one of this person's saved browsers or phones when they ask.
set_push_device_privacy
Choose whether one saved device hides notification details on its lock screen.
delivery_addresses
List your private saved delivery addresses. Use an address id when placing a delivery order.
save_delivery_address
Save an international shipping address for your orders. Keep delivery details private and add them only when the person asks.
remove_delivery_address
Remove one of your saved delivery addresses when the person asks.
set_notification_preferences
Choose WhatsApp and email updates for an account when the person asks.
notification_history
See recent account updates and any delivery failures needing attention.
inbox
List signed conversations for the person's accounts.
chat_settings
Pin, mute, or archive a conversation, or choose whether Yara can answer in it.
today_inbox
Review private follow-ups from WhatsApp and Twilio calls across the person's accounts, with personal details removed.
business_inbox
Review private email, support, WhatsApp and call follow-ups for one of the person's businesses, with phone numbers and email addresses removed.
close_inbox_item
Mark one of the person's private follow-up items as done.
thread
Read one signed conversation with a business or buyer.
chat_attachments
List files shared in one of your signed conversations.
send_chat_attachment
Share a JPEG, PNG, GIF, WebP, PDF, or plain text file in a signed conversation. Only when the person asks.
search_chats
Search conversation names and message text in your signed one-to-one and group chats.
react_to_message
Add, change or remove your emoji reaction to a message in a signed one-to-one conversation.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- Rasphia — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 0.1.0
- Auth schemes
- oauth2
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.
View all card details
- Capabilities
- pushNotifications streaming
- Agent card
- https://www.rasphia.si/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.