Feature support by surface
Domino shares product objects and safety rules across surfaces, but the mechanics and availability are not identical. Use this table to answer “Can I do this here?” before giving instructions.
Support levels
- Full: the primary supported flow for this particular outcome exists on that surface, subject to permissions and eligibility.
- Capability: a structured Domino operation, such as searching inventory or creating a private plan, is implemented for this surface. Calling it requires a supported tool or API operation, the connection's required permissions, and account eligibility. Feature rollout restrictions still apply.
- Explain or hand off: the surface can explain or return a web management link, but does not perform the setting itself.
- No: do not promise the behavior.
Conversational means the assistant carries out the flow or invokes the capability. Prepared capability means the operation prepares an action for the later approval and commit described in the confirmation matrix. These labels describe access and interaction mechanics; they are not rankings of assistant completeness.
Outcome matrix
The search row covers Domino's existing inventory. Research outside that inventory has separate external Discovery boundaries.
| Outcome | Web | SMS | MCP | Capability API | Assistant API |
|---|---|---|---|---|---|
| Read public Domino documentation | Full | Explain | Explain | Explain | Explain |
| Register, sign in, recover password, edit profile, delete account | Full | Explain or hand off | No | No | Explain or hand off |
| Create or revoke static Agent Access tokens; edit or revoke OAuth connections | Full | No | No | No | No |
| Browse and filter recommendation cards | Full | Conversational equivalent | Capability | Capability | Conversational capability |
| Search known places, events, ideas, lists, or plans | Full | Full conversationally | Capability | Capability | Conversational capability |
| Create and manage Ideas Lists | Full | Full conversationally | Capability | Capability | Conversational capability |
| Like or unlike ideas | Full | Conversational capability | Capability | Capability | Conversational capability |
| Create or archive user-created ideas | Full | Conversational capability | Capability | Capability | Conversational capability |
| Create or archive private places | Full | Text fields; media management hands off to web | Capability for supported fields | Capability for supported fields | Conversational capability with web handoff for media |
| Add or edit a Friend in Mind | Full | Full conversationally | Capability | Capability | Conversational capability |
| Create a mutual connection invitation | Full link/QR flow | Prepared external action when supported | Prepared capability | Prepared capability | Prepared capability |
| Share an Ideas List | Full link flow | Link or prepared direct share, depending on recipient | Prepared capability | Prepared capability | Prepared capability |
| Open and copy a shared Ideas List | Full recipient flow | Link opens web | No direct copy flow unless capability is exposed | No direct copy flow unless capability is exposed | Explain or hand off |
| Connect, pause, reconnect, or remove a calendar | Full | Web handoff | Web handoff | Web handoff | Web handoff |
| Check calendar connection status | Full | Full conversationally | Capability | Capability | Conversational capability |
| Find free/busy availability | Full planning use | Full conversationally | Capability | Capability | Conversational capability |
| Capture text or a URL | Full | Full conversationally | Capability | Capability | Conversational capability |
| Capture protected media | Full through Add screenshot | Supported MMS path | Current opaque Domino media references only; otherwise web/SMS handoff | Current opaque Domino media references only; no general bearer-token upload | Current supported references or web/SMS handoff |
| Review a capture or roundup | Full review link | Status and review link | Capability/status | Capability/status | Conversational status and link |
| Create or edit a private plan draft | Full | Full conversationally | Capability | Capability | Conversational capability |
| Publish or send invitations | Explicit web review/send | Prepare then exact uppercase SEND |
Prepare, later approval, actions.commit |
Prepare, later approval, actions.commit |
Prepare, later approval, explicit Assistant API commit endpoint |
| Inspect plans and invitation delivery | Full | Full conversationally | Capability | Capability | Conversational capability |
| Edit or cancel an active plan | Full host controls | Prepared consequential action | Prepared capability | Prepared capability | Prepared capability |
| Manage plan-progress or logistics items | Full | Supported Domino progress items | Capability | Capability | Conversational capability |
| Make a reservation, purchase tickets, or submit payment | No | No | No | No | No |
| List and answer invitations | Full | Full conversationally | Capability | Capability | Conversational capability |
| Add one accepted plan to an external calendar | Full | Link/web handoff | Link/resource when returned | Link/resource when returned | Link/resource when returned |
External Discovery
External Discovery researches options beyond Domino's existing inventory. It is enabled separately by account and surface. The paths below describe implemented behavior; they do not establish that Discovery is enabled for a particular connection. Disabling external Discovery does not disable ordinary inventory search for an otherwise authorized user.
Production access as of September 8, 2026: Web Discovery is open to signed-in users. Authenticated Capability API callers can use ideas.discover, ideas.discover.refine, ideas.discover.save, and owned Discovery status reads without joining the owner-only beta allowlist. Required token abilities, record ownership, usage limits, and the global pause switch still apply. Other beta API operations, including the Assistant API, retain their existing access restrictions. SMS and MCP Discovery remain disabled. This access rollout does not establish complete workflow acceptance on every client.
| Surface | Research and refinement path | Current action boundary |
|---|---|---|
| Web | Domino researches and supports conversational refinement of retained results. | Actionable results can support saving to an Ideas List and creating a private plan; incomplete results can remain read-only. |
| SMS | Domino researches through the SMS flow; completion returns a short summary and a retained-results web link. | Only choices in the recorded completion message are ordinal-selectable; additional results use the returned Web link. Full carrier and conversational journey acceptance remains separate. |
| Capability API | The caller invokes structured Discovery or refinement operations and polls accepted work. | Runtimes returning domino.discovery-selection.v1 expose exact Save/private Plan inputs and owner list/Plan readback. Use the returned Web handoff on older runtimes. |
| Assistant API | Domino's hosted assistant can select research, refinement, and actions on retained results. | Follow returned actionability and outcomes. Shared operations do not establish that every conversational research-to-plan sequence is complete. |
| MCP | Domino supplies context and inventory; the host assistant researches and submits results for recording. Refinement uses that prepare/research/record flow again with the prior research context. | Recording does not independently verify host claims. Where advertised by authenticated tools/list, domino_save_discovery_results saves exact returned selections; private Plan creation and readback use the shared contract. Live host acceptance remains separate. |
Saving and planning from research must preserve the selected result, its evidence, and the user's constraints. A research result handle is not interchangeable with a save reference or an ordinary plan candidate ID. Looking up the same venue again does not recover the original research constraints. Use only references accepted by the current operation; if the required action or reference is unavailable, explain the limitation and use a returned web handoff when available.
Recording research does not confirm an Ideas List save, a plan, an invitation, or a reservation. Inspect the returned outcome before claiming that any action occurred. Research and calendar free/busy results do not establish venue availability or complete a booking; the current boundaries still apply.
Confirmation matrix
| Surface | Private write | External effect |
|---|---|---|
| Web | User chooses the visible save control. | User reviews and chooses the current publish/send control. |
| SMS | Domino can make authorized private changes conversationally. | Domino prepares; a later entire trimmed message equal to uppercase SEND commits the current eligible action. |
| MCP | Caller supplies a stable idempotency key. | Caller prepares, presents disclosures, stops for later explicit approval, then calls actions.commit from the same principal. |
| Capability API | Caller supplies a stable Idempotency-Key header. |
Caller prepares, presents disclosures, stops for later explicit approval, then calls actions.commit from the same token/principal. |
| Assistant API | Each turn uses a unique request key and stable conversation identity. | Caller prepares, presents disclosures, stops for later explicit approval, then uses the returned Assistant API commit endpoint. SEND is ordinary text here. |
Outcome parity does not mean UI parity
For example, “create an Ideas List” can be a web form, an SMS conversation, an MCP tool call, a Capability API request, or an Assistant API turn. The resulting Domino object follows shared rules, but button labels, confirmation, error recovery, and authorization remain surface-specific.
Feature support and assistant completeness
This page describes individual supported outcomes and their access conditions. Full applies to the named outcome, not to the whole assistant or every journey involving that outcome. An available capability does not prove that conversational interpretation, follow-up continuity, asynchronous result handling, or the complete search → refine → save → plan journey is equally complete across surfaces. It also does not establish live acceptance of those journeys. Detailed implementation progress and dated acceptance evidence belong in the development documentation; this page records the user-facing support boundaries.
How to answer availability questions
If a cell says Capability, check the operation for the current connection:
- MCP: use the authenticated connection's
tools/list, as described in the MCP guide. The public MCP tool catalog provides schemas; it is not the connection's authorized tool list. Even a listed tool can be restricted by feature rollout or account eligibility at execution time. - Capability API: use the generated OpenAPI document or capability reference for operation names, schemas, and required abilities. Compare those requirements with the connection's granted permissions and inspect the returned outcome for the requested operation. The public schema is not a personalized list of authorized or enabled operations. Follow the API guide for authentication and status handling.
Use the connection verification guide for a read-access check. A successful connection or read verifies that access only; it does not prove access to every operation or confirm a write. Honor the requested operation's returned restrictions and typed outcome.
If a cell says Explain or hand off, give the shortest web route and state that the current surface cannot complete the setting.
If a behavior is absent from this table or the current generated catalog, use Limits, unsupported behavior, and current boundaries and do not infer support from an internal route or data model.
LLM answering guidance
- Start with the user's current surface and desired outcome.
- Verify authenticated capability availability before offering to act.
- Never import the confirmation syntax from one surface into another.
- When the surface cannot perform a task, explain the handoff without pretending the action occurred.