{"openapi":"3.1.0","info":{"title":"Inboxzero API","version":"0.1.0","description":"A fully local email-triage methodology guide: named methodologies (Inbox Zero, the 4 D's, batching, priority triage, folder systems), a deterministic decision-tree triage tool, a situation-to-methodology matcher, common mistakes, response templates, and a methodology-combining guide. Never receives or stores actual email content.\n\nEvery operation is read-only or compute-only. The same tools are available over MCP (streamable HTTP) at https://inboxzero.connectorbay.com/mcp.","contact":{"name":"Unify Dynamics LLC","email":"hr@unifydynamics.com","url":"https://connectorbay.com/inboxzero/docs"},"termsOfService":"https://connectorbay.com/inboxzero/terms"},"servers":[{"url":"https://inboxzero.connectorbay.com"}],"externalDocs":{"url":"https://connectorbay.com/inboxzero/docs"},"security":[{},{"bearer":[]}],"components":{"securitySchemes":{"bearer":{"type":"http","scheme":"bearer","description":"Optional. A Pro API key raises rate limits; no credentials are required."}},"schemas":{"Error":{"type":"object","properties":{"ok":{"const":false},"error":{"type":"object"}}}}},"paths":{"/v1/tools/methodology_by_name":{"post":{"operationId":"methodology_by_name","summary":"Explains one named email-triage methodology: how it works, who it's best for, and its common pitfall.","description":"Explains one named email-triage methodology: how it works, who it's best for, and its common pitfall.\n    Use for \"what is Inbox Zero\", \"explain the 4 D's for email\".","tags":["tools"],"requestBody":{"required":true,"content":{"application/json":{"schema":{"properties":{"name":{"description":"inbox_zero | four_ds | batching | priority_inbox_triage | folder_or_label_systems","title":"Name","type":"string"}},"required":["name"],"title":"methodology_by_nameArguments","type":"object"}}}},"responses":{"200":{"description":"Tool result. `ok: true` on success; `ok: false` with a structured `error` (provider_unavailable, upstream_error, bad_input) when the tool could not answer.","content":{"application/json":{"schema":{"type":"object","additionalProperties":true}}}},"422":{"description":"Arguments failed validation","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"429":{"description":"Rate limit exceeded (see Retry-After)","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}},"x-read-only":true}},"/v1/tools/methodology_list":{"post":{"operationId":"methodology_list","summary":"All five methodologies this reference covers. Use for \"what email triage methods do you know about\".","description":"All five methodologies this reference covers. Use for \"what email triage methods do you know about\".","tags":["tools"],"requestBody":{"required":true,"content":{"application/json":{"schema":{"properties":{},"title":"methodology_listArguments","type":"object"}}}},"responses":{"200":{"description":"Tool result. `ok: true` on success; `ok: false` with a structured `error` (provider_unavailable, upstream_error, bad_input) when the tool could not answer.","content":{"application/json":{"schema":{"type":"object","additionalProperties":true}}}},"422":{"description":"Arguments failed validation","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"429":{"description":"Rate limit exceeded (see Retry-After)","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}},"x-read-only":true}},"/v1/tools/compare_methodologies":{"post":{"operationId":"compare_methodologies","summary":"A side-by-side comparison of core idea, best-for, and common pitfall for several methodologies. Use for","description":"A side-by-side comparison of core idea, best-for, and common pitfall for several methodologies. Use for\n    \"compare Inbox Zero and the 4 D's\".","tags":["tools"],"requestBody":{"required":true,"content":{"application/json":{"schema":{"properties":{"names":{"description":"Two or more methodology names to compare.","items":{"type":"string"},"minItems":2,"title":"Names","type":"array"}},"required":["names"],"title":"compare_methodologiesArguments","type":"object"}}}},"responses":{"200":{"description":"Tool result. `ok: true` on success; `ok: false` with a structured `error` (provider_unavailable, upstream_error, bad_input) when the tool could not answer.","content":{"application/json":{"schema":{"type":"object","additionalProperties":true}}}},"422":{"description":"Arguments failed validation","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"429":{"description":"Rate limit exceeded (see Retry-After)","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}},"x-read-only":true}},"/v1/tools/methodology_for_situation":{"post":{"operationId":"methodology_for_situation","summary":"Suggests the best-fitting methodology for a described email problem. Use for \"what should I do about","description":"Suggests the best-fitting methodology for a described email problem. Use for \"what should I do about\n    checking email too often\", \"I have too many unequal-priority senders, what method fits\".","tags":["tools"],"requestBody":{"required":true,"content":{"application/json":{"schema":{"properties":{"situation":{"description":"A described problem with your email habits, e.g. 'I check email compulsively all day'.","minLength":1,"title":"Situation","type":"string"}},"required":["situation"],"title":"methodology_for_situationArguments","type":"object"}}}},"responses":{"200":{"description":"Tool result. `ok: true` on success; `ok: false` with a structured `error` (provider_unavailable, upstream_error, bad_input) when the tool could not answer.","content":{"application/json":{"schema":{"type":"object","additionalProperties":true}}}},"422":{"description":"Arguments failed validation","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"429":{"description":"Rate limit exceeded (see Retry-After)","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}},"x-read-only":true}},"/v1/tools/decision_tree_reference":{"post":{"operationId":"decision_tree_reference","summary":"The full triage decision tree's questions and outcomes, for reference. Use for \"show me the email","description":"The full triage decision tree's questions and outcomes, for reference. Use for \"show me the email\n    triage decision tree\".","tags":["tools"],"requestBody":{"required":true,"content":{"application/json":{"schema":{"properties":{},"title":"decision_tree_referenceArguments","type":"object"}}}},"responses":{"200":{"description":"Tool result. `ok: true` on success; `ok: false` with a structured `error` (provider_unavailable, upstream_error, bad_input) when the tool could not answer.","content":{"application/json":{"schema":{"type":"object","additionalProperties":true}}}},"422":{"description":"Arguments failed validation","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"429":{"description":"Rate limit exceeded (see Retry-After)","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}},"x-read-only":true}},"/v1/tools/triage_email":{"post":{"operationId":"triage_email","summary":"Walks the deterministic triage decision tree for one described email from yes/no answers, returning the","description":"Walks the deterministic triage decision tree for one described email from yes/no answers, returning the\n    recommended action and the path taken. Provide answers one level at a time as the tool asks for more via\n    bad_input errors. Use for \"help me decide what to do with this email\".","tags":["tools"],"requestBody":{"required":true,"content":{"application/json":{"schema":{"properties":{"needs_action":{"description":"Does this email require any action from you at all (not just FYI)?","title":"Needs Action","type":"boolean"},"quick_to_handle":{"anyOf":[{"type":"boolean"},{"type":"null"}],"default":null,"description":"Can you fully handle it in under about 2 minutes? Required if needs_action is true.","title":"Quick To Handle"},"someone_else_should_own_it":{"anyOf":[{"type":"boolean"},{"type":"null"}],"default":null,"description":"Is someone else better positioned to own this? Required if not quick_to_handle.","title":"Someone Else Should Own It"},"time_sensitive":{"anyOf":[{"type":"boolean"},{"type":"null"}],"default":null,"description":"Does it have a real deadline or time-sensitive consequence? Required if not delegating.","title":"Time Sensitive"}},"required":["needs_action"],"title":"triage_emailArguments","type":"object"}}}},"responses":{"200":{"description":"Tool result. `ok: true` on success; `ok: false` with a structured `error` (provider_unavailable, upstream_error, bad_input) when the tool could not answer.","content":{"application/json":{"schema":{"type":"object","additionalProperties":true}}}},"422":{"description":"Arguments failed validation","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"429":{"description":"Rate limit exceeded (see Retry-After)","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}},"x-read-only":true}},"/v1/tools/common_mistakes":{"post":{"operationId":"common_mistakes","summary":"Frequent email-triage mistakes with fixes. Use for \"what are common email triage mistakes\".","description":"Frequent email-triage mistakes with fixes. Use for \"what are common email triage mistakes\".","tags":["tools"],"requestBody":{"required":true,"content":{"application/json":{"schema":{"properties":{},"title":"common_mistakesArguments","type":"object"}}}},"responses":{"200":{"description":"Tool result. `ok: true` on success; `ok: false` with a structured `error` (provider_unavailable, upstream_error, bad_input) when the tool could not answer.","content":{"application/json":{"schema":{"type":"object","additionalProperties":true}}}},"422":{"description":"Arguments failed validation","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"429":{"description":"Rate limit exceeded (see Retry-After)","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}},"x-read-only":true}},"/v1/tools/response_template":{"post":{"operationId":"response_template","summary":"A short, adaptable reply template for a common email-triage moment. Use for \"give me a template to","description":"A short, adaptable reply template for a common email-triage moment. Use for \"give me a template to\n    delegate this email\", \"how do I tell people I don't check email instantly\".","tags":["tools"],"requestBody":{"required":true,"content":{"application/json":{"schema":{"properties":{"kind":{"description":"quick_delegate | quick_decline_or_defer | acknowledge_and_schedule | closing_a_thread | setting_response_expectations","title":"Kind","type":"string"}},"required":["kind"],"title":"response_templateArguments","type":"object"}}}},"responses":{"200":{"description":"Tool result. `ok: true` on success; `ok: false` with a structured `error` (provider_unavailable, upstream_error, bad_input) when the tool could not answer.","content":{"application/json":{"schema":{"type":"object","additionalProperties":true}}}},"422":{"description":"Arguments failed validation","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"429":{"description":"Rate limit exceeded (see Retry-After)","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}},"x-read-only":true}},"/v1/tools/combining_methodologies_guide":{"post":{"operationId":"combining_methodologies_guide","summary":"Explains how the named methodologies typically combine (batching for when, the 4 D's for how, folders","description":"Explains how the named methodologies typically combine (batching for when, the 4 D's for how, folders\n    for where, priority triage for order) rather than compete. Use for \"should I use Inbox Zero or the 4 D's\",\n    \"how do these email methods fit together\".","tags":["tools"],"requestBody":{"required":true,"content":{"application/json":{"schema":{"properties":{},"title":"combining_methodologies_guideArguments","type":"object"}}}},"responses":{"200":{"description":"Tool result. `ok: true` on success; `ok: false` with a structured `error` (provider_unavailable, upstream_error, bad_input) when the tool could not answer.","content":{"application/json":{"schema":{"type":"object","additionalProperties":true}}}},"422":{"description":"Arguments failed validation","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"429":{"description":"Rate limit exceeded (see Retry-After)","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}},"x-read-only":true}}}}