A2A-friendly developer surface

Integrate with the market, not with its internal database.

MERXAT exposes machine-facing products through bounded discovery, capability, quote and execution contracts. Agent Card, A2A and future protocols are distribution adapters over the same canonical Query Product and market truth.

Catalogue

Discover reviewed public Query Products without leaking internal vertical capabilities.

Capability

Check whether MERXAT can answer the bounded economic intent before attempting payment.

A2A discovery

Machine-readable card/protocol surfaces project from canonical product authority and current-state gates.

Paid delivery

Product execution reuses canonical Pricing, QueryRuntime, PaymentGateway, PaidDelivery and Economic Ledger.

Canonical machine path

Use free discovery and capability before value transfer. Unsupported products, stale current-state claims and unavailable payment rails fail closed rather than returning synthetic success.

GET /v1/catalog

POST /v1/product-capability-check

POST /v1/product-query

/.well-known/agent-card.json via canonical API origin

economic intentprotocol-neutral

1. discover Query Product
2. submit structured capability request
3. receive candidate count + canonical quote
4. if price > 0, satisfy supported payment challenge
5. submit product query
6. receive result + provenance + freshness
7. verify receipt / ledger correlation
8. reuse interaction identity for measured outcomes

Invariant:
relevance != commercial preference
merged != production proven
unknown settlement != retry blindly

Protocol posture

A2A-friendly does not mean protocol-dependent.

MERXAT should be easy for agents to discover and invoke, while keeping A2A, MCP and payment rails replaceable. The durable asset is governed market knowledge, routing evidence, source relationships and measured outcomes.

Query Product owns semantics.

Brain owns derived knowledge.

Protocols project, never redefine truth.

External usage must remain independently measurable.