Problem
The issue is not simply that Aether lacks OpenAI Responses API support.
The actual problem is that, in OpenAI-compatible mode, Aether returns a JSON response (or streaming/non-stream payload) that OpenClaw cannot parse correctly in some cases.
This causes OpenClaw integration to fail with a JSON parsing / schema compatibility error.
Impact
When OpenClaw uses Aether as an OpenAI-compatible backend, requests can fail because the returned payload is not compatible with what OpenClaw expects.
Expected behavior
Aether's OpenAI-compatible responses should be valid and stable enough for clients like OpenClaw to parse successfully.
Actual behavior
OpenClaw encounters a JSON compatibility / parsing issue when using this Aether version.
Clarification
This report is not primarily about missing Responses API support.
It is about a malformed / incompatible / unexpected JSON payload problem in the OpenAI-compatible response path.
Suggested investigation areas
- Validate non-stream response JSON against OpenAI-compatible schema
- Validate stream chunk structure and final assembled payload
- Check for incomplete JSON / malformed fields / unexpected field names
- Compare Aether output with a known-good OpenAI-compatible backend that works with OpenClaw
Repro context
- Client: OpenClaw
- Backend: Aether
- Failure mode: JSON parsing / schema compatibility issue in OpenAI-compatible path
If needed, I can provide a concrete failing request/response sample in a follow-up.
Problem
The issue is not simply that Aether lacks OpenAI Responses API support.
The actual problem is that, in OpenAI-compatible mode, Aether returns a JSON response (or streaming/non-stream payload) that OpenClaw cannot parse correctly in some cases.
This causes OpenClaw integration to fail with a JSON parsing / schema compatibility error.
Impact
When OpenClaw uses Aether as an OpenAI-compatible backend, requests can fail because the returned payload is not compatible with what OpenClaw expects.
Expected behavior
Aether's OpenAI-compatible responses should be valid and stable enough for clients like OpenClaw to parse successfully.
Actual behavior
OpenClaw encounters a JSON compatibility / parsing issue when using this Aether version.
Clarification
This report is not primarily about missing Responses API support.
It is about a malformed / incompatible / unexpected JSON payload problem in the OpenAI-compatible response path.
Suggested investigation areas
Repro context
If needed, I can provide a concrete failing request/response sample in a follow-up.