# Bounty Engineer Task State Transition Gate

> Bounty Engineer Task State Transition Gate is a paid API for AI agents from bounty-engineer-x402-prod.onrender.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-12).

Validates and enforces allowed state transitions for agent tasks, returning a decision (allow/deny) with the set of valid next states from a given current state.

## Facts

- Endpoint: POST https://bounty-engineer-x402-prod.onrender.com/v1/task-state-transition-gate?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bounty-engineer-task-state-transition-gate-8e6b5054
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_78GXfmNbjsdkqRBMtYzwz

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability bounty-engineer-task-state-transition-gate-8e6b5054 -d '<json body>'
```

Example prompt: Check whether my agent task is allowed to transition from 'working' to 'completed' — I don't have any custom state rules so just use the default task state machine.

## When to prefer this

Use this endpoint when an autonomous agent needs to enforce task lifecycle rules before committing a state change — especially in multi-step pipelines where illegal transitions could corrupt task state. Prefer it over ad-hoc conditional logic when you need a consistent, auditable gate with explicit allowed-transition semantics and support for custom state machine overrides.

## Known failure modes

- Unknown 'from' state returns known_from_state: false and may restrict allowed_targets
- Missing 'to' or 'from' fields may result in a validation error or denial
- Custom allowed_transitions map with invalid structure may cause unexpected behavior
- Self-transitions denied by default unless allow_self is set to true

## How this service works

Machine-buyable infrastructure for autonomous agents: API cost routing, margin optimization, funding-rate data, webpage extraction, result verification, spend controls, retry planning, state, tender search and GitHub bounty intelligence.

## Output

Returns a JSON object with a boolean 'ok', the decision ('allow' or 'deny'), the reason for the decision, the mode ('task_state_transition_gate'), a list of allowed target states from the current state, a flag indicating whether the from-state is recognized, and any limitations (e.g. whether a generic or custom state machine was applied).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "to": {
   "type": "string"
  },
  "from": {
   "type": "string"
  },
  "allow_self": {
   "type": "boolean"
  },
  "allowed_transitions": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "to": "completed",
  "from": "working",
  "mode": "task_state_transition_gate",
  "reason": "allowed_transition",
  "decision": "allow",
  "limitations": [
   "The default state machine is a generic agent-task profile. Supply allowed_transitions when a specific protocol or application uses different states."
  ],
  "allowed_targets": [
   "input_required",
   "completed",
   "failed",
   "cancelled"
  ],
  "known_from_state": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bounty-engineer-task-state-transition-gate-8e6b5054/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bounty-engineer-x402-prod.onrender.com](https://www.zero.xyz/host/bounty-engineer-x402-prod.onrender.com/llms.txt)