# Starter Template
source: https://developer.mastercard.com/agent-suite-for-merchants/documentation/index.md

👉 Replace the placeholders on this page with your real service name, product page URL, system actors, and diagram. Keep the section order and level of detail aligned with the example structure below.

## Overview {#overview}

The {Your Service Name} API is a RESTful API that enables clients to programmatically manage core business resources, execute downstream workflows, and maintain supporting administrative records.
It serves as a centralized system-of-record layer for day-to-day operations, replacing manual processes and disconnected integrations with a standardized, automated interface.

The API offers endpoints categorized into clear resource families, with each tailored to support a distinct part of the service workflow and the data exchanged between related operations.
Note: The Mastercard {Your Service Name} product page can be found on the [product landing page](https://developer.mastercard.com/agent-suite-for-merchants/product/reference-service-ngw-product/index.md).

## How It Works {#how-it-works}

![how-it-works](https://static.developer.mastercard.com/content/agent-suite-for-merchants/documentation/img/how-it-works-new.png)
* **Primary business entity:** The core resource or record being managed by the service.
* **Consumer or operator:** The person or system that submits requests to create, retrieve, search, update, or delete records.
* **Administrative user:** The user responsible for configuration, exception handling, and operational management.
* **API:** The REST interface that processes authenticated requests and returns governed responses.
* **Client application:** The consumer-facing interface or internal system that initiates the API calls.
* Automate and streamline operational workflows such as creating, updating, querying, and deleting records.
* Improve data accuracy, reliability, and security across the service lifecycle.
* Reduce manual handling by providing standardized request and response patterns.
* Establish a repeatable onboarding and operational model for service consumers and administrators.
* For a more detailed view of the service journeys, explore the [Use Cases](https://developer.mastercard.com/agent-suite-for-merchants/documentation/use-cases/_index/index.md) section.

## Good to Know {#good-to-know}

> * **Onboarding Information:** Onboarding starts by creating an account on [Mastercard Developers](https://developer.mastercard.com/) and generating Sandbox project credentials.
> * **Testing Information:** We have an [Open Sandbox](https://developer.mastercard.com/agent-suite-for-merchants/documentation/api-reference/index.md) that you can use to test Sandbox calls.
> * **Batch Processing:** Mastercard {Your Service Name} does not support [Batch Processing](https://aws.amazon.com/what-is/batch-processing/#:~:text=Batch%20processing%20is%20the%20method,run%20on%20individual%20data%20transactions.).
> * **Region Availability/Border Control:** Mastercard {Your Service Name} is available according to the environments documented in this template.

## Next Steps {#next-steps}

Now that you have an understanding of what the service does, you can proceed to the [Quick Start Guide](https://developer.mastercard.com/agent-suite-for-merchants/documentation/quick-start-guide/index.md) to quickly get started, or to the [API Basics](https://developer.mastercard.com/agent-suite-for-merchants/documentation/api-basics/index.md) section for details on authentication and encryption.