---
title: Introduction
description: REST and MCP access to AMFG Engine entities for external integrations.
---

The Public API exposes the entities of an AMFG Engine App (orders, quotes, parts, materials, machines, builds and more) to your own systems. Every call is authenticated with one header, and the same operations for quotes, tickets and parts are also available to AI agents over [MCP](/engine-service/public-api/v1/docs/mcp).

## Base URL

```text
https://next.amfg.ai/engine-service/public-api/v1
```

The path, the `Authorization` header and the secret format are a stable contract. A breaking change ships as `/public-api/v2`; nothing under `/public-api/v1` changes shape.

## Quickstart

1. **Create an Incoming Secret**

    In the console, open **Settings → API Keys** and create an **Incoming** secret. Copy the value. It is shown only once.

2. **Call the API**

    ```bash
    curl "https://next.amfg.ai/engine-service/public-api/v1/ticket-quote?limit=1" \
      -H "Authorization: <secret>"
    ```

3. **Explore the reference**

    Every operation has its own page in the [API reference](/engine-service/public-api/v1/docs/reference), with a **Try it** panel that sends real requests with your secret.

## Where to next

**[Authentication](/engine-service/public-api/v1/docs/authentication)**

Incoming Secrets, the Authorization header and IP allowlists.

**[Conventions](/engine-service/public-api/v1/docs/conventions)**

Filters, retrieves, whole-record updates and errors.

**[Worked examples](/engine-service/public-api/v1/docs/examples)**

Read an order, manage entities, create quotes.

**[MCP](/engine-service/public-api/v1/docs/mcp)**

Connect Claude and other agents to the same operations.