GEgetsales
agent_examples

Add to the golden set

Add to the golden set: Remember this reply (message_sid, a message of ours that went out, the lead's message before it as the situation: 201, or 200 already_exists when the set held it and it was promoted to golden) or a pair typed by hand (situation, answer, kind), born golden. 409 message_not_sent, message_has_no_situation.

Contract:

  • MCP tool create_agent_example, registry package mcp.unibox/agent_examples, mount unibox.agent-memory.
  • Operation create, response envelope create.
  • Flags: none.
post/api/agent-examples

Request

  • Base URL
    https://beta.getsales.io/unibox/v1
  • Auth
    HTTP bearer and API key in header Team-SID

Request body

agent_sidstring

The AI SDR it is made for (ub_ag_…, block 10, 2026-10-30); left out, the team's default agent.

message_sidstring

Remember this reply: a message of ours that went out (ub_ms_…) becomes a golden row, the lead's message before it the situation; promoted when held already. 409 message_not_sent, message_has_no_situation. Takes note, not the fields below.

situationstring

A pair typed by hand: what the lead wrote, 1..4000 chars, names as placeholders ({lead}, {lead_company}, {sender}). Required with answer.

answerstring

The team's answer to it, 1..8000 chars. Required with situation.

kind'reply' | 'followup'

reply (default) or followup.

context_beforestring nullable

Our message before the lead's, max 1500 chars.

channel'linkedin' | 'email' nullable

The channel it answers on; omit for every channel.

scenario_keystring nullable

The scenario the situation belongs to (interested, objection, ...).

notestring nullable

When the row applies, in a person's words, max 512 chars.

Response

create success envelope.

successtrue required
operation'create' required
already_existsboolean required

Changes

No recorded changes to this operation across all 1 revision of this API.