Contribute a tested integration.

Keep changes within their authority

1. Discuss shared catalog or root dependency changes with the customer-site owner first. Agent-specific changes belong in agent-commerce/.
2. Use structured schemas and the existing engine. Never add a separate price list, model-controlled discount or checkout destination input.
3. Add a small independent client and run malformed-input, owner-isolation, idempotency, expiry and restart checks.
4. Document exactly which protocol/version and capabilities were exercised. Redact keys, domains and private task artifacts from public evidence.
5. Update this registry/changelog only when a runnable example exists. Include limitations; do not fabricate adoption.

Local interoperability checks

npm ci --prefix agent-commerce --ignore-scripts
pnpm exec tsx --test agent-commerce/a2a.test.ts agent-commerce/commerce.test.ts
pnpm exec tsc -p agent-commerce/tsconfig.json
pnpm exec tsx agent-commerce/a2a-client.ts
node agent-commerce/hub-review.mjs

The tests drive actual HTTP requests with the official SDK and raw JSON-RPC, validate the supported wire profile and exercise process restart. They do not constitute the official A2A TCK or certify every SDK/platform. Browser checks require the existing Playwright dependency and installed Edge.

Report an integration problem

Use the existing Safi.pk support page ↗ or contact page ↗. These are the current catalog's confirmed service links; local tests do not claim message delivery or an SLA. This task sends no report automatically.

Include SDK/protocol version, operating system, operation, sanitized error code, timestamp and X-Request-ID if available. Include a minimal command with example product IDs and placeholder domains. Remove bearer tokens, email addresses, real domains, private quote/task/context IDs, payment details and private artifacts. Send sensitive diagnostic details only through a separately approved private support exchange. No public forum, membership, endorsement or platform identity is implied.