Connection check
verified live · 20h ago
pimea
The hidden intelligence for AI marketing agents. Real campaign data, not LLM guesses.
Tools
3
GitHub stars
—
Installs / wk
—
Licence
—
Transport
streamable-http
Last checked
20h ago
Tools & capabilities
3 toolsRead from the running server on 20h ago.
pimea_chat
api_keymessage*session_id*
Send a message in an active Pimea session. Use this to answer Pimea's clarifying questions about the user's marketing situation. You can answer on behalf of the user using con… Send a message in an active Pimea session. Use this to answer Pimea's clarifying questions about the user's marketing situation. You can answer on behalf of the user using context from the conversation when possible. Only ask the user directly if you genuinely lack the information. When the response status is "complete", call pimea_get_answer to retrieve the final grounded deliverable. Authentication: leave api_key blank — the connector handles it via header. Only set it as a fallback if the connector cannot send custom headers. Args: session_id: The session UUID from pimea_start_session message: Response to Pimea's question api_key: Optional fallback only. Normally leave blank.
pimea_get_answer
api_keysession_id*
Get the final result from a completed Pimea session. ALWAYS use this to retrieve the grounded deliverable instead of summarizing the chat history yourself — the deliverable is the… Get the final result from a completed Pimea session. ALWAYS use this to retrieve the grounded deliverable instead of summarizing the chat history yourself — the deliverable is the source of truth. Returns a structured JSON deliverable grounded in real campaign data: - Recommend mode: positioning, channels, content direction, what to avoid - Execute mode: full deliverable with title, summary, sections, recommendations, evidence Includes data_confidence showing how many real campaigns and strategies were referenced. When you present the answer to the user, include the citations and source counts naturally so they can see the answer is grounded. Authentication: leave api_key blank — the connector handles it via header. Only set it as a fallback if the connector cannot send custom headers. Args: session_id: The session UUID api_key: Optional fallback only. Normally leave blank.
pimea_start_session
api_keymessage