# Exclusive Digits A2A

Discover https://exclusivedigits.com/.well-known/agent-card.json and send A2A 1.0 JSON-RPC to https://exclusivedigits.com/a2a. Include A2A-Version: 1.0 and Content-Type: application/json.

SendMessage accepts one structured data part: {"operation":"find_numbers","arguments":{"request":"A memorable Miami number","area_codes":["305"]}}. Use the input schemas of the four existing MCP tools for inventory arguments; inventory is free. Each call returns a Message containing text and structured results. No persistent A2A task, streaming or push-notification support is advertised.

Inventory operations: find_numbers, get_number, catalog_vocabulary, how_buying_works. A plain text message returns connection instructions; use structured arguments to preserve the buyer's requested filters.

Approved commerce partners can also use create_checkout, get_checkout, update_checkout, complete_checkout and cancel_checkout. Send the existing ED commerce bearer credential in the HTTP Authorization header, never in a message. Inventory credentials do not grant checkout access.

For create_checkout, arguments are the existing ACP checkout request, including line_items, buyer and capabilities. For other checkout operations, arguments.checkout_id identifies the checkout; the remaining arguments follow the corresponding ACP request. complete_checkout requires the buyer-authorized Stripe shared payment token in the existing ACP payment_data shape. See https://exclusivedigits.com/agent/commerce and https://exclusivedigits.com/openapi.json.

Send a stable, unique messageId for every operation and reuse it only for an identical retry. Checkout mutations use that messageId as their durable Idempotency-Key. Review the returned current quote before requesting payment. Creation does not reserve numbers or charge a card. Pending bank authentication and supplier authorization holds retain their existing checkout behavior.

Checkout messages are independent requests; keep checkout_id for subsequent operations. A contextId groups messages but grants no access and does not store buyer data. The checkout API enforces ownership on every request. Results with status >= 400 describe an operation failure; do not treat them as a successful purchase.