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

👉 The template should follow this flow:
1. Overview
2. API Basics
3. Quick Start Guide
4. Use Cases
5. API Reference
6. Integration and Testing
7. Postman Collections (optional)
8. Reference Application.
9. Code and Formats
10. Support
11. Release History (optional)

<br />

Warning: Ensure all instances of '{Pet Store}' are replaced with the actual name of your service.

## Overview {#overview}

👉 Add a brief outline of the service and its value proposition. What problem does the API solve for the developer in the real world? Click [here](https://stage.developer.mastercard.com/jamstack/documentation/content-guide/documentation-guide/#homepage-root-of-the-documentation-page) for documentation about what is expected in this page.

The {Pet Store} API provides a comprehensive suite of API calls designed to streamline and optimize store operations. Managing a large volume of pet data, tracking adoptions, and handling employee records can be challenging; the Pet Store addresses these complexities by providing a standardized, automated way to handle these tasks.

The API offers endpoints categorized into Dogs, Cats, Pets, Adoptions, and Employees, with each tailored to support specific {Pet Store} functionalities involving pet information, adoption processes, and employee records.

👉 At the end of the overview section you should provide a link back to your Product Landing Page. Please update the below link to point to your product landing page URL.
Note: The Mastercard {Pet Store} product page can be found [here](https://stage.developer.mastercard.com/reference-service-ngw/product/reference-service-ngw-product/).

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

👉 Let the developer know where the service fits in a real-world scenario. Describe the actors that are required and the outcomes that occur from usage of the service. A diagram showing how the entire system will work with a customer's system is mandatory, if possible create a base diagram and request the Mastercard UX team to style it.

![how-it-works](https://static.developer.mastercard.com/content/mastercard-agent-pay/documentation/img/how-it-works-new.png)

👉 See the [Lists shortcode](https://stage.developer.mastercard.com/jamstack/documentation/theme/markdown-guide/syntax/#unordered-lists) here   
* **Party 1:** Add some Information.
* **Party 2:** Add some Information.
* **Party 3:** Add some Information
* Add some information.
* Add some information.
* Add some information.

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

👉 Briefly (in one or two sentences) outline what is good to know about your service. For example, let them know of any contractual or legal agreements that need to be in place, or if they need to supply a client id for bespoke onboarding to your databases. Provide links to guides/tutorials/more contextual pages which have the detail instead of expanding here. Click [here](https://stage.developer.mastercard.com/jamstack/documentation/content-guide/documentation-guide/#getting-started) for documentation about what is expected.
> * **Onboarding Information:** Onboarding is done through creating an account on [Mastercard Developers](https://developer.mastercard.com/) and activating Sandbox/Production project credentials.
> * **Testing Information:** We have an [Open Sandbox](https://developer.mastercard.com/mastercard-agent-pay/documentation/integration-and-testing/index.md) which you can utilise to test sandbox calls.
> * **Batch Processing:** Mastercard {Pet Store} 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 {Pet Store} is available globally.

## Next Steps: {#next-steps}

👉 Direct the User to the API Basics page.

Now that you have an understanding of what the service does, proceed to the [API Basics](https://developer.mastercard.com/mastercard-agent-pay/documentation/api-basics/index.md) section for details on authentication and encryption.