Skip to content
KelkiDevelopers

API, MCP and A2A

Three doors to the same service, with the same rules: the MCP connector for AI assistants, the Kelki Agent for conversation, the API for applications that want to track their requests.

Mapping

MCP connectorKelki AgentAPI v1
trouver_servicethe need, in conversationPOST /trade-matches
lister_prestationsthe agent's buttonsGET /trades/{trade_id} (+ GET /consent-texts/{version})
verifier_lieuthe place questionGET /places
demander_rappelconsent at the summary stepPOST /requests then POST /requests/{request_id}/confirmation
The same kelki.ai confirmation page, opened from the “Confirm my request” e-mail.
——tracking specific to the API: GET /requests, /events, webhooks, /account

Which to choose

For another agent to talk to the Kelki Agent (A2A), the principle is the same as through the API: same steps, same consent, same e-mail confirmation.

Shared rules