ACP compatibility for AI agents
ACP compatibility lets an integration discover Autopilot or Ask AI agents and submit work using alternative request formats.
What it is
INSIDE has compatibility adapters for Bee ACP and AGNTCY-shaped agent requests. They offer discovery and run operations for Autopilot and Ask AI. Both use the same AI execution and temporary run history as other agent requests.
Who uses it and why
Developers use the adapters when an existing agent integration expects one of these request formats. Agree the supported contract and authentication with Powerfront before connecting a client.
Where to find it
These are authenticated integration operations, with no separate Settings screen. Configure the AI features they execute in Settings › AI › Features with the Settings role and AI access, or the Developer role.
How it works
The Bee ACP adapter supports agent discovery, run creation, run lookup, event lookup and cancellation. Run creation waits for completion by default. An asynchronous request returns a run that you can check later.
The AGNTCY compatibility adapter supports agent search, agent lookup, run creation, run lookup and cancellation. Its run creation waits for completion.
Discovery describes Autopilot and Ask AI. It is not a check that a suitable feature is available. At execution, INSIDE selects an enabled, active feature of the requested type, preferring higher priority and then the more recent feature identifier. A request fails if no suitable feature exists.
Run lookup and cancellation are restricted to the request's website. The Bee event operation returns the events retained for that run.
Configure it
Ask Powerfront to confirm the adapter and authenticated integration access for your use case. Prepare the intended Autopilot or Ask AI feature and check its availability and priority in Settings › AI › Features.
There is no dedicated ACP enablement option. Do not assume that Enable A2A Endpoint controls these compatibility operations.
Permissions
| Permission | Lets you |
|---|---|
| AI | With the Settings role, allows configuration of AI features; the Developer role can also access Features. |
Limits and good to know
- Discovery contains fixed descriptions of two agent types; it does not list every configured AI feature.
- Both adapters use temporary run records. Default expiry is 60 minutes after an active update and 15 minutes after a terminal update.
- A service restart can remove run history. Save results you need to retain.
- Cancelling a terminal run returns its existing state without restarting it.
- Compatibility with one request shape does not establish conformance with every ACP version or client.
Depends on and works with
View all connections as a list
This feature uses
- AI feature settings and change historyConfigured by
Enabled, active features and their priorities determine which feature executes a run.
- Autopilot for live chatConfigured by
When ACP executes Autopilot, that feature's instructions and selected functions determine the work it performs.
- Ask AI beside a visitor conversationConfigured by
When ACP executes Ask AI, that feature's instructions and selected functions determine the work it performs.
- AI accounts and shared defaultsRequires
The AI feature executing ACP requests needs a working AI account.
- INSIDE APIRequires
Compatibility operations use the authenticated HTTP API.
- My API Keys and access restrictionsRequires
Token-authenticated requests require credentials with permission to run AI features.
FAQ and troubleshooting
Why is an agent discoverable but its run fails?
Discovery lists agent types. Check that the website has an enabled, active AI feature of the requested type.
Why did a different feature handle the request?
The adapter selects by feature type and priority. Review competing features and their priorities with someone who has the Settings role and AI access, or the Developer role.
Can I submit asynchronous work through either adapter?
The Bee adapter supports asynchronous creation. The AGNTCY-shaped creation operation waits for execution.
Why can I no longer retrieve a run?
It may belong to another website, have expired or have been lost after a service restart. Run history is temporary.