---
title: "Discover operations"
description: "Read the exact operations and input schemas granted to an Agent key."
image: "https://help.agent.mq/og.svg"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.agent.mq/llms.txt
> Use this file to discover all available pages before exploring further.

# Discover operations

Operation discovery is the contract an agent should read before calling anything. It includes only enabled, configured, supported operations admitted for the presented machine credential.

```bash
curl https://api.agent.mq/v1/agent/applications/app_<32-lowercase-hex>/operations \
  -H "Authorization: Bearer $AGENTMQ_TOKEN"
```

Each entry includes:

| Field | Meaning |
| --- | --- |
| `id` | Stable application operation identifier used in Agent paths |
| `name` | Display name |
| `capability` | Internal capability name; omitted from isolated one-off purchase applications |
| `requiresEndUser` | Whether to use the prepare/approval flow |
| `inputSchema` | JSON Schema for the direct request body |

## Boundaries

- Discovery does not return provider credentials.
- A disabled connection or withdrawn workflow disappears from callable discovery.
- An Agent key follows the application's current enabled operation set; it is not a frozen operation list.
- Write effects still require idempotency and may require human approval.

## See also

- [Invoke an operation](/build/invoke)
- [Prepare, approve, and execute](/approval/human-approval)

Source: https://help.agent.mq/build/operations/index.mdx