---
title: "Quickstart"
description: "Discover and invoke one enabled AgentMQ operation."
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.

# Quickstart

## Prerequisites

- An application ID such as `app_<32-lowercase-hex>`.
- An enabled operation in that application.
- An unexpired application Agent key stored as `AGENTMQ_TOKEN`.

1. **Discover allowed operations**

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

   Read its `id` and `inputSchema`. The schema is the request body contract.
3. **Invoke it once**

```bash
curl -X POST \
  https://api.agent.mq/v1/agent/applications/app_<32-lowercase-hex>/operations/<operation-id>/invoke \
  -H "Authorization: Bearer $AGENTMQ_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: quickstart-20260921-01" \
  -d '{"text":"Hello from AgentMQ"}'
```

   Send the operation input object directly. Do not wrap it in an `input` property.
4. **Read an asynchronous receipt**

   If the invocation returns `202`, use its invocation ID:

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

## You should see

Discovery returns `operations`; invocation returns either a completed service result (`200`) or an accepted native execution (`202`). Reusing the same idempotency key returns the recorded invocation instead of dispatching a second effect.

## Next step

[Learn how operation discovery and schemas work](/build/operations).

Source: https://help.agent.mq/getting-started/quickstart/index.mdx