# A-Comm developer documentation

> A-Comm provides a voice and text shopping agent for merchant storefronts, with merchant signals and verifiable transaction evidence. The agent connects to the merchant's commerce systems through a Model Context Protocol (MCP) connector or an API. A-Comm is in beta; integration, access, testing, and launch are coordinated with A-Comm engineering.

These public docs help merchant engineering teams evaluate A-Comm. Canonical documentation: https://developer.a-comm.ai/. Company website: https://a-comm.ai/. This summary was reviewed against the published developer documentation on 17 September 2026.

The configured shopping workflow supports product discovery, cart changes, checkout, and payment authorization through the merchant's connected systems. The merchant retains its existing payment-processing setup. Available actions, shopper confirmations, system connections, and operating responsibilities are agreed during onboarding; the commerce-workflow checklist is a scoping guide, not a promise that every listed action is enabled.

The integration produces two useful outputs:
- Merchant signals: observations about stated needs, product choices, and shopping friction. Available fields, merchant access, and delivery are agreed for each pilot. These observations support investigation; they are not automated fraud decisions or evidence of measured business improvements.
- Journey and transaction evidence: captured intent, permissions, agent actions, and workflow responses that teams can retrieve, review, verify, and export through the agreed integration.

Capture begins at session creation on the integrated storefront. Captured records are retained under an evidence ID even without a purchase. Pre-authorization records remain unsealed. The transaction chain seals when the required payment-authorization evidence is captured; later fulfillment and dispute or chargeback records link to the journey without rewriting the sealed history. Capture is best-effort: a Vault outage does not block checkout, and evidence may be missing or incomplete.

A-Comm Evidence Protocol (AEP) defines evidence structure and integrity verification. A-Comm Vault is the managed service that stores captured records and supports retrieval, verification, and export. Verification checks recorded integrity; it does not establish completeness, the truth of every assertion, or a guaranteed dispute outcome. Reading or implementing AEP does not provision access to A-Comm's hosted services.

Dispute receipt and evidence assembly are available within the agreed integration. Submission through A-Comm is not available currently. The merchant uses its existing processor or dispute-management workflow for submission and deadlines.

Public documentation can be read without credentials. Hosted service access requires onboarding with A-Comm engineering, which supplies the applicable service addresses, authentication requirements, API examples, and credential procedures. This site is an evaluation guide, not a self-service deployment console or a public API contract. MCP references describe merchant-system connections; they do not advertise a public A-Comm MCP endpoint for external agents. Server credentials must remain outside storefront code.

The documentation links below identify sections of one HTML document. Their URL fragments are navigation targets, not separate API endpoints.

## Evaluate A-Comm

- [Overview and beta capabilities](https://developer.a-comm.ai/#start): Product purpose, system connections, current scope, and intended audience.
- [Merchant integration](https://developer.a-comm.ai/#merchant): Commerce workflows, checkout and payment boundaries, configuration, pilot-scoped customer context, and team responsibilities.
- [Merchant signals and transaction evidence](https://developer.a-comm.ai/#evidence): Captured observations, evidence IDs, sealing, retrieval, verification, export, and capture limitations.
- [Dispute preparation](https://developer.a-comm.ai/#disputes): Receipt, evidence assembly, review, and merchant-owned submission.

## Plan an integration

- [Pilot readiness checklist](https://developer.a-comm.ai/#golive): Agree scope, validate complete and incomplete journeys, and establish support, credential maintenance, rollback, and launch responsibilities.
- [Technical concepts and access](https://developer.a-comm.ai/#reference): Assisted onboarding, authentication guidance, AEP versus Vault, and terminology.
- [Contact A-Comm engineering](mailto:devs@a-comm.ai): Start an integration discussion with your storefront, commerce stack, available interfaces, and intended workflow. Do not include API secrets or payment details.

## Protocol and company

- [A-Comm Evidence Protocol specification](https://aep.a-comm.ai/): Protocol definitions for evidence structure and integrity verification; distinct from hosted-service access.
- [A-Comm company website](https://a-comm.ai/): Company and product overview.

## Optional

- [Documentation map](https://developer.a-comm.ai/#map): Full navigation for the merchant evaluation guide.