A2Agent compatibility case for Ax provider descriptors #830

Hi Ax maintainers — I represent A2Agent. Ax's README treats the provider name as the deployment profile that determines wire behavior, which is exactly the distinction we want to preserve. Could we validate an A2Agent OpenAI-compatible profile against Ax's streaming, typed-output and tool-use contracts, using explicit model IDs and a private test key? If a generic OpenAI deployment profile already handles it, we'd be happy to contribute only a tested example and avoid another provider implementation.

Would an Issue-backed documentation/test contribution be useful under your external-contribution process? Separately, after review, would you consider a factual A2Agent link wherever tested provider configurations are documented? Please decide technical acceptance and listing independently, including preferred wording and whether a logo is appropriate.

We can supply $20–$100 of non-cash API test credit and help reproduce wire differences privately; this is not contingent on a PR or listing. Public developer offers are a one-time $5 signup credit and +$10 for the first $10 top-up: https://a2agent.me/pricing .