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

# Build with AutoAdy

> Choose REST, MCP, or the CLI and verify your first account read.

Use AutoAdy from a script, an agent, or a terminal. All three interfaces act with your AutoAdy identity and check account access, tool availability, and plan requirements.

| Interface | Start here | Best for |
| - | - | - |
| REST | [Requests and responses](/developers/requests) | Your own application or HTTP client |
| MCP | [MCP clients](/developers/clients#mcp-server) | An assistant that discovers and calls tools |
| CLI | [Command line](/developers/clients#command-line) | Shell scripts and CI |

## Quickstart

1. Create a named [API key](/developers/authentication#create-a-key). For a Meta read, first connect [Meta](/connections/meta) with the intended identity.

2. Put the key in your private runtime environment as `AUTOADY_API_KEY`.

3. List the accounts that identity can reach:

   ```bash theme={null}
   curl --request POST 'https://www.autoady.io/api/mcp/list-accounts' \
     --header "Authorization: Bearer ${AUTOADY_API_KEY}" \
     --header 'Content-Type: application/json' \
     --data '{}'
   ```

4. Inspect `data.accounts`. Use a returned account ID in your first performance read:

   ```bash theme={null}
   curl --request POST 'https://www.autoady.io/api/mcp/results' \
     --header "Authorization: Bearer ${AUTOADY_API_KEY}" \
     --header 'Content-Type: application/json' \
     --data '{"account_id":"act_1234567890","level":"campaign","date_preset":"last_7d"}'
   ```

The ID above is a placeholder. A successful empty account list proves authentication, but does not prove a reachable Meta connection. Check the intended identity, connection, and workspace grants before continuing.

## Authentication and errors

REST uses `Authorization: Bearer adk_...`. OAuth-capable MCP clients can use account sign-in instead. [Authentication](/developers/authentication) covers key creation, expiry, permissions, and revocation. [Requests and responses](/developers/requests#handle-errors) explains both error envelopes and recovery.

## Endpoint reference

The [REST reference](/developers/reference) groups the 52 currently published POST endpoints by task. MCP has a wider catalog; use its `tools/list` response for the actual tools offered by that server. Tool names, argument shapes, and availability can differ between the two interfaces.

## MCP server

The remote MCP endpoint remains `https://www.autoady.io/api/mcp`. Follow [MCP and CLI setup](/developers/clients#mcp-server), or the [client setup guide](/agent/connect) for a first verified read.

## Command line

Use `npx -y @autoady/cli` or install the CLI globally. [Command line setup](/developers/clients#command-line) covers environment credentials, commands, raw JSON calls, and exit codes.

## OpenAPI specification

The public [OpenAPI 3.1 specification](https://www.autoady.io/api/openapi) supplies request schemas, examples, and response definitions. Fetch it without authentication to configure your HTTP client. Keep credentials out of generated files and shared examples.

Start with reads. Before any account change, review its exact target and proposed effect with the user, then follow the tool's returned confirmation and retry contract.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.