Tool/trigger discovery returns a bare 404 when Composio is not configured

[mmabrouk]

What happens

On a self-hosted OSS deployment without COMPOSIO_API_KEY set, the platform tools discover_tools and discover_triggers return HTTP 404. list_schedules works.

Steps to reproduce

1. Run OSS self-host without setting COMPOSIO_API_KEY.
2. From an agent, call discover_tools or discover_triggers.
3. Both return 404.

Why it happens

discover_tools and discover_triggers route through the Composio adapter, which is only built when COMPOSIO_API_KEY is set (api/entrypoints/routers.py). Without a key, the provider is missing and the service raises ProviderNotFoundError, which the router maps to 404 (api/oss/src/core/tools/service.py, api/oss/src/apis/fastapi/tools/router.py). list_schedules reads from the database and never touches the adapter, so it works.

The problem

A bare 404 reads as "endpoint missing," not "provider not configured." A self-hoster cannot tell whether they hit a bug or a missing setup step.

Suggested fix

Return a clearer status for the not-configured case, for example 501 or 503 with a body like Composio not configured; set COMPOSIO_API_KEY. This is distinct from a genuine not-found.

Context

Documented the expectation for self-hosters in #5406 (new "App tools and triggers" page). This issue tracks the API-side status-code improvement.

[linear-code]

AGE-3973

[unfitcoder101]

I'd like to work on this. Root cause is clear — ProviderNotFoundError
maps to 404 but should return 501/503 with a descriptive message when
COMPOSIO_API_KEY is not set. Will trace the error mapping in
tools/service.py and tools/router.py and update the status code + body.

[mmabrouk]

@unfitcoder101 I will assign this to you. Please however make sure that you can set up Agenta in dev mode (your machine allow it), we don't accept PRs without a video recording showing the fix in action in dev mode.

[unfitcoder101]

@mmabrouk Thanks for the assignment! Quick check — my machine struggles
with the full Docker stack (MacBook Air M1, thermal throttling).
Would a screen recording of the API response before/after the fix
using unit tests + curl against a local FastAPI instance be acceptable,
or do I need the full Docker compose running?

[mmabrouk]

API response would work. Can you try running web outside of docker that could help too

…

On Mon, Jul 20 2026 at 10:08 PM, Harshvardhan Kasliwal < ***@***.*** > wrote: *unfitcoder101* left a comment (Agenta-AI/agenta#5407) ( #5407 (comment) ) @mmabrouk ( https://github.com/mmabrouk ) Thanks for the assignment! Quick check — my machine struggles with the full Docker stack (MacBook Air M1, thermal throttling). Would a screen recording of the API response before/after the fix using unit tests + curl against a local FastAPI instance be acceptable, or do I need the full Docker compose running? — Reply to this email directly, view it on GitHub ( #5407?email_source=notifications&email_token=ABCNIJXL34UOJF3I3BP7NC35F2C6PA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBSG4ZTAMBVHEYKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5027300590 ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/ABCNIJX7M2IYZ3TYDXGN5UL5F2C6PAVCNFSNUABFKJSXA33TNF2G64TZHM3DGMRYG4YTMMRYHNEXG43VMU5TIOJSHA3TKNJWHAYKC5QC ). Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS ( https://github.com/notifications/mobile/ios/ABCNIJUNS5QO3TKJWBPJNKD5F2C6PA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBSG4ZTAMBVHEYKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y ) and Android ( https://github.com/notifications/mobile/android/ABCNIJUMRAHLIRCFDIABSN35F2C6PA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBSG4ZTAMBVHEYKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI ). Download it today! You are receiving this because you were mentioned. Message ID: <Agenta-AI/agenta/issues/5407/5027300590 @ github. com>

[unfitcoder101]

@mmabrouk PR updated with full template: #5425

[unfitcoder101]

@mmabrouk unable to run the FastAPI server locally without the full Docker stack (module resolution fails outside Docker). The fix is a 5-line exception catch with deterministic behavior — happy to provide a curl recording if you can point me to a staging environment, or if you can run it internally and verify. Ready to merge on your end.