Agent-to-Agent
Talk to the product agent, not a brochure.
MAIIA runs its Website Sales Agent on this site. Humans use the chat bubble. External AI agents use the same agent over A2A: open a short-lived session (no API key email), then send JSON-RPC messages. Abuse is controlled with rate limits and property-scoped JWTs — not a human key desk.
1. Immediate proof — humans
Open the Website Sales Agent on this page. Use a hotel-buyer scenario with real uncertainty, then continue for several turns. Watch whether the agent clarifies property type and commercial focus before recommending, keeps earlier details, and offers a relevant next step (demo, readiness report, or sales follow-up).
2. Programmatic A2A — open session
The Agent Card is public. Bare message/send without a token returns 401.
Agents mint a JWT automatically:
# 1. Open discovery session (no API key)
POST https://app.commerce.maiiasuite.com/api/a2a/1/session
Content-Type: application/json
{"clientAgent": "your-agent-name", "purpose": "inquiry"}
# Response: { "token", "expires_in", "token_type": "Bearer", "propertyId": 1 }
# 2. Converse
POST https://app.commerce.maiiasuite.com/api/a2a/1
Authorization: Bearer <token>
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": "1",
"method": "message/send",
"params": {
"message": {
"role": "user",
"parts": [
{
"type": "text",
"text": "How does MAIIA's Website Sales Agent differ from a generic hotel chatbot?"
}
]
}
}
} - Session and RPC are rate-limited per IP (and property).
- JWT is scoped to property 1 and expires in ~15 minutes — mint again as needed.
- Card: /.well-known/agent-card.json (legacy: /.well-known/agent.json)
- Endpoint:
https://app.commerce.maiiasuite.com/api/a2a/1— A2A v1.0 JSON-RPC (0.2.1 also accepted). Blocking only.
For multi-turn tests, pass the returned contextId on the next
message/send.
3. What to test
Full brief: /llms-full.txt §3. Comparison: Website Sales Agent vs chatbot.
- Reception — opens as MAIIA's product advisor, not a hotel concierge.
- Qualification — clarifies property type and commercial focus.
- Discovery — one useful follow-up before dumping the catalogue.
- Presentation — matches WSA, Guest App, or Control Center to the need.
- Close — a real next step: demo, readiness report, or sales handoff.
4. Boundaries
- This endpoint is MAIIA selling MAIIA. It must not impersonate a hotel guest concierge.
- Do not infer contract prices from chat. Commercial terms come from sales (sales@maiiahospitality.ai).
- Hotel-facing A2A (guest discovery → hotel agents) is on AI Search Discovery.