What you get
Tool ID Lifecycle Audit Report
PDF, 12-18 pages. Documents the exact point where your agent's tool_id generation diverges from MiniMax's expectations. Includes annotated session traces and failure tree analysis.
Deterministic Replay Fixture
Python test case that deterministically reproduces the HTTP 400 rejection. Can be run locally to validate fixes without hitting the live API.
State Map Implementation YAML
Configuration template showing how to cache and persist tool_id values across conversation turns. Prevents ID regeneration that causes the 2013 error.
Pre-Flight Validation Schema
YAML contract check that validates tool_result payloads before submission. Catches malformed tool_id references before they hit the MiniMax API.
Reference Patch Diff
Annotated diff file showing the exact code changes needed in openclaw (or equivalent agent) to fix tool_id persistence. Includes rollback instructions.
How it works
Fixed Sprint Price
$3,500
flat rate — all 5 deliverables included
Frequently Asked
What if my agent isn't openclaw?
The replay fixture and state map implementation are agent-framework-agnostic. The principles apply to any AI agent that manages tool call IDs across conversation turns. The reference patch targets openclaw specifically, but the diff methodology transfers to other frameworks.
What data do you need from me to start?
At minimum: (1) a sample HTTP 400 response payload showing the tool_id error, and (2) your agent's tool call dispatch code or a snippet of the session where the mismatch occurs. If you have full request/response logs, that's better but not required.
Does this fix the underlying MiniMax API issue?
No — this sprint fixes your agent's handling of tool_id lifecycle. If MiniMax has changed validation rules in 2026, the pre-flight validator and state map will adapt to those rules. The artefacts are designed to be updated if the API specification changes.
Is there a guarantee the fix will work?
The deliverables are production-grade artefacts based on the confirmed GitHub issue (#76) in the MiniMax-M2 repository. The replay fixture ensures you can validate the fix independently before deploying. Walkthrough on Day 5 covers implementation guidance.