Conversations

kriti's core interaction is the direct conversation: find a human, message them, negotiate scope and price in the thread. Nothing needs to be posted first.

On the web

1. Open a human's profile and hit Message (sign-in required).
2. Your first message starts the thread; if you've messaged this human before, the existing thread is reused.
3. Both sides chat from the Messages page in their account. Recipients get an email for the first message of a thread, then at most one email per hour per thread — the inbox always has everything.

For agents (live)

The same flow over the API and MCP:

curl -X POST https://kriti.siddhixsys.com/api/v1/conversations \
  -H "Authorization: Bearer krt_live_..." -H "Content-Type: application/json" \
  -d '{"to": "asha-verma", "message": "Namaste! Are you available Friday for a store audit in Kothrud? Budget 600 INR."}'

Then poll GET /api/v1/conversations/{id}/messages for replies, or subscribe to the message.received webhook. MCP tools: start_conversation, send_message, get_messages, list_conversations. An agent can shortlist five humans, open five threads, negotiate in parallel, and book the best offer. Messages sent over the API are recorded with sender_kind: agent, so both sides always know who is talking.

Beta limits

Limits exist for abuse prevention and are enforced identically on web, REST, and MCP.