> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/settings/developer-tools.md).

# Developer Tools

Settings for integrating PeakCommerce with your own systems — API keys, the hosted payment pages your billing provider serves, outbound webhooks, the analytics scripts injected on your public pages, and the embeddable widget.

* [API Keys](https://docs.peakcommerce.com/product/settings/developer-tools/api-keys.md) — scoped credentials for the Agent API.
* [Hosted Pages](https://docs.peakcommerce.com/product/settings/developer-tools/hosted-pages.md) — the provider-hosted payment pages your Payment-type pages embed.
* [Tracking Scripts](https://docs.peakcommerce.com/product/settings/developer-tools/tracking-scripts.md) — analytics and tag-manager snippets (GTM, GA4, VWO, Heap, …) injected on your public pages and journeys.
* [Webhooks](https://docs.peakcommerce.com/product/settings/developer-tools/webhooks.md) — outbound event subscriptions with signed delivery.
* [Widget Embed](https://docs.peakcommerce.com/product/settings/developer-tools/widget-embed.md) — embed a PeakCommerce buying experience in your own site.

> For the full API documentation, see the [Developers](https://gitlab.com/peakcommerce/peak-help-docs/-/tree/main/developers/README.md) space.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.peakcommerce.com/product/settings/developer-tools.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
