AgenticDome Copilot
From setup to verification.
Copilot guides your team through connecting an agent, runs read-only checks to show what is done and what is left, and prepares changes for you to review. It never makes enforcement decisions.
Illustrative. Live guidance reflects your own progress.
How do I connect my application?
Which describes it best: an application using an SDK, an MCP server, or OpenClaw? If it was discovered, I can start from there.
Know where to start
Pick the path that matches what you have. Select one to see what Copilot does next. Illustrative.
Application and SDK
Copilot helps you add the SDK or plugin to your agent application so that actions inside it are checked before they run.
- Choose your framework.
- Copilot prepares the change for your team to review.
- Your team applies it and runs the application.
- Verify with a real test action and read the evidence.
Read-only checks
Copilot checks what is complete and what needs attention without changing anything. It prepares setup changes for your team to review, and your team applies them.
Live onboarding needs an account and the right tenant permissions.
Abi and Copilot
Abi plans. Copilot connects and verifies.
Abi, your deployment concierge
Describe the outcome you need from your agents. Abi compares gateway, SDK, identity and runtime options, explains the trade-off, and produces a blueprint your team can review. Use text, or voice where enabled, and request a human handoff.
Explore Abi
AgenticDome Copilot, your onboarding guide
Once you have chosen a route, Copilot takes your team through setup, runs read-only checks, tracks progress and guides verification, and helps you gather context for support.
Open customer onboarding (sign-in required)
Setup shortcuts
The setup that fits your situation.
Use the supported setup route, then verify the connected execution path. Your team reviews and applies configuration changes.
| Your situation | What Copilot offers | Status |
|---|---|---|
| You can change service URLs | Your assigned sidecar URL, native client examples and caller identity settings. | Available |
| You use a supported framework | Supported SDK and plugin onboarding with connection settings and verification guidance. | Available |
| You deploy on Kubernetes, Docker or ECS | Generated workload environment fragments for your assigned sidecar; approved bundles for customer-hosted runtimes. | Available |
| You already run an API gateway or service mesh | Explicit HTTP routing guidance that preserves caller identity, target authentication and streaming. | Available |
| An unprotected asset was discovered | Connect protection, a suggested route, generated settings and linked runtime evidence. | Available |
| You want to confirm it works | Guided verification and read-only readiness checks. | Available |
You stay in control
Your team approves any repository or configuration change and any move to production enforcement. Source code stays local during guided setup.
Ready means verified
Readiness comes from your workload's verification checks and evidence, not from Copilot saying so. Coverage applies only to the integrations and execution paths you connect and verify.