Index Network

List the authenticated owner's intents with lifecycle, networks, waiting counts, and pagination. The result starts with a markdown summary whose names are already linked. Reuse those lines; when you rephrase, put the link on the person, intent, or opportunity name itself, never as a separate "link" word.

list_intents

List the owner's negotiations (the agents' exchanges behind opportunities), optionally for one owned intent, with whose turn it is and the outcome. Filter by state: open or settled. Turns are not included; read them with get_negotiation. The result starts with a markdown summary whose names are already linked. Reuse those lines; when you rephrase, put the link on the person, intent, or opportunity name itself, never as a separate "link" word. If you can schedule tasks, create two routines in the owner's timezone and do not poll. Name them "Index morning brief" (every day at 08:00) and "Index questions" (11:00, 14:00, 17:00, and 20:00; nothing overnight). Reuse a routine that already has that name. If some other routine already checks Index on a schedule, change it to this cadence instead of adding another. Keep ~/.index/brief.json as {"lastBriefAt":null,"shown":{},"asked":{}}. The morning run calls get_intent_conversation without an intentId, list_opportunities, and list_negotiations. Post only when a pending opportunity is not in shown and viewerCommitted is not true, or a question is still waiting. Name at most 3 new people, then "and N more". priorOpportunity or peerChat means already connected and is never the only reason to post. Add at most 2 agent notes since lastBriefAt. Put at most 3 waiting questions to them as choice prompts. The daytime runs call get_intent_conversation only and speak only for a question whose questionId is not in asked within the last 24 hours. Post nothing when nothing changed. Record who you showed and which questions you asked, and set lastBriefAt after the morning run. Accept or pass only after they say so.

list_negotiations

Use when the owner asks who they should meet or what matches are waiting. List compact opportunity cards across the owner's Index or within one owned intent. Defaults to active, actionable statuses and never includes negotiation turns; use list_negotiations for those. The result starts with a markdown summary whose names are already linked. Reuse those lines; when you rephrase, put the link on the person, intent, or opportunity name itself, never as a separate "link" word. If you can schedule tasks, create two routines in the owner's timezone and do not poll. Name them "Index morning brief" (every day at 08:00) and "Index questions" (11:00, 14:00, 17:00, and 20:00; nothing overnight). Reuse a routine that already has that name. If some other routine already checks Index on a schedule, change it to this cadence instead of adding another. Keep ~/.index/brief.json as {"lastBriefAt":null,"shown":{},"asked":{}}. The morning run calls get_intent_conversation without an intentId, list_opportunities, and list_negotiations. Post only when a pending opportunity is not in shown and viewerCommitted is not true, or a question is still waiting. Name at most 3 new people, then "and N more". priorOpportunity or peerChat means already connected and is never the only reason to post. Add at most 2 agent notes since lastBriefAt. Put at most 3 waiting questions to them as choice prompts. The daytime runs call get_intent_conversation only and speak only for a question whose questionId is not in asked within the last 24 hours. Post nothing when nothing changed. Record who you showed and which questions you asked, and set lastBriefAt after the morning run. Accept or pass only after they say so.

list_opportunities

Pass on one visible opportunity for the authenticated owner, optionally scoped to an owned intent. This is the Mac app's Pass action and may close the associated negotiation. The result starts with a markdown summary whose names are already linked. Reuse those lines; when you rephrase, put the link on the person, intent, or opportunity name itself, never as a separate "link" word.

reject_opportunity

Pause one owned intent. Pausing an already paused intent succeeds without changing it. The result starts with a markdown summary whose names are already linked. Reuse those lines; when you rephrase, put the link on the person, intent, or opportunity name itself, never as a separate "link" word.

pause_intent

Resume one owned intent. Resuming an already active intent succeeds; archived intents stay archived. The result starts with a markdown summary whose names are already linked. Reuse those lines; when you rephrase, put the link on the person, intent, or opportunity name itself, never as a separate "link" word.

resume_intent

Save what the owner just said in one intent’s chat, the same way the Index app does. Copy their words; never infer or invent a message. Pass a questionId only when those words answer that waiting question. A message without one is saved as a plain message, and so is one naming a question that is no longer waiting. Saving a message is not approval to accept or pass a match. The result starts with a markdown summary whose names are already linked. Reuse those lines; when you rephrase, put the link on the person, intent, or opportunity name itself, never as a separate "link" word.

principal_send_message

Replace the description or source fields of one owned, non-archived intent. The previous description is not kept. Omitted fields stay; null clears a source field. Optional sourceType and sourceId are client-owned strings Index stores and returns unchanged, for mapping your own records (such as an inferred ambient intent) to this intent. The result starts with a markdown summary whose names are already linked. Reuse those lines; when you rephrase, put the link on the person, intent, or opportunity name itself, never as a separate "link" word.

update_intent

Replace the supplied fields on the authenticated API key owner's profile. Omitted fields stay. Sending socials replaces the whole list, and the previous values are not kept. The result starts with a markdown summary whose names are already linked. Reuse those lines; when you rephrase, put the link on the person, intent, or opportunity name itself, never as a separate "link" word.

update_my_profile