get_agent_inbox_sources
shallowbot.mailbox/mailbox · Verify this server
Deprecated: use get_inbound_item. Still served unchanged during the alias window. Primary OCR read after list_agent_inbox: GET /v1/agent-inbox/:id/sources. Requires assigned-inbox and indexed-source reads enabled for the account, plus agent.inbox.read + agent.read. After indexed-source rollout, read selected item_id pages: exterior, requested contents and original sample_letter. Group by item, then request_id/bundle_id; cite page_id, preserve source_sha256 and review flags. Derive sender/address only from returned evidence. Both read scopes required; no acknowledgment version or extraction is created. Field meanings and sort order are in outputSchema. Use narrow queries/date windows and fetch selected items, not every mailbox on every poll. Pages: limit 1–50 (default 25), offset 0–10000. Item lists use next_offset; sources/scans use has_more and offset + returned length. Stop before exceeding 10000; narrow item searches, or report incomplete source/scan history. Pagination is a current view, not a snapshot or durable queue. Bound concurrency and retries; honor Retry-After when present, back off with jitter on 429/transient failures, and stop on access errors or disabled rollout. Do not share private results across agents/environments. No ETag, change cursor or unbounded export is promised. No receipt, provider call, signed image URL, email or charge. Managed-PMB custody and forwarded email remain separate and excluded. Required scopes: agent.inbox.read, agent.read. Agent-scoped bearer key required; member/facility keys cannot impersonate an agent. Rollout switches, current member approval, assignment, credential environment and SQL authorization are shared with REST. Never substitute another key or mail API after denial.
1 trials · measured 14 days ago
get_agent_inbox_sources scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against bot.mailbox/mailbox, measured 23 Sept 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- gated
- Category
- Developer infrastructure
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-09-23 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/ff3448dc-0b94-472e-a076-d3da4f713f36)