# OneShotAgent Compute Orchestrator

> OneShotAgent Compute Orchestrator is a paid API for AI agents from win.oneshotagent.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-13).

Executes autonomous multi-step goals using natural language objectives and a suggested USDC budget

## Facts

- Endpoint: POST https://win.oneshotagent.com/v1/compute
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/oneshotagent-compute-orchestrator-6a19eda5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Z2BYfzE2xU8jpc62w9h3O

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 oneshotagent-compute-orchestrator-6a19eda5 -d '<json body>'
```

Example prompt: Go research the top 5 competitors of Notion, compile a comparison table of their pricing and key features, and save the result as a markdown file — my budget for this is $0.10 USDC.

## When to prefer this

Choose this endpoint when the user's goal cannot be accomplished in a single API call and requires autonomous planning, multi-step execution, and tool use — especially when the scope of sub-tasks is unknown upfront. Prefer this over single-purpose endpoints (search, email, enrichment) when the task needs to combine multiple capabilities dynamically under a budget constraint.

## Known failure modes

- Insufficient budget_usdc causes task to terminate early or fail mid-execution
- Ambiguous or underspecified objective leads to misinterpretation and incorrect output
- Dependent sub-services unavailable causing orchestration failure
- Budget exhausted before goal completion with partial results returned
- Invalid params object schema causes request rejection
- Timeout if goal requires too many sequential steps

## How this service works

Compute orchestrator - autonomous multi-step goal execution

## Output

Returns the outcome of the autonomously executed multi-step goal, which may include computed results, gathered data, created artifacts, or a completion status depending on the objective provided.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "params": {
   "type": "object",
   "description": "Task-specific parameters"
  },
  "objective": {
   "type": "string",
   "description": "Natural language goal"
  },
  "budget_usdc": {
   "type": "number",
   "description": "Suggested budget in USDC"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/oneshotagent-compute-orchestrator-6a19eda5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from win.oneshotagent.com](https://www.zero.xyz/host/win.oneshotagent.com/llms.txt)