Embed Navigator in your product

​

Keep each responsibility clear

​

Integration path

1. Register your application. Follow Developer account setup. Keep application keys server-side. An application key can authenticate Search; it cannot Act for every customer.
2. Search from the user’s goal. Call Search, handle needs_input and no_match, and display ranked matches with their reasons and uncertainties. Preserve the selected agent and capability IDs and revision. Use Search results describes the handoff fields.
3. Let the person choose. Show what the capability offers, its declared setup, and its current readiness. Search is discovery; do not imply that viewing or selecting a result connected an account or started work.
4. Obtain that person’s authority. For Act in a customer-facing app, use that customer’s Darwin sign-in and OAuth approval with human:actions. Use the returned grant for that customer alone. Provider authentication, exact action approval, or payment may still be requested later in the thread.
5. Start and follow Act. Call Act with one selected agent and a stable idempotency key. Read its returned threadId through Get act request. Surface typed requests for authentication, approval, or payment without turning plain chat text into consent.
6. Return the result to your product. Show the provider’s actual output and unresolved exceptions in the originating customer workflow. Keep pending, failed, cancelled, and completed states distinct. An accepted request or a copied connection prompt is not a completed outcome.