BRAINIAC Agent Contract State Transition Checker is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.04/call, status unknown (last checked 2026-11-12).
Validates state machine consistency in agent workflow contracts, detecting contradictory transitions, unknown states, and undefined operations.
Pay-per-call APIs for AI agents: OFAC sanctions screening, compliance checks, token security, and Base chain data via x402. No account. Fixed USDC price. MCP-ready.
Returns a numeric validation score (0-100), a list of issues with type, severity (high/medium/low), location, description, agent impact explanation, and suggested fix, plus warnings for soft problems like states with no incoming or outgoing transitions, and an analysis summary string.
POSThttps://www.brainiac.software/api/v1/agent-contracts/state-transition-check?utm_source=zero.xyzUse this endpoint when you need to statically validate the logical consistency of an agent workflow contract's state machine before deployment or execution — especially when the contract mixes OpenAPI operations with named states and transitions. Prefer this over manual review or generic linting when you need structured issue reports with agent-impact explanations and actionable fix suggestions. Best suited for catching contradictory transitions, dangling state references, and undefined operations in multi-step agentic workflows.
| Field | Type | Description |
|---|---|---|
| openapi | object | |
| workflows | array | |
| operations | array |
{
"type": "json",
"example": {
"score": 48,
"issues": [
{
"type": "unknown_operation",
"evidence": "missing_op",
"location": "workflows[0].transitions[1]",
"severity": "medium",
"description": "A transition names an operation that is not in the supplied operation list. The operation was not assumed to exist.",
"agent_impact": "An agent can call an operation the contract bundle does not define.",
"suggested_fix": "Point the transition at a supplied operation name."
},
{
"type": "contradictory_transition",
"evidence": "draft on place -> submitted and paid",
"location": "workflows[0].transitions[1]",
"severity": "high",
"description": "The same state and trigger lead to two different states in the supplied workflow.",
"agent_impact": "An agent cannot choose one next state for the same trigger.",
"suggested_fix": "Keep one destination for that state and trigger."
},
{
"type": "unknown_state",
"evidence": "archived",
"location": "workflows[0].transitions[2]",
"severity": "high",
"description": "A transition ends in a state that is not in the supplied state list.",
"agent_impact": "An agent can record a state the rest of the contract does not mention.",
"suggested_fix": "Add archived to states or change the transition."
}
],
"success": true,
"analysis": "Checked 1 workflows or operation texts that declare a transition.",
"warnings": [
{
"type": "no_incoming",
"evidence": "draft",
"location": "workflows[0]",
"severity": "low",
"description": "No supplied transition enters this state. The contract does not identify it as the start.",
"agent_impact": "An agent has no declared way to reach this state.",
"suggested_fix": "Add the transition that enters it, or mark it as the start in the workflow text."
},
{
"type": "no_outgoing",
"evidence": "paid",
"location": "workflows[0]",
"severity": "low",
"description": "No supplied transition leaves this state. The contract does not say it is terminal.",
"agent_impact": "An agent may wait for a later state that is never defined, or it may stop early.",
"suggested_fix": "Add the next transition, or state that this state is terminal."
}
],
"limitations": [
"Checks read only the supplied operations, workflows, and OpenAPI document. No URL is fetched and no model reads the text.",
"A missing sentence is an undocumented contract. It is not a confirmed defect in a running implementation.",
"A contradiction is two statements in the supplied text. It is not proof of how a server behaves.",
"The HTTP method is not evidence that an operation is safe to retry or that it is idempotent.",
"Matches are fixed phrases and field names. They do not infer a business rule that the text does not state.",
"Transitions come from workflow.transitions and from operation sentences that say from X to Y or X -> Y.",
"An unknown operation is reported only when other operations were supplied and the name is absent. The check does not invent the missing operation.",
"An unknown state or a trigger with two destinations is a conflict in the document. A state with no edge is a warning and does not change the score.",
"Each unknown state subtracts 15. A contradictory trigger subtracts 25. An unknown operation subtracts 12. The score is omitted when no transition is declared."
],
"recommendations": []
}
}No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"