Ask Proto

Proto searches the live Protograms catalog and returns a best match, up to two alternatives, and up to two follow-up questions. Every product it returns is a real listing. When nothing fits, it says so instead of guessing.

Send a POST to /v1/proto with a signed-in Protograms session as a Bearer token. Requests without a session get 401.

POST /v1/proto
Authorization: Bearer <Protograms session token>
Content-Type: application/json

{
  "message": "turn my meeting notes into a summary"
}

• message: what you want to get done, up to 500 characters.
• history: optional earlier turns, up to 6, each with a role of user or proto.
• contextProductIds: optional product ids from the previous answer, up to 3.

{
  "message": "Here's the best match on Protograms.",
  "bestMatch": { "product": { "id": "…", "title": "…" }, "reason": "…" },
  "alternatives": [],
  "followUps": [],
  "noResults": false
}

bestMatch is null and noResults is true when nothing in the catalog fits. If search is unavailable the endpoint returns 503.

• 12 requests per minute per account, and 60 per minute per network.
• Over the limit you get 429 with a Retry-After header. Wait for it rather than retrying straight away.

To learn what people look for, Proto keeps a shortened copy of each question with emails, links, and long numbers removed. That removal is best-effort, so leave personal details out of questions. Proto doesn’t store your account, IP address, or the full conversation with that copy.

New to listing on Protograms? Read the builder guide.