What an agent should log when it calls Sume: ids yes, signed URLs no
Safe log fields for agents using the Sume API, CLI and MCP: request ids, job ids, status, sanitized media metadata. Never keys, signed URLs or transcripts.
An agent that calls Sume should log request ids, job ids when necessary, high-level status and sanitized media metadata, and should never log API keys, signed URLs, raw private media URLs or large amounts of user content and transcripts (Safe automation).
Log or drop
| Field | Log it? |
|---|---|
| request_id | Yes |
| job id | Yes, when needed to follow up |
| status such as queued, processing, completed | Yes |
| media metadata (sanitized: type, duration, size) | Yes; the page says "sanitized media metadata" |
| API key or OAuth token | Never |
| signed or private media URL | Never |
| full transcript or user prompt text | No; the page lists too much user content or too many transcripts as unsafe |
A redacting helper
A small filter in Python that keeps the safe keys from a response and drops the rest.
SAFE_KEYS = {"id", "request_id", "status", "job_status", "resource_status", "video_url"}
def loggable(resp: dict) -> dict:
return {k: v for k, v in resp.items() if k in SAFE_KEYS}
print(loggable({"id": "job_123", "status": "completed", "authorization": "Bearer secret"}))Boundaries that matter more than logs
The API key or app session selects the workspace; tools must not accept a workspace id from the user. Spending actions should be explicit: on hosted MCP use OAuth mcp:read for exploration, and grant mcp:write or use an API key before paid tools such as generate_image or avatars_create. Paid and write calls must send idempotency_key.
Sources
Related posts
More in Agents
- Agent Completion: a 15 s MiniMax H3 clip plus voiceover, cap 1.50
A 15-second MiniMax H3 clip at 768p ($1.125) plus a 750-character voiceover ($0.035625) comes to $1.160625, so a cap of 1.5 is enough. Table and body.
- Agent Completion attachments: 16 full-size images fit the 500 MB cap
An Agent Completion takes up to 30 images, each up to 30 MB, in a set up to 500 MB. At full size only 16 fit; for 30 images the average must be under 16.7 MB.
- Agent Completions rejects assistant turns: how to carry chat history
Sume Agent Completions return 400 on any assistant message in messages[] and start a fresh thread each time. Here is what that means for multi-turn history.
- Agent run log allowlist: which Sume fields are safe to keep
Log request ids, job ids, status and sanitized media metadata from Sume agent runs; never log API keys, signed URLs, raw private media URLs or full transcripts.
Written by Sume